Home/Pricing
Pricing / how the licence works

An annual subscription and a three-week onboarding.

Forge is a licence to a versioned runtime, plus the estate packs you need, plus a one-time fixed-price fitting. Deployment location is a modifier on the licence, not a rebuild. This page sets out what you are buying and what moves the number — the number itself is scoped to your estate rather than read off a list, and it comes back from the founder rather than from a sales team.

You own the tuned weights Annual subscription, per deployment Fixed-price onboarding No per-seat pricing Exit at the pilot gate
01 / the subscription

Three tiers. The difference is where it runs and what you own.

Every tier is the same runtime at the same version. Nothing below is a different product, a cut-down build, or a feature held back to create a ladder. Which tier you need is usually obvious in the first conversation, and it is the main thing that sets the price.

Free

Sandbox

Twenty-five of your own documents, typed onto a pack schema with a page reference behind every field, scored against a ground-truth set your people label.

ForAnyone evaluating
CostFree
CommitmentNone — no contract, no call
Start an evaluation
Subscription

Forge Standard

The full runtime on gothink Cloud, in your tenant and region, under your keys. For one department getting a single document family under control.

ForOne department, gothink Cloud
IncludesRuntime, 1 estate pack, standard support
SupportBusiness hours · portal
Subscription · most common

Forge Enterprise

The same runtime inside your own boundary, under your IAM and your keys, with the tuned weights contractually yours. This is the tier regulated buyers land on.

ForRegulated, customer VPC
IncludesRuntime in-boundary, 2 packs, weight ownership
Support24×5 · named engineer
SeatsUnlimited
Subscription

Forge Sovereign

Air-gapped or public sector. Everything in Enterprise, plus an offline update channel, source escrow and on-site enablement.

ForAir-gapped or public sector
AddsOffline updates, escrow, on-site enablement
PricingScoped per deployment
There is no per-seat licensing at any tier. Charging your stewards to look at an exception queue would be an odd way to encourage anyone to use the gate. Deployment tier moves you between price levels rather than adding a rebuild charge — it is the same image with a different install profile.
02 / what is on the order form

Four lines, and you will recognise all of them.

No usage meter you cannot predict, no per-seat count, no surprise line at renewal. This is the whole commercial structure — each line is priced against your estate.

LineTypeWhat it is
Forge RuntimeAnnual subscriptionThe five-layer pipeline, model runtime, exception queue, command centre, lineage store and eval harness. One versioned artifact, identical for every customer.
Estate packAnnual add-onPer-domain schemas, gates, validation and reference ground truth. Standard includes one, Enterprise and Sovereign include two; further packs are added at a per-pack rate and co-term with the licence.
FittingOne-time, fixed priceThree weeks: estate assessment, schema mapping, threshold setting, ground-truth labelling with your experts, go-live. Fixed at signing, with a fixed end date.
SupportIn the tierStandard is business hours and portal. Enterprise and Sovereign are 24×5 with a named engineer and upgrade assistance.
SandboxFreeTwenty-five documents, typed output with citations, and a score against a set you label. No contract, no call.

An alternative to the volume band: pay for cleared files

The structure above prices capacity — a volume band you buy in advance. Some teams would rather pay for work that actually completed, so Enterprise can instead be priced per file cleared straight through above the confidence gate, with the accuracy floor attached and exceptions not billed.

It suits an estate whose volume is seasonal or genuinely unknown, and it aligns the bill with the thing you are buying: a file nobody had to re-key. It is the harder option for us to price, and we offer it because a vendor who will only sell capacity has an incentive you should be suspicious of. What we will not do is quote a cost per page — a page is not a unit of work, and pricing on it rewards the vendor who lowers the gate.

03 / what moves the number

Four things set the price. None of them is how badly you need it.

We would rather you knew the shape of the quote before you ask for one. If you can answer these four, you will get an indicative figure in the first conversation rather than the fourth.

01

Where it runs

gothink Cloud, your own VPC, or air-gapped. This is the single biggest factor, and it is a modifier on the licence rather than a rebuild charge — the image is the same in all three cases.

02

How many document families

One family under control costs less than five. Each additional estate pack is a line on the order form, and packs co-term with the licence so renewals stay on one date.

03

Annual page volume

Priced in bands rather than per page, so a busy quarter does not generate a bill you have to explain. Bands are re-declared at renewal, not metered in real time.

04

Support level

Business hours and portal, or 24×5 with a named engineer and upgrade assistance. Seat count never enters the calculation.

Why the figures are not published here

A document estate is not a seat count. Two firms of the same size can differ several-fold on page volume, number of families and deployment requirements, and a published band wide enough to be honest about that range would not tell you anything useful. So the model is public and the number is scoped: tell us the four things above and you will get a real figure quickly, not a discovery process. What we will not do is price against how much you appear to need it.

