Click Start and we'll provision you a scoped sandbox tenant with rights across DOOH, CTV, mobile, and messaging. Fire a synthetic delivery batch, watch the proof chain build, and verify every signature in your browser using the open-source auditor. The proof packs are bit-identical with what the production platform issues — same envelope, same canonical-JSON encoding, same Ed25519 chain.
You don't bring code, you don't pick a substrate, you don't configure anything. Click through six steps, watch the platform demonstrate itself end-to-end, then verify every cryptographic claim yourself.
You've read the marketing copy and need to see whether the platform actually works the way we claim — does the proof chain really verify, do constraints really enforce, do the numbers really reconcile. Twenty minutes of yes-it-does.
See the integration shape before committing — what the HTTP API looks like, what the SDKs return, what a real audit pack contains. Download the pack, run it through our CLI or the open-source auditor offline.
The chain runs end-to-end, the verifier is open source under MIT, the verification key is published, and the signing seed is re-derivable from a public string. No NDA required to validate the trust model.
The sandbox is a demonstration environment, not a production trust boundary — but everything it produces is cryptographically real. Three honest signals on every byte you'll see.
Sandbox proof packs use the same envelope.v1 wire format, the same canonical-JSON encoder, and the same Ed25519 + SHA-256 primitives as the production platform. Conformance is enforced in CI — a sandbox build only ships when the open-source auditor verifies every shape.
The sandbox derives its signing key from a public seed (enfinitos.sandbox.2026-q4.seed.v1). Anyone can re-derive it. Sandbox cannot sign production packs and production cannot sign sandbox packs — the keyIds and key directories are separate.
Sandbox tenants live in memory for the duration of your session. There is no persistent database, no risk of data leakage between visitors. Hitting Reset discards everything and gives you a fresh tenant.
@enfinitos/sdk-auditor library a regulator would use runs in your browser tab and walks the pack signature-by- signature, link-by-link, line-by-line.Each step is a real action against a real tenant — signed on the server, verifiable in your browser. No mock data.
One click creates a scoped tenant, seeds three legal bases (property, contractual, marketing-consent), and issues four starter rights across DOOH, CTV, mobile, and messaging.
Your operator org proposes to share a sub-scope of the DOOH right with brand Acme. The offer goes on-chain as a content-addressable hash — auditable later by either party.
Acting as Acme, accept the proposed offer. The platform issues a derived right whose contentHash references the parent right + the offer — full provenance chain captured.
The synthetic factory generates 12 delivery events with substrate-realistic dwell times (DOOH 6–14s, CTV 15–30s, mobile 2–8s). Each becomes a signed proof receipt; receipts hash-chain into a single envelope.
The seven-step audit roundtrip runs locally — re-canonicalise payloads, recompute SHA-256 hash chain, verify every Ed25519 signature against the published key, re-project metering, reconcile settlement. No server trust required.
Pre-render constraints run before any signature is computed. Pick a scenario and see real compliance enforcement — opt-out registry, automotive speed gate, drone Remote ID.
The sandbox demonstrates the full audit chain in twenty minutes. Real customer tenancy launches alongside the platform in February 2027. If what you just saw is the shape you want for your estate, reserve a pilot slot.