See the strict path now. Bind a deployment when ready.
First, run the complete test-only lifecycle in one click—no account, domain or setup. Then, when the mechanics make sense, bind a domain or public GitHub repository and complete one server-observed private pilot. Public proof remains a separate, optional choice. No payment provider is contacted and no money moves in either path.
From instant understanding to verified activation.
Test the mechanics before changing infrastructure. The verified pilot then keeps production authority, payment execution and public evidence separate.
01
Run the instant test
One click exercises all eleven strict test stages with no account, payment credential or external provider.
02
Bind what you control
When ready, verify an HTTPS domain through DNS or the default-branch commit of a public GitHub repository.
03
Run the private pilot
The immutable kit reaches one strict live reservation and fresh credential-bound permit redemption without calling a payment provider.
04
Choose what happens next
Activate ongoing Starter access immediately, or separately opt in to a public human page, machine JSON and badge.
WHAT YOU NEED
Nothing to test. One subject to prove.
The instant strict test needs only this browser.
The verified pilot needs an HTTPS domain where you can add a DNS TXT record; or
a public GitHub repository whose default branch you control.
A terminal with Node.js 22 or newer.
Setup is guided. DNS propagation and repository access determine the elapsed time.
WHY IT MATTERS
Keep the pilot private or replace a screenshot with evidence.
Public proof is optional. If selected, its MandateShield signature exposes the exact server observations and non-claims in both human- and machine-readable form.
The instant sandbox is accountless and test-only. The separate verified pilot requires sign-in, current service terms and external subject control. A card is not required, and public proof remains optional.