Priced on the estate, not the headcount
You pay for how many models are under active governance and how many environments they run in. The figures are indicative: hypotheses the three pilots exist to test.
The price list
A platform base for the pooled work every estate shares, then a line per model and per environment for the work that is yours.
| What | Figure | What it covers |
|---|---|---|
| WhatPlatform base | FigureNZ$24,000 a year | What it coversTwo models, one environment and quarterly re-benchmarking, plus the pooled work: the admission pipeline, licence adjudication, upstream watch, evidence and policy enforcement. |
| WhatEach additional model under active governance | Figure+NZ$4,000 a year | What it coversGolden-set evaluation on your codebase, compatibility testing, and re-benchmarking as the model or the codebase moves. |
| WhatEach additional execution environment | Figure+NZ$8,000 a year | What it coversA second cluster, your private cloud or an edge fleet. A hosted provider or frontier API route, in build, counts as an environment too, and carries provenance by host attestation, not verified. |
| WhatFloor | Figurearound NZ$30,000 a year | What it coversBelow that a deal does not pay for the support load it creates. |
Indicative, not a quote or an offer: the structure is the durable part. Hardware is separate.
The Estate Pilot
NZ$45,000 to NZ$60,000, fixed scope, 8 to 12 weeks, priced to cover its own cost and never a loss leader. Indicative until tested in pilots. Hardware is separate.
The headline deliverable is utilisation-aware TCO on your own tasks: whether running it yourself beats paying per token. Discovery is free, and scope is fixed in writing before price. We vary scope, never discount.
How the pilot runs, week by week.
What the pilot includes
- Admission and a provenance artefact for each model in scope
- Deployment into your environment, from a commit
- Integration with your identity provider
- The enforcement hook: keys, entitlement, and the admission join
- Policy as code in your own repository, with tests
- Audit logging of every request and decision
- One knowledge source, access-controlled, where it applies
- A Compare run against your own tasks
- Data-flow and security documentation
- Utilisation-aware TCO, a results session and a production recommendation
What the price does not include
- Accelerator hardware, hosting or cloud accelerator cost
- Production hardening, high availability, disaster recovery or multi-site
- More than the one agreed workload
- Custom connectors or bespoke integrations
- Model training or adaptation
- Certification, regulatory sign-off or legal review
- Out of hours support during the pilot
Anything on this list can be scoped separately after the pilot. Hardware strategy is set out under Deployment and hardware.
A representative estate
Four models under active governance across two environments: the platform base at NZ$24,000, two more models at NZ$8,000 together, and the second environment at NZ$8,000: NZ$40,000 a year. Indicative until tested in pilots. Hardware is separate.
What to measure it against
A 150-engineer shop pays roughly NZ$90,000 to NZ$120,000 a year in cloud coding-assistant seats, against NZ$40,000 to govern the estate. Directional, and indicative until tested in pilots. Hardware is separate.
What a subscription carries
New models land, licences change and your codebase drifts. A subscription keeps the admission answer current, measured against your last one, and keeps the release tracking, patching and fit testing off your team. You can leave at any time; a subscription renews at month six on the same scope, so the renewal decision is a test of whether the admission answer is still current. What you keep is on the exit page.