COMPARISON

Iron Suite vs Accusoft ImageGear + PrizmDoc

Accusoft ImageGear + PrizmDoc is a modular SDK split across two product lines, in-process ImageGear for .NET plus server-hosted PrizmDoc, with separately licensed add-ons (Recognition, Barcode, PDF, DICOM) and quote-only commercial pricing layered with per-deployment runtime fees. Iron Suite is a single ten-product bundle sold at a published perpetual price from $2,998, royalty-free on the licensed seats, with a single Redistribution Add-On for SaaS or OEM redistribution beyond the base. Total cost exposure is therefore very different: Accusoft scales with developer seats, ImageGear deployment count, and PrizmDoc Server VM count; Iron Suite scales with developer count alone.

This comparison leads with what a procurement-led decision actually hangs on: how each suite is priced, what the license covers, and whether a separate server VM has to be operated. The product descriptions and capability code follow below for the engineers who will ship the integration.

At-a-Glance Comparison

DimensionAccusoft ImageGear + PrizmDocIron Suite
Pricing positioningQuote-only, no public list priceLite $2,998 / Plus $4,498 / Professional $8,998 / Unlimited $17,998 (Enterprise custom). All 10 products for the price of 2, save 80%
License modelQuote-only commercial + deployment/runtime fees; OEM + SaaS licensingPerpetual per-developer, royalty-free base; Redistribution Add-On for SaaS/OEM
Components in bundleImageGear .NET family + PrizmDoc Server + PrizmDoc Viewer + optional DICOM10 Iron products as a single bundle
Format/capability coverageImaging + PDF + OCR + Barcode + HTML5 viewer + 100+ format conversion + Annotation + Redaction + FormsPDF + OCR + Barcode + QR + Excel + Word + PowerPoint + Print + ZIP + WebScraper
Cross-platform / cloudImageGear Windows-centric; PrizmDoc Server runs Windows + LinuxWindows / Linux / macOS / Docker / Azure / AWS Lambda
.NET runtime support.NET Standard 2.0 base (.NET 5–10, Core 2.0–3.1, Framework 4.6.1–4.8.1) for ImageGear.Core.NET Framework 4.6.2+, .NET Core, .NET 6/7/8/9
Target marketEnterprise ISVs in legal, healthcare, gov building document viewer/processing portals.NET developers and ISVs needing one vendor for everyday document automation
VendorAccusoft Corporation (Apryse subsidiary since 2025-07-10)Iron Software

The two suites overlap on imaging, PDF, and OCR, but diverge sharply on architecture: Accusoft fits enterprise ISVs that genuinely need both in-process imaging and a hosted HTML5 multi-format viewer, while Iron Suite fits .NET teams that want one in-process bundle covering PDF, Office, recognition, and utility without standing up a viewer/conversion server stack.

Pricing and Licensing

Accusoft ImageGear + PrizmDoc are sold quote-only. There is no public list price for either product line. The model is per-developer for the SDK seats plus deployment/runtime fees that scale with production servers and SaaS deployment counts. OEM tiers are available at higher pricing. Procurement requires sales engagement and the total cost of ownership depends on modeling developer seats, in-process ImageGear deployment count, and PrizmDoc Server VM count together.

Iron Suite ships at $2,998 for the entry tier, marketed as "all 10 products for the price of 2, save 80%". 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 separate runtime/server license is required for the base deployment. SaaS or OEM redistribution beyond the base requires the separate Redistribution Add-On.

The pricing-model contrast is significant: Accusoft adds deployment-side runtime fees plus PrizmDoc Server VM costs on top of developer seats, with the quote cycle adding procurement time; Iron Suite ships at a flat per-developer cost with royalty-free in-process deployment. Buyers running document workflows across many production environments should model Accusoft's combined exposure carefully against Iron Suite's flat cost.

What is Accusoft ImageGear + PrizmDoc

Accusoft's developer SDKs come in two complementary product lines. ImageGear for .NET is the in-process imaging/PDF/OCR toolkit: load, process, and write images and PDFs from a .NET application. PrizmDoc is the server-based stack: PrizmDoc Server runs as a service (Windows or Linux) and powers PrizmDoc Viewer, a browser-based HTML5 multi-format document viewer with annotation, redaction, and conversion. Accusoft was acquired by Apryse on 2025-07-10, with the Accusoft brand and product lines retained post-acquisition.

