Gothink AIR ships as one versioned system, identical for every customer; onboarding fits it to your estate with schema mapping, confidence gates and a ground-truth set your experts label. Fixed scope, fixed price, fixed end date — then you are running software, not a project.
Test the claims, compare us against alternatives, and work out how you would buy — all before anyone from gothink is in the room.
Your documents, your labels, your number — plus the gate log, exception list and a one-page summary written for a risk committee. Free, no contract, five business days.
Score your documents Compare usCitation correctness, gate precision, abstention correctness, reviewer agreement, evidence completeness, case-file completeness — open method and harness, with the corpus on request under a permissive licence, including for marketing against us.
The attestation benchmark Buy itGothink AIR runs in your own account or on gothink Cloud; marketplace listings are planned, not live. Direct or partner-delivered — same artifact, same licence, same ownership.
Partner enquiriesYou buy a statement of work with a fixed fee and a date — no open-ended build, because there is nothing customer-specific to build: everything is configuration.
| Week | What happens | Who from your side | Ends with |
|---|---|---|---|
| 01 Estate & schema | Document families are inventoried against the pack schema, missing fields added as schema entries, and connectors pointed at your sources and targets. | A data owner and a platform engineer, part-time | schema mapping signed |
| 02 Gates & ground truth | Your risk function sets the per-field threshold; your experts label a ground-truth set that will score every release; steward routing is wired to your queues. | A steward or SME, and whoever owns the risk policy | thresholds set, ground truth labelled |
| 03 Pilot gate & go-live | Gothink AIR runs the estate and is scored against your labelled set: if it clears the gate criteria in the run-book, it goes live and the weights are handed over; if not, you stop here. | Whoever signs off on a wrong value reaching a client | scored, live, weights handed over |
Most software companies leave this vague — naming the humans in delivery invites the question of whether you are buying software or people. The honest answer: three weeks of expert work sits between your estate and a working deployment.
The engineer who fits your estate writes the runtime — not a delivery organisation, partner bench, or solutions team on billable hours. What they learn in your estate lands in the product, because they ship it.
Anything built during a fitting must ship to every customer or become a versioned pack, or it does not get built — no customer branch. When a request cannot be generalised, we decline rather than fork.
The metric is the share of what was built during fittings that shipped to everyone within a quarter — not utilisation or hours. You can check it: every promotion ships to every customer.
Four checkable things distinguish them: a fixed fee and end date in the statement of work; an engineer in engineering whose output goes to the main repository; no per-customer branch (verify it in the shipped artifact); and work that is transferable — certified implementation partners can run a fitting instead of us. A delivery model a vendor will hand to somebody else is a product.
Every customer runs the same Gothink AIR runtime at the same version. What differs between two deployments is a set of files you could read.
The master fields your systems of record expect, and how each document family maps onto them. A versioned file in the pack, extended for you at Fitting.
Per field, set by your risk function. A number, not a code path. Change it on a Tuesday without a release.
Which exception goes to which queue, which cross-field checks must hold, which entitlements apply before a record is served.
Which sources, which masters, which targets, under which credentials. From the released connector library.
The ground truth your experts labelled. It scores every release we ship you, and it is yours to take.
If you need something Gothink AIR does not do, it ships to everyone or into a pack, or it does not get built; where a request cannot be generalised, we decline rather than fork.
It is very hard to hold a per-customer branch and a dated, signed release at once. Your running version is printed in your control plane.
Deployment location is a modifier on the licence, not a rebuild — the image and version are the same on gothink Cloud as inside a bank's VPC; only the runbook and connector reach change.
| Profile | Runs on | Same image? | Typical reason |
|---|---|---|---|
| gothink Cloud | An isolated tenant in the region you choose | Yes | Fastest path to production; no infrastructure work on your side |
| Customer VPC | Your AWS, Azure, GCP or Kubernetes, your IAM and keys | Yes | Policy or regulator requires the documents never leave your boundary |
| Air-gapped / sovereign | On-prem or a national cloud, with an offline update channel | Yes | No outbound network path is permitted at all |
There is no pod to leave, because there was never a pod. What recurs after go-live is software and an SLA.
Quarterly feature releases, security patches for the current and previous major.
When ACORD revises a form or a custodian changes a statement layout, the pack ships the change as a new version. You do not re-fit.
Standard is business hours through the portal. Enterprise adds priority response, 24×5 and a named engineer. Both are documents you can read before you sign.
The ground truth your experts labelled at Fitting runs against each new version before you take it, so an upgrade cannot quietly cost you accuracy.
Accuracy, straight-through rate, drift and lineage completeness, formatted for model-risk and audit functions — and if the number has fallen below the floor set at Fitting, gothink retrains at gothink’s cost. The guarantee, in full.
The weights, records and lineage are yours permanently. The system keeps running on the schemas and the accuracy it had the day you stopped. Why people renew anyway.
Before any of the above, score Gothink AIR on twenty-five of your own documents against a ground-truth set you label yourself.
Your documents, your labels, your number. No contract and no call.
Fixed scope, fixed price, fixed end date, and an exit at the pilot gate.
The tuned weights, the records and the lineage are handed over at go-live.