Browser-first sandbox

From policy idea to working integration

Choose the result your protocol needs, create an isolated sandbox, and run its hosted test without a wallet, zkLogin, or terminal.

Build a sandbox

1

Choose the result.
Start with the product goal. Abraxas recommends a policy and shows exactly what the partner receives.

2

Create the sandbox.
Name the app and callback. Abraxas creates an isolated test tenant and shows its test key once.

3

Run the relying-party pilot.
Walk through age 21+ verification, holder disclosure, signed receipt verification, and the second-partner reuse path.

4

Run the hosted test.
After creation, select “Run hosted sandbox test.” The returned receipt is checked through the same server integration used by partner apps.

What is live

Policy selection, starter-kit generation, isolated sandbox provisioning, API-key issuance, hosted Partner Flow, public receipt verification, and reviewed Solana devnet proof verification are connected product surfaces.

Open technical proof surfaces

Clear boundary

Sandbox creation does not require a wallet or identity proof. Wallet binding is an optional integration capability for protocols that need onchain action control. Production access remains a reviewed upgrade.