Two commercial paths for OEM partners.
Start with the paid pilot when the goal is to validate one event schema and one verifier path before a production commitment.
90 days. No annual commitment.
- One scoped event schema.
- ECDSA-signed records by default.
- Founder integration support.
- Static verifier sample.
- Cancel at pilot end.
- One scoped event schema with working /v1/enforce/{pack}/{intent} call.
- ECDSA-signed records covering pilot traffic, with the verifier path represented by the static /r sample.
- Sample of production-pattern signed records you can show internal stakeholders.
- Production SOW outline or shutdown checklist.
No production claims about your customers until your pilot results say there is something to claim.
Annual, plus per-record pricing.
- Production deployment plan.
- Production support path.
- Usage reporting.
- Agreed retention policy.
- SLA terms need SOW and deployment architecture.
Pricing post-discovery. Scope: partner-branded verifier presentation and domain policy work. This does not include customer co-signing or BYOK, which are not live in the current product.
Direct deployer engagements: separate sales motion, contact for details.
Per-record pricing can step down with volume.
Pilot and early customer traffic. Keep the unit price simple while schema and verifier policy settle.
Production usage with enough record volume to justify a lower per-record fee.
High-volume partner traffic. Final pricing depends on retention, verifier access, and support scope.
About 88 engineering hours across 13 weeks.
Peak partner-side load is Weeks 1 through 3, about 44 hours. This assumes one partner engineer owns the integration and a founder or product lead joins scoping and review.
The pilot is realistic for a small RegTech vendor if one engineer can spend about half time during Weeks 1 and 2, then a few hours per week during the live-record period. If the partner cannot cover Weeks 1 through 3, the pilot should wait.