Can you import our FlexiCapture document definitions?

Not today. Field sets, zones and validations are rebuilt here — the same work the Vantage path asks of you. What shortens it is blueprint provisioning and model-assisted template authoring: drop in a sample page, get a draft template with zones and data types, correct it, train it.

Is Tesseract going to lose against the ABBYY engine?

On degraded scans and dense forms, yes, measurably. That is why the hybrid path exists: Tesseract first, low-confidence words or pages re-read by a vision model. Settle it with a bake-off on your own documents — we publish the fields we lose.

We run ICR-heavy forms. Should we switch?

Probably not on that use case alone. Handwriting runs through the model path here, which carries a cost per page and a latency the traditional engines do not. We price it honestly rather than pretending the gap is closed.

Vantage has pre-trained skills. What do we get on day one?

A blueprint — finance, accounts payable, insurance, KYC, anti-money-laundering or supply chain — that provisions the project, workflow, routing, upload endpoint, export goal and a full field set in one action. That is a pre-authored field set, not a pre-trained model: you still author the template, with a model drafting it from a sample page. We would rather state that plainly than lose the pilot.

Can we run entirely offline?

Yes. Tesseract for text and a local GGUF vision model through a managed llama-server cover recognition with no outbound network. Vantage cannot run offline.

How does the cost curve actually compare?

Below roughly 100–150k pages a year, a metered platform is often cheaper than running infrastructure — we say so. Above it the gap widens every year, and for a service provider with twenty clients on one install it is not close.

Can you match its pages per hour?

Not as a blanket claim. Throughput here scales by adding nodes that declare the workflow duty, and the honest answer for any given box is a benchmark on your hardware and your paper. We run it before quoting volume.

Is your PDF/A really PDF/A?

The renditions assert PDF/A-2b with an sRGB output intent and PDF/A identification in XMP, built with PDFBox from stored page images and persisted word geometry. Archive buyers audit that claim, and we encourage validating a sample set with veraPDF as part of acceptance.

We already run TotalAgility for process automation. Why change capture?

You may not need to. The strongest shape is often capture here, feeding your existing orchestration through REST, JDBC, message bus or file drop — you keep the process estate and stop paying capture volume fees.

Does anything replace VRS?

The pre-processing chain covers deskew, despeckle, binarize, crop, line and punch-hole removal and colour dropout, ordered per project. VRS remains the benchmark on hostile paper; on ordinary departmental scanning the difference rarely survives a bake-off.

Do we have to draw a template for every supplier?

No. A template carries alternatives for layouts that differ, label search finds fields that move, and the model paths read documents you have not templated at all. Where a template does earn its keep is auditability: the same input produces the same output, and the field says which method produced it.

Can you learn from corrections the way Rossum does?

Templates train from operator corrections, and the verification hub's word-group mode applies one correction everywhere the same misread text appears. It is a different mechanism from a continuously retrained global model, and it stays inside your tenant.

We are happy with ChronoScan. When should we move?

When a second operator, a second client, an audit requirement or a compliance question arrives. Those are the four triggers we see — not features.

Is this overkill for one mailroom?

Possibly, and we will say so on the call. A single-machine install runs fine here, but if you will never need users, tenants, workflow or audit, the cheaper tool is the right tool.

Why would we leave a platform that works?

Usually one of three reasons: the renewal, a tenancy requirement Transact cannot meet, or a mandate to run models locally. If none of those apply, staying is a defensible answer and we will say so.

Our developers say they can wire this up in a sprint.

The recognition call, yes. The forty-odd capabilities around it — batch assembly, separator handling, template versioning, validation rules, an operator review UI, retries, retention, audit, tenant isolation, export mapping — are the sprint that never ends. Ask what happens when the person who wrote it leaves.

Can we use Textract as an engine here?

Recognition is pluggable and the plugin SDK exists for exactly this. Most teams end up local for volume and remote for the hard pages.

So you will not quote against ReadSoft for AP?

Not on SAP-native accounts payable with live master-data matching. We will quote for the other 70% of the documents in the building, and we will say the same thing on the first call as on the last.

