Iron Suite vs TX Text Control .NET Server

At-a-Glance Comparison

For the contract-drafting platform whose end users design and edit documents in the browser interactively, TX Text Control is the engine. For the backend ISV whose application transforms data into documents at scale (invoices, statements, certificates, reports) under one perpetual license, Iron Suite is the engine.

Pricing and Licensing

TX Text Control .NET Server publishes pricing transparently: Single Developer at $4,198 perpetual + $1,698/year renewal, Team (4 developers) at $8,398 + $3,398/year, Unlimited Deployment at $18,196 + $7,347/year. Each developer-seat tier includes 2 production licenses; per-server runtime licenses beyond those are required for additional production deployment and are quote-priced. The renewal model is essentially subscription-for-updates layered on a perpetual seat. Perpetual use is unconditional but continued access to updates and support requires the ~40%-of-list annual renewal.

Iron Suite ships at $2,998 for the entry tier, marketed as "all 10 products for the price of 2; save 75%". Tiers escalate through Lite, Plus, Professional, Unlimited, and Enterprise on a per-developer basis. The base license is royalty-free for the licensed seats and locations. No per-server runtime license is required for the base deployment. SaaS or OEM redistribution beyond the base requires the separate Redistribution Add-On.

TX Text Control's procurement is layered: a per-developer perpetual seat starting at $4,198, an annual $1,698 renewal for continued updates, plus per-server runtime licenses for production deployment beyond the bundled two licenses, with the JS DocumentEditor as a sibling SKU. Iron Suite's procurement is self-serve at a published USD price per tier, perpetual, with royalty-free deployment under the base license and the Redistribution Add-On as the only separately-priced item.

What is TX Text Control .NET Server

TX Text Control is a specialist word-processing and reporting engine for .NET, with deep WYSIWYG document editing as its defining capability. The .NET Server family targets ASP.NET and ASP.NET Core, with DocumentEditor JS frontends for Blazor, Angular, and React. Sibling products (.NET for Windows Forms, .NET for WPF) deliver the same editor for desktop applications. It is positioned for enterprise ISVs and corporate dev teams building document generation, contract drafting, and reporting into web and desktop apps.

Key bundled components:

• ServerTextControl core: server-side document load/manipulate/save (DOC, DOCX, RTF, PDF, PDF/A, HTML)
• Document Server: MailMerge engine, PDF export, format conversion
• DocumentEditor JS: browser-based WYSIWYG editor for Blazor, Angular, React, ASP.NET MVC
• DocumentViewer JS: browser-based document viewer
• ReportingCloud: SaaS reporting add-on
• TX Text Control .NET for Windows Forms / WPF: desktop editor controls (sibling SKUs)

What is Iron Suite

Iron Suite is Iron Software's programmatic .NET document bundle, ten products sized for backend applications and headless services that generate documents from data and read documents from disk. IronWord and IronPDF generate Word and PDF from code, the recognition stack reads scanned input, and the rest handles Office formats, printing, archives, and scraping. Sold as a single perpetual per-developer license at five tier levels from $2,998, royalty-free for the licensed seats. SaaS and OEM redistribution use a separate Redistribution Add-On.

The ten components, grouped by relevance to a programmatic Office and PDF workflow:

• Office stack (anchor): IronWord (DOCX creation and editing with paragraph and text-run object graphs that map directly to OOXML; styles, fonts, headers, footers, tables, content extraction); IronXL (XLSX with formula recalculation, charts, pivot tables, cell styling, conditional formatting, data validation); IronPPT (PPTX creation and editing, slide and text and shape primitives).
• PDF generation (IronPDF): HTML-to-PDF and URL-to-PDF rendering, native merge and split, PKCS#12 plus HSM plus TSA signing aligned to eIDAS and ESIGN, PDF/A-1 through PDF/A-4, PDF/UA-1 and PDF/UA-2, encryption, AcroForm fill and flattening, font management, rasterization, compression and linearization.
• Recognition: IronOCR (Tesseract 5, 125+ languages, handwriting at ~90% English); IronBarcode (30+ symbologies); IronQR (ML-powered).
• Utility: IronPrint, IronZIP, IronWebScraper.

Capability Comparison