Ask for an indicative figure
04 / onboarding

Fitting is a fixed price, and it has an end date.

It is a statement of work with a fixed fee and a date on it, not a retainer that discovers its own scope. Three weeks: schema mapping, gates and ground truth, then the pilot gate and go-live.

You can leave at the pilot gate

Fitting invoices against three milestones: kick-off, pilot gate passed, and go-live with the weights handover. If Forge does not clear the gate criteria written into the run-book when scored against the set your experts labelled, the later milestones are never invoiced and you exit having paid the first only. That is in the statement of work, not offered in the room.

How the three weeks run
05 / the obvious question

You own the weights. So what are you paying for?

The model, the records and the lineage are yours permanently — export them, keep them, run them if you leave. What the subscription buys is not a stream of improvements. It is a guarantee that the asset still performs.

Your accuracy is certified at go-live against the ground-truth set your experts labelled. Every quarter it is re-measured against that same set. If it has fallen below the contracted floor, gothink retrains it — at gothink’s cost, inside your boundary — and reissues the evidence pack. That is the product. Everything else on this page is how it is delivered.

Own the asset. Insure the accuracy.

The guarantee

The accuracy floor is a contract term, not a target

The floor is set per field family during fitting, against your labelled set, and written into the order form. It is not our benchmark number and it is not an average across your estate — averages hide exactly the fields that matter.

MeasuredQuarterly, on your ground truth
If it dropsWe retrain at our cost
If we cannot restore itYou exit and keep everything
Why this and not a feature list

Estates drift whether or not you renew

New layouts arrive, counterparties change their forms, a regulator amends a schedule. A model certified in March is quietly less accurate by November, and nothing in the system announces it. The measurement is the part you cannot do without us; the retraining is the part you should not have to pay for twice.

What you keep if you stop

Everything, unguaranteed

The weights, the records, the lineage and the eval set remain yours and the system keeps running. What lapses is the measurement, the retraining, the new schemas and the support — so the asset stays yours and starts ageing. That is an honest trade and we would rather you saw it written down.

Yours permanently

The tuned weights

Trained on your documents, exportable on request, and covered by a contract clause that says so. Three years of your experts’ corrections accumulate into a model on your side of the boundary.

Yours permanently

The records and the lineage

Every typed record and every page reference behind it. In your systems, in your formats, under your retention policy.

Yours permanently

The eval set

The ground truth your experts labelled. It is the thing that makes any future vendor comparison possible, and it leaves with you.

What lapses

New schemas and new versions

Regulatory forms change. Document families get added. The runtime ships quarterly. Stop subscribing and you keep last year’s version, running on last year’s schemas.

What lapses

Recalibration and drift work

Estates drift. New document layouts arrive. Keeping accuracy where it was on go-live day is continuous work, and it is most of what you are subscribing to.

What lapses

Support and upgrade assistance

Named engineer, 24×5 on Enterprise, and someone to call when a promotion goes badly at 2am.

05a / the ownership schedule

“You own the weights” is a contract schedule, not a slogan.

A promise of ownership is worth what the paperwork behind it is worth. This is what the schedule attached to every order form actually specifies, and it is available to read before you are in a sales process rather than after.

QuestionWhat the schedule specifies
What transfersThe tuned model weights, the typed records, the lineage store, the eval set your experts labelled, and the pack configuration as it stood at your last release
In what formatStandard open weight files with the tokenizer and config, plus records and lineage as documented schemas — not a proprietary export that only Forge can read
Under which licenceThe base model is named in the schedule, and gothink warrants that its licence permits the derivative weights to be transferred to you and used without gothink. If a base model cannot support that, it does not go into the runtime
Runnable without usOpen weights run on ordinary inference infrastructure from several independent providers, or on your own. We will demonstrate the exported weights running outside gothink’s software before you sign, on request
What gothink keepsThe platform, the pipeline source, the base schemas and the pack IP. You own what was built from your estate; we own the machine that built it
When you can take itOn request at any time during the term, and on expiry. Not conditional on a dispute, a notice period or a final invoice
If gothink stops existingEnterprise and Sovereign include source escrow with a named agent and defined release triggers. Your deployment continues running in your account regardless, because it already was
Why the base-model line is in there. Most “you own your model” claims in this market are made about weights that sit on the vendor’s infrastructure under a licence that was never checked for transferability. It is the difference between owning something and being a tenant with better furniture, and it is invisible until the day you try to leave. Naming the base model and warranting the transfer is the cheapest way for us to prove which one this is. The technical detail →  ·  How small we are, said plainly →
Before the quote / the number that matters

Get a figure sized to your estate.

Tell us where it needs to run, how many document families and roughly what page volume, and you will get an indicative number quickly. If you would rather see the software work before discussing money, the sandbox is free and needs no contract.