Key bundled components:

  • ImageGear .NET (Core, All): imaging, format conversion, image processing
  • ImageGear PDF / PdfReader: PDF creation, editing, rasterization
  • ImageGear Recognition: OCR add-on for searchable PDF output
  • ImageGear Barcode: 1D/2D barcode reading and writing
  • PrizmDoc Server: server-side document conversion + 100+ format viewer engine
  • PrizmDoc Viewer: browser-based HTML5 viewer with annotation/redaction UI
  • DICOM add-on for medical imaging (optional)

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) in one in-process .NET package rather than deploying a separate viewer/conversion server. 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:

Capability Comparison

Imaging

ImGearEvaluationManager.Initialize();
ImGearCommonFormats.Initialize();
using (FileStream fs = new FileStream("scan.tif", FileMode.Open))
{
    ImGearPage page = ImGearFileFormats.LoadPage(fs, 0);
    ImGearProcessing.Despeckle(page, ImGearDespeckleType.SmallNoise);
    ImGearProcessing.AutoOrient(page);
    using (FileStream outFs = new FileStream("scan-clean.jpg", FileMode.Create))
        ImGearFileFormats.SavePage(page, outFs, 0, ImGearSavingModes.OVERWRITE,
            ImGearSavingFormats.JPG, null);
}
ImGearEvaluationManager.Initialize();
ImGearCommonFormats.Initialize();
using (FileStream fs = new FileStream("scan.tif", FileMode.Open))
{
    ImGearPage page = ImGearFileFormats.LoadPage(fs, 0);
    ImGearProcessing.Despeckle(page, ImGearDespeckleType.SmallNoise);
    ImGearProcessing.AutoOrient(page);
    using (FileStream outFs = new FileStream("scan-clean.jpg", FileMode.Create))
        ImGearFileFormats.SavePage(page, outFs, 0, ImGearSavingModes.OVERWRITE,
            ImGearSavingFormats.JPG, null);
}
Imports System.IO

ImGearEvaluationManager.Initialize()
ImGearCommonFormats.Initialize()
Using fs As New FileStream("scan.tif", FileMode.Open)
    Dim page As ImGearPage = ImGearFileFormats.LoadPage(fs, 0)
    ImGearProcessing.Despeckle(page, ImGearDespeckleType.SmallNoise)
    ImGearProcessing.AutoOrient(page)
    Using outFs As New FileStream("scan-clean.jpg", FileMode.Create)
        ImGearFileFormats.SavePage(page, outFs, 0, ImGearSavingModes.OVERWRITE, ImGearSavingFormats.JPG, Nothing)
    End Using
End Using
$vbLabelText   $csharpLabel

Iron Suite does not provide a direct equivalent for a standalone imaging-processing API (despeckle, auto-orient as independent primitives). IronOCR includes deskew and denoise baked into its input pipeline, but they are not exposed as a general-purpose imaging API. For applications that need standalone imaging processing, applying filters to images outside of an OCR flow, ImageGear is the purpose-built option.

PDF Processing

ImGearFileFormats.Filters.Add(ImGearPDF.CreatePDFFormat());
ImGearPDF.Initialize();
using (FileStream pdfStream = new FileStream("input.pdf", FileMode.Open))
{
    ImGearPDFDocument pdfDoc = (ImGearPDFDocument)ImGearFileFormats.LoadDocument(pdfStream);
    for (int i = 0; i < pdfDoc.Pages.Count; i++)
    {
        ImGearPage page = pdfDoc.Pages[i];
        using (FileStream outFs = new FileStream($"page_{i + 1}.png", FileMode.Create))
            ImGearFileFormats.SavePage(page, outFs, 0, ImGearSavingModes.OVERWRITE,
                ImGearSavingFormats.PNG, null);
    }
}
ImGearPDF.Terminate();
ImGearFileFormats.Filters.Add(ImGearPDF.CreatePDFFormat());
ImGearPDF.Initialize();
using (FileStream pdfStream = new FileStream("input.pdf", FileMode.Open))
{
    ImGearPDFDocument pdfDoc = (ImGearPDFDocument)ImGearFileFormats.LoadDocument(pdfStream);
    for (int i = 0; i < pdfDoc.Pages.Count; i++)
    {
        ImGearPage page = pdfDoc.Pages[i];
        using (FileStream outFs = new FileStream($"page_{i + 1}.png", FileMode.Create))
            ImGearFileFormats.SavePage(page, outFs, 0, ImGearSavingModes.OVERWRITE,
                ImGearSavingFormats.PNG, null);
    }
}
ImGearPDF.Terminate();
Imports System.IO

