Pricing

A fixed annual licence. Not a meter on your document flow.

DocxIntel is licensed by deployment footprint — how many environments, how many GPU workers, what level of redundancy and support. Page volume is not an input. Process ten thousand pages or ten million; the licence is the same, and reprocessing your archive costs nothing extra.

No per-page charge
Unmetered reprocessing
All six capabilities included
Air-gapped installs included

DocxIntel licence model illustration showing a fixed annual licence covering unlimited document volume

Fixed
Annual licence: Unmetered
Pages processed: 6 of 6
Capabilities included: $0
Marginal cost per page

The licence figure itself is quoted per deployment after a sizing call. Everything that determines that figure is listed on this page, and the Proof of Value fee and conversion price are both fixed in writing before any work begins.

Straight answer

Why there is no price list on this page.

We would rather explain the pricing model honestly than publish a table that would be wrong for most readers. A licence covers a specific deployment, and deployments are not interchangeable — so the number is quoted after we know what we are deploying, and it is fixed in writing before you commit anything.

A single-node departmental install and a dual-site high-availability estate are different engineering jobs with different licence figures
Nothing about the figure depends on your page volume, so nothing about it changes when your volume changes
The fixed Proof of Value fee and the conversion price to a full licence are agreed in writing before the Proof of Value starts
You are never quoted a rate that scales with success — automating more documents does not increase what you pay

If a published number matters more to you than a sized one, the arithmetic further down this page will tell you roughly where metered alternatives land at your volume.

Private cloud deployment topology for DocxIntel showing GPU workers, storage and API gateway inside the customer VPC

What the licence covers

One licence, the whole platform, no volume clauses

There is no capability tier, no page bundle and no feature that unlocks at a higher spend. Everything below is included in every DocxIntel licence.

All six capabilities

Analyse, Identify, Classify, Map, Modify and Ask are one platform, not six SKUs. You do not buy classification and then discover redaction is an add-on.

No per-capability licensing
One API surface
One upgrade path

Unlimited page and document volume

No page allowance, no credit balance, no overage rate. Reprocessing a two-million-page archive after a model update or a schema change costs nothing beyond the compute you already own.

No page counters
No credit ledger
Full-archive reprocessing included

Open-weight models in the bundle

Layout, OCR, table-structure, classification and language models ship inside the deployment bundle and run on your GPUs. You hold the weights, and nothing loads from an external registry at runtime.

Weights delivered with the release
Checksummed model bundles
No external inference calls

See what's in the box

Every deployment model

Air-gapped, private cloud, managed single-tenant and evaluation sandbox are all licensable footprints. Air-gapped operation is not reserved for a top tier — it is the default assumption.

Fully air-gapped supported
Kubernetes or Docker Compose
Bare metal or your own cloud

Compare deployment models

Updates within the support window

Security patches, bug-fix releases, model bundle refreshes and upgrade runbooks are published throughout the support window, packaged for offline installation as well as connected ones.

Security and bug-fix releases
Model bundle updates
Offline upgrade runbooks

Reviewer and administrator seats

Human-in-the-loop review is part of the product, so reviewer seats are not metered either. Add the whole operations team to the review queue without a seat conversation.

Unmetered reviewer seats
Role-based access control
SSO via OIDC or SAML

What moves the number

The five things that actually determine your licence

Every input to a DocxIntel quotation is a property of the deployment. None of them is a property of your document volume.

Deployment footprint

Environments: Production, disaster recovery, user acceptance testing and development are counted separately. Most estates license production plus one non-production environment.
Sites and regions: A second physical site or a second regulated jurisdiction is a second footprint, because it is a second install to support and patch.
Deployment model: Air-gapped, private cloud, managed single-tenant or evaluation sandbox. Air-gapped installs carry more offline packaging and runbook work; managed single-tenant includes operational responsibility.

Compute and resilience

GPU worker count: The primary capacity input. Workers set your pages-per-hour ceiling, so you buy throughput rather than throughput-shaped volume.
High availability vs single node: A single-node install is the smallest production footprint. Active-active control planes, replicated queues and multi-node GPU pools raise both the hardware and the licence.
Throughput target: Peak pages per hour and the latency you need at peak, sized against your real document mix rather than a synthetic page.

Support and services

Support tier: Standard business-hours cover through to 24x7 with committed response times, a named solutions engineer and audit support.
Proof of Value scope: A fixed fee set by the document set, the number of extraction schemas and the environment complexity. Agreed before day one and never billed as time and materials.
Integration assistance: Optional. Schema design, pipeline integration and review-queue configuration delivered by our engineers rather than yours.

Sizing is done against your document mix, not a page count. The sizing and throughput reference explains how GPU workers translate into pages per hour for scanned, photographed and native inputs.

