Not the way we would prefer to sell it. Procurement is usually the longest part of a deal and the part with the least to argue about. If your committed cloud spend, your core platform vendor or your existing implementation partner is the shortest path to running Forge, that is the path we would rather take — even where it costs us margin.
Forge ships as a container image that runs in your own account. If you hold a committed-spend agreement with AWS or Microsoft, buying through their marketplace draws the purchase down against a commitment you may otherwise forfeit — and routes it through a supplier your procurement team has already approved.
The transaction sits on your existing cloud billing relationship. New-supplier onboarding, payment terms and much of the standard legal review are already done, which is where most of the calendar goes in a first purchase from a small vendor.
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 competing for a net-new line item that has to survive a budget round.
Enterprise and Sovereign deployments run inside your own boundary. Buying through the marketplace that operates that boundary 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. A buyer who tells us in the first conversation that a purchase has to draw against committed spend moves that listing to the front of the queue — and in the meantime we will structure the direct order form so that nothing has to be renegotiated when the listing goes live. Telling us late is what creates the delay; telling us early usually does not.
Wealth, asset-servicing and insurance platforms all inherit the same intake problem: the data model is excellent and the way data gets into it is a queue of people re-keying PDFs. Building a governed pipeline underneath an existing platform is eighteen months of work in a discipline that is not the platform’s own.
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 own risk policy. Deployment stays in your customer’s account or yours, whichever your contract already promises.
Where a platform has its own canonical schema, the estate pack is written against it rather than against ours — field definitions, confidence gates, validation and steward routing, versioned as a pack file. Your schema stays the standard; we map to it.
Fitting is three weeks of fixed-price work: estate assessment, schema mapping, threshold setting and ground-truth labelling with the customer’s own experts. It needs domain people more than it needs us, and consultancies in wealth operations, insurance underwriting and regulatory change already have them.
The full fixed-price onboarding fee, on your own paper, in your own client relationship. gothink does not take a cut of delivery work a partner performs.
The runtime licence and the packs stay with gothink, with a referral fee on the first term. Our incentive is that the customer renews, which means our incentive is that 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 of certified partners is published, and so is the date each certification was issued.
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. If you are considering it, you would be first, and the terms reflect that — joint delivery on the first engagement, gothink carrying the risk on the fixed price, and your fee protected if the scope was wrong. What a fitting actually involves →
Some buyers do not want a platform, a partner or a workflow. They want typed records with citations arriving in their own pipeline, and everything else is overhead.
From licence to first typed record, with the request and response shapes, the schema reference and the deployment runbook. Written to be read before a sales conversation rather than after one.
Read the docsWhat is guaranteed between versions, how long a schema is supported after it is superseded, and what constitutes a breaking change. On the changelog, not in a contract annex.
Versions and supportThe same harness that produces the numbers on the benchmark page, so your team can score the pipeline continuously in their own CI rather than at a quarterly review.
The attestation benchmarkMarketplace, partner, OEM or direct — the same container image at the same version, on the same public changelog. There is no partner build, no OEM fork and no marketplace edition.
The end customer owns the tuned weights, the records and the lineage regardless of who invoiced them. A partner or platform cannot licence that away on the customer’s behalf, 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. Stated here rather than negotiated per deal, because a partner channel that 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 own behaviour — where it abstains, which layouts defeat it — 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, not product. If Forge is the wrong fit we will say so in that call rather than in the fourth one.