class DocumentEditorController : Controller
{
    public IActionResult Index()
    {
        ViewBag.DocumentEditorSettings = new DocumentEditorSettings
        {
            Dock = DocumentEditorDock.Fill,
            UserNames = new[] { "iron.user@example.com" },
            ToolbarDocked = true,
            RibbonTabsVisible = true
        };
        return View();
    }
}

class DocumentEditorController : Controller
{
    public IActionResult Index()
    {
        ViewBag.DocumentEditorSettings = new DocumentEditorSettings
        {
            Dock = DocumentEditorDock.Fill,
            UserNames = new[] { "iron.user@example.com" },
            ToolbarDocked = true,
            RibbonTabsVisible = true
        };
        return View();
    }
}

Imports System.Web.Mvc

Public Class DocumentEditorController
    Inherits Controller

    Public Function Index() As ActionResult
        ViewBag.DocumentEditorSettings = New DocumentEditorSettings With {
            .Dock = DocumentEditorDock.Fill,
            .UserNames = New String() {"iron.user@example.com"},
            .ToolbarDocked = True,
            .RibbonTabsVisible = True
        }
        Return View()
    End Function
End Class

using (ServerTextControl tx = new ServerTextControl())
{
    tx.Create();
    tx.Load("invoice-template.tx", StreamType.InternalUnicodeFormat);
    MailMerge mm = new MailMerge { TextComponent = tx };
    var invoice = new
    {
        CustomerName = "Acme Corp",
        InvoiceNumber = "INV-2026-0042",
        Total = 1498.00m,
        Items = new[] { new { Sku = "IRONSUITE", Qty = 1, Price = 1498.00m } }
    };
    mm.MergeObject(invoice);
    tx.Save("invoice.pdf", StreamType.AdobePDF);
}

using (ServerTextControl tx = new ServerTextControl())
{
    tx.Create();
    tx.Load("invoice-template.tx", StreamType.InternalUnicodeFormat);
    MailMerge mm = new MailMerge { TextComponent = tx };
    var invoice = new
    {
        CustomerName = "Acme Corp",
        InvoiceNumber = "INV-2026-0042",
        Total = 1498.00m,
        Items = new[] { new { Sku = "IRONSUITE", Qty = 1, Price = 1498.00m } }
    };
    mm.MergeObject(invoice);
    tx.Save("invoice.pdf", StreamType.AdobePDF);
}

Imports TXTextControl

Using tx As New ServerTextControl()
    tx.Create()
    tx.Load("invoice-template.tx", StreamType.InternalUnicodeFormat)
    Dim mm As New MailMerge With {.TextComponent = tx}
    Dim invoice = New With {
        .CustomerName = "Acme Corp",
        .InvoiceNumber = "INV-2026-0042",
        .Total = 1498.0D,
        .Items = New() {New With {.Sku = "IRONSUITE", .Qty = 1, .Price = 1498.0D}}
    }
    mm.MergeObject(invoice)
    tx.Save("invoice.pdf", StreamType.AdobePDF)
End Using

var doc = new WordDocument();
var heading = new Paragraph();
heading.AddChild(new TextRun("Quarterly Report — Q1 2026") { FontSize = 18, Bold = true });
doc.AddParagraph(heading);
var body = new Paragraph();
body.AddChild(new TextRun("Revenue grew 14% quarter-over-quarter."));
doc.AddParagraph(body);
doc.SaveAs("report.docx");

var doc = new WordDocument();
var heading = new Paragraph();
heading.AddChild(new TextRun("Quarterly Report — Q1 2026") { FontSize = 18, Bold = true });
doc.AddParagraph(heading);
var body = new Paragraph();
body.AddChild(new TextRun("Revenue grew 14% quarter-over-quarter."));
doc.AddParagraph(body);
doc.SaveAs("report.docx");

Dim doc As New WordDocument()
Dim heading As New Paragraph()
heading.AddChild(New TextRun("Quarterly Report — Q1 2026") With {.FontSize = 18, .Bold = True})
doc.AddParagraph(heading)
Dim body As New Paragraph()
body.AddChild(New TextRun("Revenue grew 14% quarter-over-quarter."))
doc.AddParagraph(body)
doc.SaveAs("report.docx")

