Shadow Warden AI — Gateway v7.10 — Explore the API Reference
Sovereign AI Cloud · 11 features shipped

Your AI Traffic.
Your Jurisdiction.

MASQUE-protocol encrypted tunnels across 8 jurisdictions. Every AI request is routed to a jurisdiction-compliant tunnel with a cryptographically signed attestation.

8 Jurisdictions · Always Compliant

Traffic is routed to the lowest-latency ACTIVE tunnel in an allowed jurisdiction for the request's data class.

EU
European Union
US
United States
UK
United Kingdom
CA
Canada
SG
Singapore
AU
Australia
JP
Japan
CH
Switzerland
Data Class EUUSUKCASGAUJPCH
GENERAL ✓✓✓✓✓✓✓✓
PII ✓✓✓✓~~~✓
FINANCIAL ✓✓✓✓~~~✓
PHI ✓✓✓✓✗✗✗✓
CLASSIFIED ✗✗✗✗✗✗✗✗
✓ Allowed ~ Adequacy check required ✗ Blocked

All Tunnel Features

Sovereign routing layer. Built and tested; not part of any plan today.

CP-12 ✓ Shipped
8-Jurisdiction Registry
Sovereign AI Cloud · v4.4

EU, US, UK, CA, SG, AU, JP, CH jurisdictions with AI regulations, compliance frameworks, and data classification transfer rules matrix. Adequacy decisions for EU↔UK/CA/JP/CH.

Not on a plan
CP-13 ✓ Shipped
MASQUE Tunnel Protocol
MASQUE Tunnels · v4.4

MASQUE_H3, MASQUE_H2, CONNECT_TCP protocol support. TOFU TLS pinning via SHA-256 fingerprint. Lifecycle: PENDING → ACTIVE → DEGRADED → OFFLINE.

Not on a plan
CP-14 ✓ Shipped
Sovereign Routing Engine
Per-Tenant Routing · v4.4

Picks lowest-latency ACTIVE tunnel in allowed jurisdictions. Prefers preferred_tunnel_id. Checks compliance before routing. BLOCK/DIRECT fallback modes.

Not on a plan
CP-15 ✓ Shipped
Sovereignty Attestation
Per-Tenant Routing · v4.4

HMAC-SHA256 signed attestations. Redis 7-year TTL. Verify endpoint for audit. 10,000 cap per tenant. SOVEREIGN_ATTEST_KEY env var.

Not on a plan
CP-16 ✓ Shipped
Data Classification Matrix
Sovereign AI Cloud · v4.4

Transfer rules per data class: CLASSIFIED (never), PHI (US/EU/UK/CA/CH only), PII/FINANCIAL/GENERAL (all, adequacy check). Sovereign Pod Tags per entity.

Not on a plan
CP-17 ✓ Shipped
Per-Tenant Routing Policy
Sovereign AI Cloud · v4.4

Per-tenant data-class overrides (PHI→US only, CLASSIFIED→none). BLOCK/DIRECT fallback. Redis-backed with in-memory fallback.

Not on a plan
CR-06 ✓ Shipped
Async TCP Health Probing
MASQUE Tunnels · v4.4

probe_tunnel() async TCP health-check on configured endpoint. Marks tunnel ACTIVE on first success, DEGRADED after 2 failures, OFFLINE after 5.

Not on a plan
CR-15 ✓ Shipped
QUIC/HTTP3 Support
MASQUE Tunnels · v4.7

Caddy v2 UDP 443 for QUIC/HTTP3. Alt-Svc header injection. HSTS enforced. hostname-based routing: api/app/analytics/landing subdomains.

Not on a plan
CP-22 ✓ Shipped
Cross-Border Transfer Rules
Per-Tenant Routing · v4.4

Adequacy decisions matrix: EU↔UK, EU↔CA, EU↔JP, EU↔CH. is_transfer_allowed() checks data class + source/dest jurisdiction. Non-adequate transfers blocked.

Not on a plan
CP-23 ✓ Shipped
GDPR Art. 35 DPIA
Sovereign AI Cloud · v4.4

Data Protection Impact Assessment for sovereign routing decisions. Article 35 documentation, risk mitigations, residual risk scoring.

Not on a plan
CP-24 ✓ Shipped
Sovereignty Report API
Sovereign AI Cloud · v4.4

GET /sovereign/report — full jurisdiction compliance summary, active tunnels, attestation count, routing decisions, adequacy partners.

Not on a plan
🔏 Sovereignty Attestation

Every routing decision
gets a signed receipt

Each request routed through a sovereign tunnel generates an HMAC-SHA256 signed attestation stored in Redis with a 7-year TTL. Auditors can verify any historical routing decision.

Signature HMAC-SHA256 over attest_id|request_id|tenant_id|jurisdiction
Storage Redis 7yr TTL · 10,000 cap per tenant
Verification GET /sovereign/attest/{id}/verify — re-derives signature
Key SOVEREIGN_ATTEST_KEY → fallback VAULT_MASTER_KEY
Attestation object
{
  "attest_id": "att_0Xk4aB7mN2p",
  "request_id": "req_8f3a2c1d",
  "tenant_id":  "acme-corp",
  "jurisdiction": "EU",
  "tunnel_id":  "tun_eu_h3_01",
  "data_class": "PHI",
  "compliant":  true,
  "issued_at":  "2026-05-27T14:32:01Z",
  "signature":  "sha256:a3f9b2..."
}
🌐

Sovereign AI Cloud is not on a plan today

The routing layer is built and tested. No plan includes it, so it cannot be bought.