Problem Deploy Demo Security Pricing GitHub FAQ
Pricing

Start with one design partner.
Scale to production.

One engagement is open today. Whatever comes later produces the same 33-field record, verified the same way, by the same standalone tool.

Available now
Design Partner
A paid 90-day pilot, 50% upfront, with two partners taken on in total. You tell us what your examiner or auditor will ask for and the artifact gets built to that. Scope and price are set together in the first conversation, because these first engagements are how we learn what this is worth.
  • Full record schema v1.0.0, all 33 fields
  • Software signing (Ed25519, FIPS 186-5)
  • S3 Object Lock COMPLIANCE WORM, in your own bucket
  • RFC 3161 timestamping
  • Standalone verify CLI your auditor runs without us
  • Direct founder access
  • Artifact format shaped to your auditor
Book a 30-minute call

Where this goes as you scale

Production and enterprise engagements follow the same record and the same verification, at higher volumes, with signing moved into FIPS 140-3 Level 3 hardware and support commitments alongside. Those arrive with later phases rather than being available today, and we would rather say so than list them as though you could buy them this afternoon. If that is the shape you need, the call is still the right place to start.

On the signing substrate: Signing today is in software, using Ed25519 (FIPS 186-5). Moving it into FIPS 140-3 Level 3 hardware is a later phase, with the same algorithm and the same schema. The artifact format, field structure, and verification semantics are identical across both. See deployment modes for the full technical detail.