using (ServerTextControl tx = new ServerTextControl())
{
    tx.Create();
    tx.Load("input.docx", StreamType.WordprocessingML);
    SaveSettings pdfASettings = new SaveSettings
    {
        CreatorApplication = "Internal Reporting",
        Author = "Compliance Team",
        PDFExportSettings = new PDFExportSettings
        {
            PDFAVersion = PDFAVersion.PDFA3B,
            EmbedFonts = true
        }
    };
    tx.Save("output_pdfa3b.pdf", StreamType.AdobePDFA, pdfASettings);
}

using (ServerTextControl tx = new ServerTextControl())
{
    tx.Create();
    tx.Load("input.docx", StreamType.WordprocessingML);
    SaveSettings pdfASettings = new SaveSettings
    {
        CreatorApplication = "Internal Reporting",
        Author = "Compliance Team",
        PDFExportSettings = new PDFExportSettings
        {
            PDFAVersion = PDFAVersion.PDFA3B,
            EmbedFonts = true
        }
    };
    tx.Save("output_pdfa3b.pdf", StreamType.AdobePDFA, pdfASettings);
}

Imports (Assuming necessary namespaces are imported)

Using tx As New ServerTextControl()
    tx.Create()
    tx.Load("input.docx", StreamType.WordprocessingML)
    Dim pdfASettings As New SaveSettings With {
        .CreatorApplication = "Internal Reporting",
        .Author = "Compliance Team",
        .PDFExportSettings = New PDFExportSettings With {
            .PDFAVersion = PDFAVersion.PDFA3B,
            .EmbedFonts = True
        }
    }
    tx.Save("output_pdfa3b.pdf", StreamType.AdobePDFA, pdfASettings)
End Using

// NuGet: Install-Package IronPdf
// Docs: https://ironpdf.com/how-to/pdfa/
using IronPdf;

class Program
{
    static void Main()
    {
        // SaveAsPdfA exports to a PDF/A archival profile.
        // PdfAVersions exposes PdfA1a, PdfA1b, PdfA2a, PdfA2b, PdfA3a, PdfA3b.
        PdfDocument pdf = PdfDocument.FromFile("invoice.pdf");

        // PDF/A-3b is the common archival target for long-term retention.
        pdf.SaveAsPdfA("invoice-archive.pdf", PdfAVersions.PdfA3b);
    }
}

// NuGet: Install-Package IronPdf
// Docs: https://ironpdf.com/how-to/pdfa/
using IronPdf;

class Program
{
    static void Main()
    {
        // SaveAsPdfA exports to a PDF/A archival profile.
        // PdfAVersions exposes PdfA1a, PdfA1b, PdfA2a, PdfA2b, PdfA3a, PdfA3b.
        PdfDocument pdf = PdfDocument.FromFile("invoice.pdf");

        // PDF/A-3b is the common archival target for long-term retention.
        pdf.SaveAsPdfA("invoice-archive.pdf", PdfAVersions.PdfA3b);
    }
}

Imports IronPdf

Module Program
    Sub Main()
        ' SaveAsPdfA exports to a PDF/A archival profile.
        ' PdfAVersions exposes PdfA1a, PdfA1b, PdfA2a, PdfA2b, PdfA3a, PdfA3b.
        Dim pdf As PdfDocument = PdfDocument.FromFile("invoice.pdf")

        ' PDF/A-3b is the common archival target for long-term retention.
        pdf.SaveAsPdfA("invoice-archive.pdf", PdfAVersions.PdfA3b)
    End Sub
End Module

X509Certificate2 cert = new X509Certificate2("signer.pfx", "pfx_password");
DigitalSignature signature = new DigitalSignature(cert, null, "SignatureField1");
SaveSettings settings = new SaveSettings
{
    SignatureFields = new[] { signature }
};
tx.Save("contract_signed.pdf", StreamType.AdobePDF, settings);

X509Certificate2 cert = new X509Certificate2("signer.pfx", "pfx_password");
DigitalSignature signature = new DigitalSignature(cert, null, "SignatureField1");
SaveSettings settings = new SaveSettings
{
    SignatureFields = new[] { signature }
};
tx.Save("contract_signed.pdf", StreamType.AdobePDF, settings);

Imports System.Security.Cryptography.X509Certificates