Pricing

One licence for the deployment. None for your documents.

Capture pricing normally has four dials: pages, stations, modules and users. We use one — the deployment. Add operators, add projects, add tenants, double your volume: the licence does not move. What moves is your infrastructure bill, and you can see it.

Single site

One node, one organisation

All hubs, all import and export lanes, all recognition engines. Unlimited pages, documents and operators. Updates and second-line support included.

Flat annual licence · quoted per deployment

Cluster

Duty-aware nodes, HA

Everything in single site, plus clustering: dedicated import, workflow and export nodes, GPU boxes for local models, and rolling upgrades. Still no page meter.

Flat annual licence · quoted per cluster

Service provider & OEM

Many tenants, or embedded in your product

Multi-tenant operation for BPOs and MSPs, embedded scanning and verification hubs behind API keys, white-label chrome, and partner margins. See Partners.

Per-tenant or revenue-share · agreed with the partner

Prefer not to run it yourself? Managed hosting, implementation, migration, training and support are all available — quoted separately, on request. Nothing on this page includes them.

What the alternatives cost, from public sources

Read this carefully: the figures below are published list bands, analyst-reported contract benchmarks and vendor pricing pages checked in August 2026. They are not quotes, and your negotiated price will differ. We publish them because every buyer we meet has already found them.

Platform	Licence shape	Typical annual outlay	Marginal page cost	Ops burden
KognitCapture	Self-hosted, no runtime gate	Infrastructure + your team	$0 local · tokens only if you choose remote	You run it
ABBYY FlexiCapture 12	Pages + stations + modules	$15k – $150k+	Metered	Windows estate + integrator
ABBYY FineReader Server	Volume / core tiers	$10k – $60k	Metered	Moderate
ABBYY Vantage	Transactions / documents	Median ≈ $150k	≈ $0.02 – $0.10	Vendor-managed
Kofax / Tungsten	Users + modules + volume	$50k – $500k	Metered	Heavy; services $20k–150k+
ReadSoft	Invoice volume + SAP add-on	Enterprise contract	Per invoice	SAP Basis + AP team
Rossum	Annual subscription by volume	From $18k	Per document	Vendor-managed
Amazon Textract + glue	Pay per page, no floor	≈ $3k at 2M pages, text only	$1.50–$15 per 1k pages	You build and own the platform
ChronoScan	Perpetual, per workstation / server	From ≈ €245	$0 (your own AI keys)	Light, single machine

Cost model

Illustrative, not a quote. Metered figures use the public $0.02–0.10 per-page band plus a platform floor; the self-hosted line assumes three commodity nodes, PostgreSQL, no GPU, and a fraction of an engineer's time. One column grows with volume. The other does not.

Start from

Annual page volume

pages

Client organisations on the install

organisations

Verification operators (seats)

seats

Station and user licences are what most capture vendors charge for. Here they are free.

Recognition mode

Your annual revenue

€

€60 000 0.05 % of revenue · per tenant

Our licence is a share of your revenue, not a count of your pages: 0.6 % up to €200k of turnover, falling to 0.05 % at scale — and halved for every organisation above €100k revenue. Minimum €300 a year. Above €500M we quote.

Three-year saving, at the top of the range —

Projected saving against each alternative most expensive first

—Year-one difference

—Our cost per 1 000 pages

—Cheaper from month

—Cheaper over three years

Cumulative spend, months 0–36

Option	Year one	Three years	Marginal page cost	What moves the number

What running it yourself actually costs

The self-hosted line above is not a black box. At your volume it breaks down like this — and if your estate already has the capacity, most of these lines are already paid for.

Line	What it is	Per year

Send me this model Put it to the test on your documents

Not binding, and deliberately conservative. Competitor figures are published list bands and analyst-reported benchmarks applied to the numbers you set here; your negotiated price will differ. The self-hosted column is infrastructure and your own team only — it does not include cloud hosting, a managed service, implementation, migration, training, support, or the bake-off and pilot engagements — all of those are consulting work, quoted separately and billed at our standard rate. We would rather you argued with this model than took it on trust.