Skip to content
YTT Secunet

Sandbox · runs in your browser

Test a sovereign route.

Six tenants, six legal regimes, one gateway. Send requests, break regions, tamper with receipts, and watch the policy engine hold the line.

Request composer

EUeu-gdpr-strict· Banking

Model
Prompt

3 PII entities detected: PERSON, IBAN, DE_STEUER_ID

PII handling
Gateway pipelineawaiting request

  1. Edge ingress

    ·

  2. PII scan

    ·

  3. Policy eval

    ·

  4. Endpoint resolve

    ·

  5. Upstream inference

    ·

  6. Notary sign

    ·

Compose a request and send it.

Try the developer override on a German tenant, or simulate an outage on the Swiss tenant with gpt-4o, and watch where the gateway refuses to go.

Audit event log0 events
#Time (UTC)TenantPolicyModelDecisionEndpointLeaf
Events appear here as you send requests.
Force a transferPick the German bank tenant, switch on the developer override and send. The policy engine denies egress to us-east and signs a denial receipt.
Break the primary regionChoose the Swiss tenant with gpt-4o and simulate an outage. Zurich fails over to Geneva. Switch to claude-sonnet-4 and the gateway fails closed.
Tamper with a receiptAfter any allowed request, flip Tamper with region and press Verify. The recomputed Merkle root no longer matches the published one.
Route health dataThe French clinic tenant carries an HDS rule: only the HDS-certified Paris host is eligible, whatever model you pick.

Hashes in the sandbox are real SHA-256 computed in your browser with the Web Crypto API. In production, receipts are Ed25519-signed by the regional notary. How receipts work

Sovereign route ready

Ready to route real traffic?

Start a 14-day production trial with EU, UK and US zones, or bring your architecture to a sovereign architect.

Schedule an architecture demo Start 14-day trial