ImGearFileFormats.Filters.Add(ImGearPDF.CreatePDFFormat())
ImGearPDF.Initialize()

Using pdfStream As New FileStream("input.pdf", FileMode.Open)
    Dim pdfDoc As ImGearPDFDocument = CType(ImGearFileFormats.LoadDocument(pdfStream), ImGearPDFDocument)
    For i As Integer = 0 To pdfDoc.Pages.Count - 1
        Dim page As ImGearPage = pdfDoc.Pages(i)
        Using outFs As New FileStream($"page_{i + 1}.png", FileMode.Create)
            ImGearFileFormats.SavePage(page, outFs, 0, ImGearSavingModes.OVERWRITE, ImGearSavingFormats.PNG, Nothing)
        End Using
    Next
End Using

ImGearPDF.Terminate()
$vbLabelText   $csharpLabel

IronPDF starts from HTML and generates PDFs:

var renderer = new ChromePdfRenderer();
string html = @"<h1>Invoice 2026-0428</h1><p>Customer: Acme Corp</p><p>Total due: $1,240.00</p>";
using var pdf = renderer.RenderHtmlAsPdf(html);
pdf.SaveAs("invoice.pdf");
var renderer = new ChromePdfRenderer();
string html = @"<h1>Invoice 2026-0428</h1><p>Customer: Acme Corp</p><p>Total due: $1,240.00</p>";
using var pdf = renderer.RenderHtmlAsPdf(html);
pdf.SaveAs("invoice.pdf");
Dim renderer As New ChromePdfRenderer()
Dim html As String = "<h1>Invoice 2026-0428</h1><p>Customer: Acme Corp</p><p>Total due: $1,240.00</p>"
Using pdf = renderer.RenderHtmlAsPdf(html)
    pdf.SaveAs("invoice.pdf")
End Using
$vbLabelText   $csharpLabel

ImageGear treats PDF as a registered format filter in its imaging stack; ImGearPDFDocument exposes pages, and you save them through the imaging encoder pipeline. IronPDF treats PDF as the primary citizen, generated from HTML/CSS via a Chromium-class engine. For rasterizing inbound PDFs as part of an imaging workflow, ImageGear fits its model; for generating new PDFs from structured data, IronPDF is more direct.

OCR

ImGearFileFormats.Filters.Add(ImGearPDF.CreatePDFFormat());
ImGearPDF.Initialize();
using (ImGearRecognition recog = new ImGearRecognition())
{
    recog.Languages.EnableLanguages(ImGearRecLanguages.English);
    using (FileStream input = new FileStream("scan.tif", FileMode.Open))
    {
        ImGearRecPage page = recog.ImportPage(input, 0);
        page.Recognize();
        using (FileStream output = new FileStream("searchable.pdf", FileMode.Create))
            page.Output.PageToPDF(output, ImGearPDFOutputType.SearchablePDF);
    }
}
ImGearPDF.Terminate();
ImGearFileFormats.Filters.Add(ImGearPDF.CreatePDFFormat());
ImGearPDF.Initialize();
using (ImGearRecognition recog = new ImGearRecognition())
{
    recog.Languages.EnableLanguages(ImGearRecLanguages.English);
    using (FileStream input = new FileStream("scan.tif", FileMode.Open))
    {
        ImGearRecPage page = recog.ImportPage(input, 0);
        page.Recognize();
        using (FileStream output = new FileStream("searchable.pdf", FileMode.Create))
            page.Output.PageToPDF(output, ImGearPDFOutputType.SearchablePDF);
    }
}
ImGearPDF.Terminate();
Imports System.IO

ImGearFileFormats.Filters.Add(ImGearPDF.CreatePDFFormat())
ImGearPDF.Initialize()
Using recog As New ImGearRecognition()
    recog.Languages.EnableLanguages(ImGearRecLanguages.English)
    Using input As New FileStream("scan.tif", FileMode.Open)
        Dim page As ImGearRecPage = recog.ImportPage(input, 0)
        page.Recognize()
        Using output As New FileStream("searchable.pdf", FileMode.Create)
            page.Output.PageToPDF(output, ImGearPDFOutputType.SearchablePDF)
        End Using
    End Using
