If your committed cloud spend, your core platform vendor or your existing implementation partner is the shortest path to running Gothink AIR, that is the path we would rather take — even where it costs us margin.
Gothink AIR ships as a container image that runs in your own account — buy through AWS or Microsoft marketplace and the purchase draws down a committed-spend agreement you may otherwise forfeit, through a supplier procurement has already approved.
The transaction sits on your existing cloud billing relationship — onboarding, payment terms and much of the legal review are already done.
Committed cloud spend is frequently use-it-or-lose-it — a marketplace purchase converts money you are already obliged to spend into software, rather than a net-new line item.
Enterprise and Sovereign deployments run inside your own boundary — the marketplace that operates it removes a step rather than adding an intermediary.
| Route | Status | What it supports |
|---|---|---|
| AWS Marketplace | Listing in preparation | Container listing with private offers, custom terms and multi-year payment schedules; draws down committed spend |
| Azure Marketplace | Listing in preparation | The same, against an Azure consumption commitment. Listed alongside AWS rather than after it |
| Procurement system integration | Follows the listings | So the purchase appears in the tool your procurement team already works in rather than beside it |
| Reseller and channel offers | Follows the listings | An authorised partner resells while billing stays on the marketplace — see delivery partners below |
| Direct order form | Available now | The standard route today: annual subscription, fixed-price fitting, exit at the pilot gate |
Marketplace listings are sequenced by demand, not by calendar — tell us in the first conversation that a purchase must draw against committed spend, and that listing moves to the front of the queue.
Wealth, asset-servicing and insurance platforms all share one intake problem — great data models fed by people re-keying PDFs, with a governed pipeline underneath eighteen months of work outside their discipline.
Your customers see your interface — underneath, documents are typed onto your data model with a page reference behind every field and a confidence gate tied to your risk policy.
Where a platform has its own canonical schema, the estate pack is written against it — field definitions, confidence gates, validation and steward routing, versioned as a pack file; your schema stays the standard.
Fitting is three weeks of fixed-price work — estate assessment, schema mapping, threshold setting and ground-truth labelling — and it needs domain people more than it needs us, which wealth, insurance and regulatory consultancies already have.
The full fixed-price onboarding fee on your own paper, in your own client relationship — gothink takes no cut of a partner’s delivery work.
The runtime licence and packs stay with gothink, with a referral fee on the first term — we win when the customer renews, so we win when your delivery was good.
Partner engineers are certified on the runtime, the pack format and the eval harness before they run a fitting unsupervised — the list and each certification date are published.
The certification programme exists on paper and the first partner conversations are open now — no third party has yet run a fitting end to end, so you would be first, and the terms reflect that. What a fitting actually involves →
Some buyers want no platform, partner or workflow — just typed records with citations arriving in their own pipeline.
From licence to first typed record, with request and response shapes, the schema reference and the deployment runbook — written to be read before a sales conversation.
Read the docsWhat is guaranteed between versions, how long a superseded schema is supported, and what constitutes a breaking change — in the signed release, not in a contract annex.
The same harness behind the benchmark numbers, so your team can score the pipeline continuously in their own CI.
The attestation benchmarkMarketplace, partner, OEM or direct — the same container image and version, with no partner build, OEM fork or marketplace edition.
The end customer owns the tuned weights, records and lineage regardless of who invoiced them — a partner or platform cannot licence that away, and the ownership schedule says so.
The ownership scheduleWhere a certified partner is engaged on an account, gothink does not bid the fitting against them — a channel a vendor competes with is not a channel.
No route creates a data-sharing arrangement — what improves across the estate is metadata about the pipeline’s behaviour, never documents, values or weights.
How we improve without your dataMarketplace, embedded, delivery or direct — the first conversation is fifteen minutes and mostly about procurement, and if Gothink AIR is the wrong fit we will say so in that call.