Sovereign Routing

Pin your AI workloads to specific countries. Ryvion enforces jurisdiction at the network level through verified node locations and latency probing -- not just a policy checkbox.

How it works

1. Node verification -- when an operator registers a node, Ryvion verifies its physical location through timezone checks, latency probing, and VPN/proxy detection
2. Jurisdiction tagging -- each verified node is tagged with its country code
3. Request routing -- when you specify a jurisdiction in your API call, the scheduler only routes to nodes in that country
4. Enforcement -- nodes that fail location verification or are detected using VPNs are automatically blocked

Available jurisdictions

Ryvion supports country-level routing to any jurisdiction where verified nodes are online. You can also use EU to route to any EU member state. Current active node locations include Canada and Germany, with more jurisdictions added as operators join.

Setting jurisdiction

Per API key

Set a default jurisdiction on your API key from the API Keys dashboard. Every request using that key will be routed to the specified jurisdiction unless overridden per request.

Per request

Override or set jurisdiction on individual requests:

Chat completions

curl -X POST https://api.ryvion.ai/v1/chat/completions \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "phi-4",
    "messages": [{"role":"user","content":"Hello"}],
    "jurisdiction": "DE"
  }'

Knowledge bases

Pin a knowledge base and its embeddings to a specific jurisdiction:

curl -X POST https://api.ryvion.ai/api/v1/knowledge-bases \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name":"eu-docs","jurisdiction":"DE"}'

Agent hosting

Deploy agents in a specific country:

curl -X POST https://api.ryvion.ai/api/v1/agents/deploy \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "eu-agent",
    "container_image": "ghcr.io/myorg/agent:latest",
    "jurisdiction": "DE"
  }'

Why this matters

Data residency

Some regulations require that data processing happens within specific countries. Sovereign routing guarantees your data stays in the jurisdiction you choose.

EU AI Act

Article 14 of the EU AI Act requires transparency about where AI processing occurs. Ryvion's sovereign routing combined with cryptographic receipts provides verifiable proof of processing location.

Client requirements

Enterprise clients often require data processing within their country or region. Sovereign routing lets you meet these requirements without building separate infrastructure.

Verification methods

Ryvion uses multiple methods to verify node locations:

• Timezone verification -- node system timezone must match claimed location
• Latency probing -- network latency to known reference points must be consistent with claimed location
• VPN detection -- connections through VPNs, proxies, or tunnels are detected and blocked
• Continuous monitoring -- location verification runs continuously, not just at registration

Sovereign tier

For organizations with strict data residency requirements, the sovereign tier provides:

• Country-level enforcement -- workloads are guaranteed to execute in the specified country with contractual backing
• Legal agreements -- data processing agreements (DPAs) specific to each jurisdiction
• Compliance packages -- pre-built documentation for GDPR, PIPEDA, and other regulatory frameworks
• Priority routing -- sovereign tier requests get priority access to nodes in the requested jurisdiction

Contact sales@ryvion.com to enable sovereign tier.

Default behavior

If you don't specify a jurisdiction, the scheduler routes to the fastest available node regardless of location. The receipt will still show which jurisdiction processed your request.