Do the arithmetic

What per-page pricing costs once volume is real

Metered parsing APIs and per-page IDP platforms are good software with honest published rates. The problem is not the rate — it is that the rate multiplies. Below is the list-rate arithmetic at two realistic enterprise volumes.

What per-page pricing costs once volume is real
Criterion	Metered parsing API	Per-page IDP platform	DocxIntel
How you are charged	Credits per page, 1,000 credits for $1.25	Per page, usage-based	Fixed annual licence by footprint
Published rate used below	$0.0125 per page10-credit agentic tier; the 45-credit tier is $0.05625	$0.30 per pageentry growth plan, around 5,000 pages a month	No per-page rate exists
100,000 pages a month (1.2M a year)	≈ $15,000 a year≈ $67,500 a year on the 45-credit tier	≈ $360,000 a year	Licence unchanged
1,000,000 pages a month (12M a year)	≈ $150,000 a year≈ $675,000 a year on the 45-credit tier	≈ $3.6M a year	Licence unchanged; add GPU workers
Reprocessing a 2M-page archive once	≈ $25,000	≈ $600,000	No incremental chargecompute you already own
Largest publicly priced plan allowance	400,000 credits a month on a $500 plan= 40,000 pages at 10 credits a page	Around 5,000 pages a month to start	No allowance; volume is not priced
Setup and onboarding fees	Not separately published	Charged in addition to subscription	Fixed Proof of Value fee, quoted up front
Self-hosted or air-gapped option	Enterprise plan only, in your cloud tenant	Exists, not publicly priced	Every licence, including fully air-gapped
If page volume doubles	Invoice roughly doubles	Invoice roughly doubles	No change unless you add capacity

How you are charged

Metered parsing API: Credits per page, 1,000 credits for $1.25
Per-page IDP platform: Per page, usage-based
DocxIntel: Fixed annual licence by footprint

Published rate used below

Metered parsing API: $0.0125 per page10-credit agentic tier; the 45-credit tier is $0.05625
Per-page IDP platform: $0.30 per pageentry growth plan, around 5,000 pages a month
DocxIntel: No per-page rate exists

100,000 pages a month (1.2M a year)

Metered parsing API: ≈ $15,000 a year≈ $67,500 a year on the 45-credit tier
Per-page IDP platform: ≈ $360,000 a year
DocxIntel: Licence unchanged

1,000,000 pages a month (12M a year)

Metered parsing API: ≈ $150,000 a year≈ $675,000 a year on the 45-credit tier
Per-page IDP platform: ≈ $3.6M a year
DocxIntel: Licence unchanged; add GPU workers

Reprocessing a 2M-page archive once

Metered parsing API: ≈ $25,000
Per-page IDP platform: ≈ $600,000
DocxIntel: No incremental chargecompute you already own

Largest publicly priced plan allowance

Metered parsing API: 400,000 credits a month on a $500 plan= 40,000 pages at 10 credits a page
Per-page IDP platform: Around 5,000 pages a month to start
DocxIntel: No allowance; volume is not priced

Setup and onboarding fees

Metered parsing API: Not separately published
Per-page IDP platform: Charged in addition to subscription
DocxIntel: Fixed Proof of Value fee, quoted up front

Self-hosted or air-gapped option

Metered parsing API: Enterprise plan only, in your cloud tenant
Per-page IDP platform: Exists, not publicly priced
DocxIntel: Every licence, including fully air-gapped

If page volume doubles

Metered parsing API: Invoice roughly doubles
Per-page IDP platform: Invoice roughly doubles
DocxIntel: No change unless you add capacity

Illustrative list-rate arithmetic, not vendor quotations. Metered figures use published 2026 credit pricing of $1.25 per 1,000 credits at 10 credits per page ($0.0125) and 45 credits per page ($0.05625); per-page IDP figures use a published growth-plan rate of around $0.30 per page. Volume commitments, negotiated discounts, annual-payment discounts, setup fees and taxes are excluded. Verify against current vendor documentation before you decide — we would rather you checked the numbers than took ours on faith.

Total cost of ownership

What per-page pricing does not put on the invoice

The per-page rate is the visible cost. These are the costs that show up in the project plan, the procurement file and the automation business case instead.

First year

Setup and onboarding, billed separately

Per-page platforms commonly charge implementation or setup fees on top of the subscription, so the first-year cost is not the rate multiplied by the volume. Ask for the first-year total, not the unit price.

Reprocessing you will quietly avoid

When re-reading the archive costs the same as reading it the first time, teams stop doing it. Schema changes get deferred, model upgrades are not applied retrospectively, and the historical corpus stays as badly extracted as the day it was ingested.

Engineering

A page processed twice is billed twice

