Sovereign Router
Layer 09 · Control plane — Net-new this year
Take an inference request at a single endpoint and place it on metal that is allowed to serve it. Residency is the first rule, and cost, latency and capacity are the rest. A request that must stay in Kenya cannot leave it, and the customer never has to know which site ran the job.
Capabilities
Section titled “Capabilities”- One endpoint across Navon sites, with failover that does not change the customer’s URL
- Placement by residency rule first, then cost, latency, and available capacity
- Commitment routing: a Reserved Lane is a promise about tokens and latency inside a jurisdiction, not about a machine, so it can be honoured on NVIDIA today and AMD next year
- Deny by default: a request bound to one jurisdiction cannot be placed outside it
- Signed proof of where each request ran, carried in the audit trail
- Overflow to partner capacity inside the same jurisdiction
- Federation, so other African operators can serve traffic under Navon’s residency contract