Pricing
Start with one design partner.
Scale to production.
Every tier produces the same 33-field record with the same schema. The difference is volume, support, and the signing substrate used in production.
Start here
Design Partner
$10–25K / 90-day pilot
For Series B fintechs and regulated enterprises that want to shape the artifact format to pass their specific auditor's requirements. 50% upfront. You tell us what the OCC examiner will ask for. We build it to your spec.
- Full record schema v1.0.0
- Software signing (Ed25519, FIPS 186-5)
- S3 Object Lock COMPLIANCE WORM
- RFC 3161 timestamping
- Standalone verify CLI
- Direct founder access
- Artifact format shaped to your auditor
Start a conversation
Production
Starter
$20K / year
For Series B fintechs deploying AI agents in customer-facing workflows. Up to 100,000 decisions per month. Full schema, production signing infrastructure, SOC2-aligned controls.
- Up to 100K decisions per month
- All record fields
- Production HSM signing (FIPS 140-2 Level 3)
- S3 Object Lock COMPLIANCE WORM
- RFC 3161 timestamping
- Standalone verify CLI
- SOC2 CC6.1 / CC4.1 evidence export
Request access
High volume
Enterprise
$40–80K / year
For banks, insurers, and healthcare companies deploying AI agents across multiple regulated workflows. Unlimited decisions, dedicated support, and full compliance reporting.
- Unlimited decisions
- All Starter features
- Dedicated support and SLA
- Multi-workflow deployment
- Compliance reporting dashboard
- Audit-ready evidence packages
- Named escrow custodian
Contact us
Customer-dedicated signing key
Artifacts signed by a key dedicated exclusively to your tenant. Satisfies isolation requirements from legal, compliance, and audit teams who require that signing keys not be shared across customers. Available at contract signature on Starter and Enterprise.
+$15K / year
On the signing substrate: The Design Partner tier uses software signing with the Ed25519 algorithm (FIPS 186-5). Production tiers use HSM signing at FIPS 140-2 Level 3 with the same algorithm and identical schema. The artifact format, field structure, and verification semantics are identical across both. See
deployment modes for the full technical detail.