Three audiences, three lenses. If a question matters to you and isn't here, ask us — we'll add it.
Buying compute from Navon: how it differs from a hyperscaler, what you actually get, and what we don't do.
Five things, all built on the same vertically integrated stack:
Most customers start with one and grow into the others.
Three differences that matter:
For workloads where sovereignty, cost, or proximity matters, the math changes. For workloads that don't care, hyperscalers remain a fine choice.
Hells Gate goes live in Q3 2026 with the first 400 kW Tier III module. Customers signed before commissioning are placed first; the typical onboarding cycle from contract to live workload is 6–10 weeks after the facility opens.
If you have a workload that's date-sensitive, talk to us early — we can sequence module commissioning around committed demand.
If your workload is latency-insensitive, low-density, and has no sovereignty requirement, a hyperscaler is probably cheaper.
Yes. Navon's GPU pods are Ollama-ready for self-hosted open weights — Llama, Mistral, Qwen, DeepSeek — with vLLM, TGI, and TensorRT-LLM available for production serving.
An OpenAI-compatible endpoint sits in front, so SDKs and tools you've already integrated — LangChain, LiteLLM, OpenRouter, LlamaIndex, Cursor — work without code changes. Bring your stack; we provide what's underneath.
Routing platforms are software gateways over third-party model APIs. They aggregate access; they don't own the inference. The compute, the model weights, and the request traffic all live with someone else — usually a hyperscaler outside the jurisdiction.
Navon is the silicon layer. We own the racks, the cooling, and the geothermal baseload. When a model runs on Navon, the weights, the prompts, and the outputs stay in country.
Routing platforms are useful — and many of them will eventually run on top of Navon.
By physics first, contracts second:
"Residency by physical fact, not policy promise" is the test we hold ourselves to.
Three commercial models, depending on how you want to consume:
We publish indicative ranges to qualified customers under NDA. Public price lists come once we're commercially live.
Building with Navon: equipment partners, capital partners, universities, and ecosystem collaborators.
Seven categories:
Email partnerships@navon.cloud with a one-page brief on what you'd bring (technology, capital, market access, talent) and where you'd want to deploy first. We respond within five working days. If there's fit, we move to MOU or pilot inside a quarter.
A structured programme that gives African universities dedicated sovereign compute at growth-market pricing, paired with:
Email partnerships@navon.cloud if you're a university or research institution that wants in.
Yes — if you bring at least one of: a secured site with permits, dedicated baseload power, anchor demand, or DFI-grade capital. Co-build deals are structured as joint ventures with shared infrastructure ownership and a Navon-operated stack on top. Talk to us early; the diligence cycle is typically 90–120 days.
Three things, in priority order:
The engineering questions: density, redundancy, networking, certifications, and the parts of the stack we own outright.
Default is 20 kW+ per rack, GPU-ready, with dual 32 A A+B PDUs (hot-aisle containment). Higher densities (up to 90 kW per rack) are supported in the next-generation pod via direct-liquid cooling — talk to us if your workload needs it.
Site by site, sourced locally and at scale:
Energy is sourced upstream — not offset.
Asterfusion leaf fabric, dual-switch HA: 25 GbE to compute nodes, 100 GbE to storage, dual-corded for redundancy. Carrier-neutral interconnect through Liquid, Safaricom and SEACOM with dual fibre entry into the meet-me room. Direct cross-connects for hyperscaler peering on request.
Navon's cybersecurity layer is built with post-quantum cryptography (PQC) embedded from the ground up — not retrofitted. Quantum Key Distribution (QKD) pathways are on the roadmap for sites with sovereign communications requirements. Key management is HSM-backed, in-country.
This is a deliberate design choice: post-quantum migration is going to be expensive for everyone running TLS 1.2/1.3 with classical key exchange. Building from scratch lets us skip that bill.
We add to this page when real questions come in. Drop us a line and we'll either answer directly — or add it here so the next person doesn't have to.