Failed jobs, tuning runs, prompt or schema iteration and A/B comparisons all consume pages. Development and calibration traffic is real traffic, and on a meter it lands on the same invoice as production.

Compliance

The cost of documents leaving your perimeter

Third-party risk assessment, a data protection impact assessment, legal review of the processing agreement and a residency argument for your regulator are all real project costs. One metered vendor caches parsed data for 48 hours by default, which is a control you then have to review, disable and evidence.

Tiering

On-premise gated behind the top tier

Where self-hosting exists on a metered platform it is generally an enterprise-plan entitlement, and it runs inside your cloud tenant — data residency rather than a genuinely air-gapped environment. You buy the most expensive tier to get the deployment model you needed from the start.

Roadmap

A price that punishes success

Metered spend rises with every process you automate, so the business case for the next workload is worse than the one before it. A fixed licence inverts that: the eleventh use case costs nothing more than the tenth, which is how automation programmes actually spread.

How to get a number

From first call to signed licence

Four steps, each with a written output. You know the Proof of Value fee and the licence conversion price before the Proof of Value begins.

Step 1 — one hour
Scoping call with an engineer, not a qualifier
We go through your document types, the volumes you handle at peak, your target environment, your regulator and the systems the output has to land in. You leave the call knowing whether DocxIntel fits; we leave it knowing what we would have to deploy.
Step 2 — a few days
Sizing and written quotation
We size GPU workers, storage and resilience against your real document mix, then quote the annual licence for that footprint together with the fixed Proof of Value fee. The quotation states what each input costs, so you can see what changes if you drop the disaster-recovery environment or add a second site.
Step 3 — 30 to 45 days
Paid Proof of Value in your environment
Deployed inside your infrastructure, measured on your documents, against an accuracy threshold agreed in writing beforehand. If it misses the threshold you keep the measured report and owe nothing further.
Step 4 — on your paperwork
Licence at the price already agreed
The conversion price was fixed before the Proof of Value started, so there is no renegotiation on the strength of a good result. The deployment you evaluated becomes the deployment you license, and the footprint recorded in the order is what renews annually.

Questions procurement asks about DocxIntel pricing

The commercial objections that come up in every evaluation, answered without a discovery call.

Why is there no price list on this page?

Because the licence is sized by what we deploy, not by what you process, and we cannot size a deployment we have not seen. A single-node evaluation footprint and a dual-site high-availability install with a disaster-recovery environment are different pieces of engineering, and quoting a number before the sizing call would either overcharge the first or underquote the second. What we will commit to in writing, before you spend anything, is the fixed Proof of Value fee and the price the licence converts to if the accuracy threshold is met.

Is there a per-page option if we prefer it?

What happens to our bill if volume doubles next year?

What does the support tier actually include?

Every licence includes named technical contacts, security and bug-fix releases, model bundle updates published during the support window, and upgrade runbooks written for air-gapped installs. Higher tiers add tighter response-time commitments, weekend and holiday cover, a named solutions engineer for schema and pipeline changes, and assistance with your own audit and penetration-test cycles. The tier you choose is one of the handful of things that moves the licence figure.

How does renewal work, and what happens if we do not renew?

The licence renews annually and covers the deployment footprint recorded in the order. If your footprint has not changed, the renewal is a like-for-like renewal — we do not reprice on the basis of how many pages you processed during the term, because we do not count them. If you choose not to renew, the terms of your agreement govern continued use of the deployed version; what does not happen is a remote kill switch reaching into your network, because nothing in the deployment calls out to us.

Is there a smaller footprint for a single team or a single use case?

Yes. The smallest production footprint is a single-node install with one GPU worker, one environment and standard support — enough for a departmental workload such as one insurer claim queue or one bank onboarding channel. It runs the same six capabilities and the same models as the largest deployment; what differs is throughput, redundancy and response times. Most customers start there or in an evaluation sandbox and grow the footprint later.

Proof of ValueThe paid 30 to 45 day evaluation, with the accuracy threshold and conversion price in writing.Accuracy benchmarkThe document mix, the methodology and the per-category numbers behind the 99% claim.Sizing and throughputHow GPU workers translate into pages per hour, and how we size the footprint you pay for.Deployment modelsAir-gapped, private cloud, managed single-tenant or evaluation sandbox — all licensable.What's in the boxEvery container, model bundle and dependency delivered with the licence.Compare alternativesSide-by-side against metered parsing APIs and per-page IDP platforms.

Ask for the sizing call, not the price list.

An hour with an engineer produces a written quotation: the annual licence for your footprint, the fixed Proof of Value fee, and the price the licence converts to if the accuracy threshold is met.

No per-page metering
Runs in your environment
Written accuracy threshold