Priced per call. No shelfware.
You pay for intelligence produced, not seats provisioned. The rate card below is not typed into this page — it is read from the metering engine that issues your invoice.
Live rate card
read from the metering engine| Product | Meter | Per call (ZAR, ex VAT) |
|---|---|---|
| Loading the live price list… | ||
Rates shown are list. Volume commitments, bundled pillars and enterprise terms are negotiated — but the meter still bills against the same product lines, so your invoice reconciles to your logs line for line.
Three ways to buy the same platform.
The engines are identical across tiers. What changes is the deployment shape, the support commitment and the contractual assurances.
Starter
Sandbox and first production traffic. For a team proving the thesis on its own data.
- Sandbox and live keys
- All five pillars enabled
- Partner portal, full RBAC
- Signed webhooks
- Usage and revenue dashboards
- Email support
Growth
A book in production, a risk committee that needs evidence, and a compliance function that needs the retention story.
- Everything in Starter
- Volume-tiered rates
- Model governance pack and underwriting memoranda
- Compliance-officer review queue
- CSV exports of audit and security ledgers
- Named technical contact
Enterprise
Regulated institutions with their own environment, their own auditors and their own residency requirements.
- Everything in Growth
- PostgreSQL with row-level security, in your environment
- White-label tenancy and namespacing
- Offline desktop deployment
- Due-diligence pack and POPIA gap assessment
- Uptime SLA and incident escalation
Every call leaves a line.
A metered call writes a usage record carrying the product, the endpoint, the response status and the latency. Nothing about the metering path is inferred at invoice time — the invoice is a sum over records that already existed.
Failed calls are metered as well. That is deliberate: a bill you cannot reconcile against your own logs is a bill you cannot audit, and an error you are not charged for is an error nobody chases. You see the failures in the portal alongside the successes, with the latency that produced them.
Loan-book events are the one product priced at zero. Recording that a loan was originated, disbursed or repaid is not intelligence — it is bookkeeping the platform needs to keep your outcome labels honest.
Live throughput
Metered calls recorded on this instance.
The ones that come up in procurement.
Is there a platform or seat fee?
Not on Starter or Growth. Portal seats, RBAC, dashboards and ledger exports come with the platform; you are billed for calls. Enterprise agreements carry an annual contract because they include deployment, SLA and diligence commitments that are not per-call in nature.
What does a sandbox call cost?
Sandbox keys run the same code against simulated registries and are not billed during evaluation. They are metered, so you can size your production spend from your own test traffic before committing to anything.
Are third-party costs passed through?
Where an underlying registry or bureau charges per lookup, that cost sits inside the published product rate — there is no separate pass-through line. Where a licensed third-party signal requires its own consent purpose, it is only fetched when that consent exists, and it is cached so a recent lookup is not re-billed.
How do we reconcile an invoice?
The portal shows usage by product, by day and — for internal tenancy — by organisation, with call counts, revenue and average latency. Export the audit ledger to CSV and the two agree.