Iron Suite vs TX Text Control .NET Server

At-a-Glance Comparison

TX Text Control is the word-processing/editor specialist; Iron Suite is the document-automation generalist. Buyers whose application's load-bearing UI is a browser-based WYSIWYG document editor pay TX's seat-plus-runtime model for that depth; buyers whose workflow is server-side document generation get broader category coverage from Iron Suite at a flat per-developer cost.

Pricing and Licensing

TX Text Control .NET Server publishes pricing transparently: Single Developer at {{tx_text_control.single_developer}} perpetual + {{tx_text_control.single_developer_renewal}}/year renewal, Team (4 developers) at {{tx_text_control.team_4_developer}} + {{tx_text_control.team_4_developer_renewal}}/year, Unlimited Deployment at {{tx_text_control.unlimited_deployment}} + {{tx_text_control.unlimited_deployment_renewal}}/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 $liteLicense 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 Iron Suite Redistribution Add-On.

The pricing-model contrast is clear: TX Text Control's developer seat plus runtime-license model produces a higher per-seat baseline and adds deployment-side exposure for production servers beyond the bundled 2 licenses; Iron Suite's flat per-developer model includes royalty-free deployment under the base license. Buyers running TX Text Control across many production servers should model the runtime exposure carefully.

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 ten-product bundle for .NET document automation, sold as a single perpetual license with transparent public pricing. It is positioned for developers and ISVs who want one vendor and one bundle for the everyday document workload, generation, recognition, and utility, rather than negotiating per-developer plus per-server runtime fees for a single document-editing specialist. The base license is royalty-free for the licensed seats, with a separate Redistribution Add-On for SaaS or OEM redistribution beyond the base.

The ten bundled components:

• IronPDF: HTML-to-PDF and PDF manipulation
• IronOCR: image and PDF OCR
• IronBarcode: barcode reading and writing
• IronQR: QR code reading and writing
• IronXL: Excel read/write without Office
• IronWord: Word document generation
• IronPPT: PowerPoint generation
• IronPrint: programmatic printing
• IronZIP: archive creation and extraction
• IronWebScraper: structured web scraping

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

If your application generates documents programmatically (from data to PDF, data to Word, data to Excel) without exposing an interactive document editor to end users, Iron Suite's surface area matches the workload without the cost of a WYSIWYG editor stack you will not deploy. TX Text Control's editor depth is real, but if no end users will ever open a document in a browser editor, you are paying for the editor frontend you will not use.

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 $liteLicense with royalty-free deployment; TX from {{tx_text_control.single_developer}} single developer + {{tx_text_control.single_developer_renewal}}/year renewal + per-server runtime fees beyond the bundled 2 licenses.
• No annual renewal for continued use: Iron Suite perpetual use is unconditional; TX's ~40%-of-list annual renewal is the cost of continued updates.
• 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 lives in TX Text Control: Browser-based document editor for Blazor/Angular/React, mail merge with master/detail templates, business-user template authoring; genuine TX edges Iron Suite does not target.
• 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

TX Text Control .NET Server is the right pick when your application's load-bearing UI surface is a browser-based WYSIWYG document editor. Contract drafting, document collaboration platforms, business-user template authoring, or reporting suites where users design templates interactively. The depth of the DocumentEditor frontend and the MailMerge / PDF/A export pipeline is genuine specialist work TX does better than any generalist suite.

Iron Suite is the right pick when your application is server-side document automation, generating PDFs, OCRing scans, reading barcodes, producing Office output, without an interactive editor for end users. At a published perpetual price starting from $liteLicense, with royalty-free deployment under the base license and no per-server runtime fees. Try the Iron Suite ten-product bundle.