How to Evaluate and Choose an Imaging SDK: Factors Beyond Price
← Back to Blog••8 min read

How to Evaluate and Choose an Imaging SDK: Factors Beyond Price

Introduction

Evaluating imaging SDK factors beyond price for .NET document applications
Evaluating imaging SDK factors beyond price for .NET document applications

Picking a imaging SDK isn’t just about the headline price. It’s about how the kit slides into your architecture, keeps your data safe, and delivers the kind of user experience your enterprise customers expect. The right SDK can shave weeks off development, cut operational risk, and scale with your workload—all while staying inside budget. Below we’ll walk through the most important evaluation criteria and explain why Doconut feels like a natural fit for .NET‑centric, document‑heavy apps.


1. Beyond the Sticker Price: Total Cost of Ownership (considerations)

Why licensing fees are only the beginning

Many vendors shout about low per‑seat rates, but hidden costs can eat that advantage fast. Keep an eye on:

Hidden CostWhat it means for youDoconut’s advantage
Server‑side processing feesIf an SDK forces you to call a cloud service for every conversion, it may add per‑request costs and latency.Doconut renders on the customer’s server, and its optional Converter plugin performs format conversion without sending documents to a third-party rendering service.
Maintenance and upgrade chargesAnnual renewal changes can affect budgets.Doconut provides a 30-day temporary evaluation license so teams can test before purchasing.
Training and onboardingSparse documentation can increase integration time.Doconut exposes a .NET server API and released plugins for annotation, text-layer search, conversion, DICOM, and signing.
Infrastructure overheadSome SDKs require additional services or hosted rendering.Doconut is self-hosted and supports web-farm and distributed deployments; its shared widget store is encrypted at rest with AES-256.

Quick cost‑calculator example

To add Doconut to an ASP.NET Core pipeline you only need a single middleware registration call in your startup code. The viewer and separately licensed plugins should be enabled according to the application’s requirements; OCR is not a Doconut capability.


2. Performance and Scalability: Rendering & Conversion Speed

Real‑world latency matters

Your users will notice even a split‑second pause the moment they click a PDF or CAD file. In high‑throughput portals—think legal case management or engineering drawing archives—those pauses add up to lost productivity.

What to measure

  • Time‑to‑first‑page for PDFs, Office docs, and CAD files.
  • Conversion throughput when turning Word or Excel into PDF on the server.
  • Memory footprint during raster rendering of large DWG files.

Doconut’s performance highlights

  • Benchmark rendering accuracy with representative PDF, Office, and CAD files.
  • Measure conversion throughput with the actual source and output formats your workflow uses.
  • Test CPU, memory, and horizontal scaling on the intended Windows or supported Linux x64 infrastructure.

How Doconut handles document opening and thumbnail generation

When a document is opened, Doconut creates an internal viewer instance that returns a token representing the loaded file. Doconut returns an opaque session token for viewer requests; teams should measure resource use under their expected concurrent load. The same API also provides a method to request thumbnail dimensions for any page, which the viewer can render on demand.


3. Feature Depth That Matters: Annotation, Text-Layer Search, and Conversion

Core capabilities you can’t afford to skip

  • Instant searchable text – users need to find a clause or part number without downloading the file.
  • Annotation tools – reviewers expect highlight, comment, and drawing features directly in the viewer.
  • OCR for scanned images – a legal‑tech platform must turn scanned contracts into searchable PDFs.
  • Controlled printing – regulated industries (healthcare, finance) often require print‑track logs or watermarks.

How Doconut delivers the essentials

FeatureDoconut implementation
Search PluginSearches the document’s existing text layer; it does not OCR scanned images.
Annotation PluginAdds review markup such as annotations to documents.
Converter PluginProvides format-conversion capabilities.
Signer PluginSigns PDF and Word documents in supported releases.

Typical annotation workflow

Developers obtain an annotation manager from the viewer instance, add annotation objects such as stamps or highlights, and then persist the annotation XML back to the document. This pattern requires only a few method calls and works consistently across all supported formats.


4. Security, Compliance, and Deployment Flexibility for .NET

