Pricing
The model, before the numbers
We publish how pricing is constructed rather than a table of numbers, because the numbers depend on modules and volume — and because the same price card applies to every customer, which we would rather show you than assert.
Three components
| Component | What it covers | Basis |
|---|---|---|
| Base subscription | Platform access per module or bundle, model operations, support | annual · per module/bundle |
| Metered usage | What the module actually processes | decisions · events · MAU · sessions · assets |
| Performance (optional) | A capped share tied to verified uplift | pre-agreed holdout measurement, in writing |
Rules we hold to
- The same price card for every customer. Volume and term discounts exist and are documented, not negotiated in the dark.
- Standard onboarding is included, or appears as a one-time line on the Order Form — never a surprise.
- Bespoke human services are out of scope of the platform subscription. If you need them, they are quoted separately and explicitly.
- The performance component only ever applies under a written measurement protocol you have signed, and it is capped.