Home/Partners
Four routes, honest status on eachBuy it the way you already buy software.
Committed cloud spend, your platform vendor or your implementation partner — whichever is shortest.
Spend the commitment you already made.
A container image in your own account, bought against committed spend you might otherwise forfeit.
Faster
No new vendor to onboard. Billing, terms and much legal review are done.
Cheaper
From a budget you already have, not a net-new line item.
A natural fit
Enterprise and Sovereign already run inside your boundary.
| Route | Status | What it supports |
|---|---|---|
| AWS Marketplace | Listing in preparation | Private offers, custom terms, multi-year payments; draws down committed spend. |
| Azure Marketplace | Listing in preparation | The same, against an Azure consumption commitment — alongside AWS. |
| Procurement system integration | Follows the listings | The purchase appears in your procurement tool. |
| Reseller and channel offers | Follows the listings | An authorised partner resells; billing stays on the marketplace. |
| Direct order form | Available now | Priced per unit, never per seat, plus an annual platform fee; quoted after scoping. Pilots are free. |
Listings are sequenced by demand. Say early that you must buy against committed spend, and that listing moves up.
For platforms whose customers arrive with documents.
Your interface on top. Underneath, documents typed onto your data model, every field cited.
The honest version
Some platforms are building document AI themselves — for some that is right. If you are two layers in already, the conversation is shorter. The five layers →
Onboarding you run. A licence we keep.
A fitting is configuration work that needs domain people more than it needs us.
The fitting fee
On your own paper, in your client relationship. We take no cut.
The subscription
Runtime and packs stay with gothink; terms agreed per partner.
The certification
Partner engineers certified before running a fitting alone. The list will be published once anyone is certified.
This is early
The programme exists on paper; no third party has run a fitting end to end yet. You would be first. What a fitting involves →
Or just build against it.
Typed records with citations, arriving in your own pipeline.
Quickstart and API reference
From licence to first typed record.
Read the docs → PublishedVersioning and support policy
What counts as breaking, and how long schemas are supported.
Release policy → PublishedThe scoring harness
Score the pipeline continuously in your own CI.
The attestation benchmark →Four rules on every route.
One artifact, whoever sells it
No partner build, OEM fork or marketplace edition.
Ownership survives the route
The end customer owns weights, records and lineage.
We do not compete with partners
Where a certified partner is engaged, we do not bid the fitting.
Nothing learns from your customers
Pipeline metadata only — never documents, values or weights.
Tell us how you need to buy it.
Or who you want to sell it to. Fifteen minutes, mostly about procurement.