Developer path
Sandbox proofs are for development. Sandbox access — and later production signing credentials — is issued after an architectural review, not at account creation.
Read the trust modelSandbox
What is instant today: a free console workspace at signup, the keyless public verify API, and the SDK's offline check-init. Proof generation unlocks with sandbox access, issued after a short architectural review.
Sandbox proofs are for development. Sandbox access — and later production signing credentials — is issued after an architectural review, not at account creation.
Read the trust modelDeveloper Path
Read the public docs and verify a live proof today; a free account opens the console, and the proof-generating sandbox is issued after a short architectural review.
Create a free account for the console workspace, verify live proofs through the keyless public API, and run the SDK's offline init check — none of these wait on review.
Sandbox proofs are canonicalized, policy-bound, and signed like production, so you can replay and inspect them without touching live signing keys.
Production signing access is review-gated, so when you are ready you request an architectural review rather than pulling automatic credentials.
Start with public developer guidance, then request sandbox access through review.
Start buildingResearch, standards, and the AEVN Initiative remain available as public resources.
Explore Intentrax LabsNothing you do here is published. The docs are public to read; your sandbox work stays private to your account, and production access is review-gated.