Dim cert As New X509Certificate2("signer.pfx", "pfx_password")
Dim signature As New DigitalSignature(cert, Nothing, "SignatureField1")
Dim settings As New SaveSettings With {
    .SignatureFields = New DigitalSignature() {signature}
}
tx.Save("contract_signed.pdf", StreamType.AdobePDF, settings)

using (ServerTextControl tx = new ServerTextControl())
{
    tx.Create();
    tx.Load("orders-report-template.tx", StreamType.InternalUnicodeFormat);
    MailMerge mm = new MailMerge { TextComponent = tx };
    mm.Merge(orders, "Orders");
    tx.Save("orders-report.pdf", StreamType.AdobePDF);
}

using (ServerTextControl tx = new ServerTextControl())
{
    tx.Create();
    tx.Load("orders-report-template.tx", StreamType.InternalUnicodeFormat);
    MailMerge mm = new MailMerge { TextComponent = tx };
    mm.Merge(orders, "Orders");
    tx.Save("orders-report.pdf", StreamType.AdobePDF);
}

Imports TXTextControl

Using tx As New ServerTextControl()
    tx.Create()
    tx.Load("orders-report-template.tx", StreamType.InternalUnicodeFormat)
    Dim mm As New MailMerge With {.TextComponent = tx}
    mm.Merge(orders, "Orders")
    tx.Save("orders-report.pdf", StreamType.AdobePDF)
End Using

Why Choose Iron Suite for Document Generation Without WYSIWYG Editing

For the .NET backend team building data-to-document workflows (reports from databases, invoices from line items, statements from accounts, contracts from templates filled programmatically), Iron Suite covers the surface area under one perpetual license. TX Text Control's DocumentEditor frontend earns its keep when end users edit documents in the browser; on backends that never expose an interactive editor, the editor stack remains paid unused capacity.

Specifically, Iron Suite is the better pick when:

• You do not need a browser-based WYSIWYG document editor for end users
• Your workflow is server-side generation: data → PDF, data → DOCX, data → XLSX
• You need OCR + Barcode + QR + Excel + Print + ZIP + WebScraper alongside PDF/Word generation
• You want public perpetual pricing with no per-server runtime fees
• You want one library that runs identically across Windows, Linux, macOS, Docker, Azure, and AWS Lambda

How is Iron Suite Different from TX Text Control .NET Server

• Generalist vs editor specialist: Iron Suite covers PDF, OCR, Barcode, QR, Excel, Word, PowerPoint, Print, ZIP, WebScraper; TX Text Control covers word processing + PDF only.
• Flat per-developer pricing vs per-developer + per-server runtime: Iron Suite from $2,998 with royalty-free deployment; TX from $4,198 single developer + $1,698/year renewal + per-server runtime fees beyond the bundled 2 licenses.
• Iron Suite perpetual use is unconditional once purchased, whereas TX's roughly 40%-of-list annual renewal is the cost of continued updates and support.
• Single bundle vs server core + JS editor + sibling SKUs: Iron Suite is one bundle; TX splits across TXTextControl.Web, TXTextControl.DocumentServer, DocumentEditor JS, WinForms, and WPF SKUs.
• WYSIWYG editing with TX Text Control, where the depth sits. Browser-based document editor for Blazor, Angular, and React, mail merge with master/detail templates, and business-user template authoring are the workloads TX positions itself for. Iron Suite's Word path covers programmatic DOCX generation through IronWord and PDF rendering through IronPDF, different products for different problems.
• No per-server runtime fees: Iron Suite is royalty-free for licensed seats; TX requires runtime licenses for production deployment beyond bundled production count.

Conclusion

For the legal-tech or collaboration-platform team whose end users need to draft, edit, and review documents in the browser, with master/detail mail merge and PDF/A export from the same surface, TX Text Control is the choice. The DocumentEditor frontend and the integrated MailMerge pipeline are workloads TX has built itself around, with the seat-plus-runtime price tag that goes with that depth. For the backend or ISV team whose application generates documents from data, OCRs uploads, reads barcodes, and produces Office and PDF output under one perpetual license, Iron Suite is the choice. From $2,998 at ironsoftware.com/csharp/suite, royalty-free under the base license, no per-server runtime fees.