End Using
ImGearPDF.Terminate()
$vbLabelText   $csharpLabel

IronOCR compresses the same workflow:

var ocr = new IronTesseract();
using var input = new OcrInput("scanned-document.png");
input.Deskew();
input.DeNoise();
var result = ocr.Read(input);
Console.WriteLine($"Confidence: {result.Confidence}");
var ocr = new IronTesseract();
using var input = new OcrInput("scanned-document.png");
input.Deskew();
input.DeNoise();
var result = ocr.Read(input);
Console.WriteLine($"Confidence: {result.Confidence}");
Imports IronTesseract

Dim ocr As New IronTesseract()
Using input As New OcrInput("scanned-document.png")
    input.Deskew()
    input.DeNoise()
    Dim result = ocr.Read(input)
    Console.WriteLine($"Confidence: {result.Confidence}")
End Using
$vbLabelText   $csharpLabel

Both produce searchable PDF from a scanned image. ImageGear exposes lifecycle (ImGearPDF.Initialize / ImGearPDF.Terminate), explicit language enabling, and page-import/output-to-PDF as separate calls. IronOCR is opinionated. For workloads sitting inside an existing ImageGear imaging pipeline, the ImageGear OCR fits naturally; for standalone OCR with preprocessing built in, IronOCR ships faster.

HTML5 Viewer (PrizmDoc)

PrizmDoc's hosted viewer is the structural edge Iron Suite does not match. A .NET client calls PrizmDoc Server to create a viewing session, then embeds the resulting URL in a browser iframe.

var client = new PrizmDocServerClient(
    baseUrl: "https://prizmdoc.example.local",
    apiKey: "YOUR_PRIZMDOC_API_KEY");
ViewingSession session = await client.CreateViewingSessionAsync(
    new CreateViewingSessionOptions { Source = new FileSource("contract.pdf") });
Console.WriteLine($"Viewer URL: https://prizmdoc.example.local/viewer.html?viewingSessionId={session.ViewingSessionId}");
var client = new PrizmDocServerClient(
    baseUrl: "https://prizmdoc.example.local",
    apiKey: "YOUR_PRIZMDOC_API_KEY");
ViewingSession session = await client.CreateViewingSessionAsync(
    new CreateViewingSessionOptions { Source = new FileSource("contract.pdf") });
Console.WriteLine($"Viewer URL: https://prizmdoc.example.local/viewer.html?viewingSessionId={session.ViewingSessionId}");
Imports System

Dim client = New PrizmDocServerClient(
    baseUrl: "https://prizmdoc.example.local",
    apiKey: "YOUR_PRIZMDOC_API_KEY")

Dim session As ViewingSession = Await client.CreateViewingSessionAsync(
    New CreateViewingSessionOptions With {.Source = New FileSource("contract.pdf")})

Console.WriteLine($"Viewer URL: https://prizmdoc.example.local/viewer.html?viewingSessionId={session.ViewingSessionId}")
$vbLabelText   $csharpLabel

Iron Suite does not provide a direct equivalent for a hosted multi-format HTML5 viewer with annotation/redaction UI. Iron Suite users who need browser-based viewing typically rasterize PDF pages with IronPDF and serve those images, or embed PDFs in browsers via the native browser PDF viewer. For DMS, contract review, and gov/legal portals where users need to view DOCX, XLSX, TIFF, email, and CAD-subset formats in a unified browser viewer, PrizmDoc is the purpose-built option.

Format Conversion (PrizmDoc Server)

PrizmDocServerClient prizm = new PrizmDocServerClient(
    "https://prizmdoc.example.local", "YOUR_PRIZMDOC_API_KEY");
ConversionResult[] results = await prizm.ConvertAsync(
    input: "contract.docx",
    destinationOptions: new DestinationOptions(DestinationFileFormat.Pdf));
foreach (ConversionResult r in results)
    await r.RemoteWorkFile.SaveAsync($"converted_{r.PageCount}p.pdf");
PrizmDocServerClient prizm = new PrizmDocServerClient(
    "https://prizmdoc.example.local", "YOUR_PRIZMDOC_API_KEY");