Data residency and regulatory pressure

Enterprises in finance, healthcare, and legal tech can’t send documents to a SaaS endpoint for rendering. They need on‑premises processing, audit trails, and the ability to lock down printing or exporting.

Doconut’s security posture

  • Self-hosted rendering – documents are rendered inside the customer’s infrastructure rather than sent to a third-party service.
  • Offline licensing – Doconut uses offline .lic licensing and can work in air-gapped environments.
  • Application-owned controls – the customer remains responsible for data-residency policy, access control, job processing, and storage.

Loading a license securely

At application startup you read the license XML from a protected location (for example, a file stored in a secure folder or a secret store) and pass the stream to the Doconut viewer instance. The SDK validates the license and will refuse to render if the license is missing or tampered with, ensuring that only authorized deployments can use the protected features.

Deployment options

  • Supported server platforms – Windows x64/x86, plus glibc-based Linux x64 for .NET 8 and .NET 6, including Docker on Linux x64.
  • Distributed deployment – Doconut supports web farms, and the shared widget store is encrypted at rest with AES-256.

5. Developer Experience: Integration Simplicity, Documentation, and Free Trial

What senior developers really care about

  • Minimal boilerplate – a few lines of code should get you from zero to a full‑featured viewer.
  • Clear API surface – predictable method names reduce the learning curve.
  • Hands‑on evaluation – a 30-day temporary license lets you test supported formats and licensed plugins in a real project.

Doconut’s developer‑first approach

  • .NET server API – Doconut provides a C#/VB server API for supported ASP.NET application models.
  • Released plugins – Annotation, Search, Converter, DICOM, and Signer extend the viewer for specific workflows.
  • Evaluation license – request a 30-day temporary license and test the SDK with representative files.

Getting a Doconut‑enabled .NET 6 web app up and running

Create a new ASP.NET Core project, add the Doconut NuGet package, register the required services (distributed cache and HTTP context accessor), and then add the Doconut middleware to the request pipeline. After configuration, test the viewer with the required files from Doconut’s 75 supported extensions across 18 format families. Integration time depends on the application, selected plugins, and deployment environment.


Key Takeaways

  • Total Cost of Ownership matters more than the headline price; Doconut’s on‑premise model eliminates per‑document fees.
  • Performance should be measured with representative files and infrastructure.
  • Feature depth includes released plugins for annotation, text-layer search, conversion, DICOM, and signing.
  • Self-hosting keeps rendering inside customer-controlled infrastructure, while security and compliance remain customer responsibilities.
  • Developer experience should be evaluated with Doconut’s .NET server API, documentation, samples, and 30-day temporary evaluation license.
  • Scalability works with any .NET hosting model, from on‑prem servers to Docker‑based microservices.
  • Future‑proofing is assured through regular updates and .NET 6 dependency optimization.

Common Questions

Q1: Does Doconut require a separate rendering server or third‑party cloud service? A: No. All rendering and conversion happen inside your .NET process. You only need to add the Doconut middleware and reference the SDK libraries.

Q2: Can I use Doconut with containerized .NET applications? A: Yes, with the .NET 8 and .NET 6 packages on glibc-based Linux x64 images such as Debian or Ubuntu. Alpine and other musl-based images are not supported.

Q3: Can Doconut search scanned images with OCR? A: No. Doconut does not currently provide OCR. The Search plugin works only with a document’s existing text layer.

Q4: Is there a way to evaluate Doconut before buying? A: Yes. Request a 30-day temporary evaluation license and confirm which packages and plugins are included before testing.


Conclusion

When the decision comes down to price versus value, the smartest enterprises look beyond the sticker and evaluate performance, security, feature completeness, and developer productivity. Doconut provides a self-hosted .NET viewer with broad format coverage and optional plugins for annotation, text-layer search, conversion, DICOM, and signing.

Request a 30-day temporary evaluation license, follow the documentation for the selected package, and test representative documents before making a production decision.

Explore Doconut →

#.NET#Imaging SDK#Document Viewer#Enterprise Development#Software Architecture