ConversionResult[] results = await prizm.ConvertAsync(
    input: "contract.docx",
    destinationOptions: new DestinationOptions(DestinationFileFormat.Pdf));
foreach (ConversionResult r in results)
    await r.RemoteWorkFile.SaveAsync($"converted_{r.PageCount}p.pdf");
Imports System.Threading.Tasks

Dim prizm As New PrizmDocServerClient("https://prizmdoc.example.local", "YOUR_PRIZMDOC_API_KEY")
Dim results As ConversionResult() = Await prizm.ConvertAsync(input:="contract.docx", destinationOptions:=New DestinationOptions(DestinationFileFormat.Pdf))
For Each r As ConversionResult In results
    Await r.RemoteWorkFile.SaveAsync($"converted_{r.PageCount}p.pdf")
Next
$vbLabelText   $csharpLabel

Iron Suite's conversion flow runs in-process. PrizmDoc Server's 100+ format conversion runs as a server job, which fits architectures where many client applications share a centralised conversion service, but requires deploying and operating PrizmDoc Server (Windows or Linux VM + service infrastructure). For applications that need in-process conversion without a server dependency, IronPDF + IronWord + IronXL cover the common cases; for centralised conversion services across a fleet of client apps, PrizmDoc's hub architecture fits better.

Why Choose Iron Suite for In-Process Document Manipulation

If your application generates and processes documents inside a .NET process, rather than offering a browser-based multi-format viewer to end users, Iron Suite's surface area matches the workload without standing up a separate PrizmDoc Server stack. Accusoft's two-product architecture makes sense when you need both in-process imaging and a hosted viewer; if you only need the in-process side, you are paying for half a product line you will not deploy.

Specifically, Iron Suite is the better pick when:

  • Your application is server-side document automation, not a browser-based viewer portal
  • You want one in-process .NET library, not an additional PrizmDoc Server VM to operate
  • You need cross-cutting document coverage: PDF + Word + Excel + PowerPoint + OCR + Barcode + Print + ZIP in one bundle
  • You want public perpetual pricing with no deployment/runtime fees
  • You want cross-platform parity (Windows / Linux / macOS / Docker / Azure / AWS Lambda)

How is Iron Suite Different from Accusoft ImageGear + PrizmDoc

  • One in-process library vs in-process + server stack: Iron Suite is purely in-process; Accusoft requires standing up PrizmDoc Server (Windows or Linux VM + service) for hosted viewer/conversion features.
  • Public perpetual pricing from $2,998 vs quote-only: Iron Suite is published-price; Accusoft is quote-only across both product lines.
  • Single bundle covers Office + Print + ZIP + WebScraper: Iron Suite ships Excel, Word, PowerPoint, Print, ZIP, WebScraper alongside PDF/OCR/Barcode; ImageGear's coverage is imaging-first with PDF/OCR/Barcode add-ons.
  • No deployment/runtime fees: Iron Suite is royalty-free for licensed seats; Accusoft layers per-deployment fees on top.
  • Cross-platform parity: Iron Suite supports Linux, macOS, Docker, Azure, AWS Lambda equivalently; ImageGear is Windows-centric (PrizmDoc Server has Linux support, but ImageGear is Windows-native).
  • Hosted HTML5 viewer + DICOM live in Accusoft: PrizmDoc's browser viewer and ImageGear's DICOM add-on are genuine Accusoft edges Iron Suite does not target.

Conclusion

Accusoft ImageGear + PrizmDoc is the right pick when your application needs both an in-process imaging library and a server-hosted HTML5 viewer with annotation, redaction, and 100+ format conversion: typically DMS, contract review, healthcare records portals, or gov/legal collaboration platforms. The two-product architecture is purposeful when both sides of the surface are exercised.

Iron Suite is the right pick when your application is server-side document automation (generating PDFs, OCRing scans, reading barcodes, producing Office output, printing, zipping, scraping) in one in-process .NET bundle without a separate server stack to deploy and operate. At a published perpetual price starting from $2,998, with royalty-free deployment under the base license. Try the bundle at Iron Software's .NET Suite.

Please noteAccusoft ImageGear and PrizmDoc are registered trademarks of their respective owners. This site is not affiliated with, endorsed by, or sponsored by Accusoft. All product names, logos, and brands are property of their respective owners. Comparisons are for informational purposes only and reflect publicly available information at the time of writing.