Sovereign AI servers · Saudi Arabia
Own your AI.
Down to the rack.
Sovereign AI servers you buy, keep in your own building and run on your own keys.
NVIDIA GPU hardware with the SoverAIn stack preinstalled: Arabic-first models, inference, retrieval and agents. Delivered, installed and supported in the Kingdom. Nothing to rent from abroad.
ذكاء اصطناعي سيادي، على أرض المملكة
SoverAIn Rack
Rack-scale AI, on your soil.
- 72 Blackwell GPUs
- Liquid-cooled
- SoverAIn stack preinstalled
- Installed in the Kingdom
Illustrative: NVIDIA GB200 rack. Photo: Pokiiri, CC BY-SA 4.0.
Hardware
Three sizes of sovereign AI. Each one ships ready to run.
NVIDIA GPU systems with the full SoverAIn software stack installed, burned in and delivered in the Kingdom. Plug it in, connect your identity provider, and your teams have private AI that day.
Design partners wantedNVIDIA DGX Spark (GB10 Grace Blackwell)
SoverAIn Node
A sovereign AI lab on a desk.
- Compute
- NVIDIA GB10 Grace Blackwell superchip
- Memory
- 128 GB unified memory
- Form factor
- Desktop, standard power
Configure SoverAIn Node →
Design partners wantedNVIDIA HGX B200, 8-GPU
SoverAIn Server
Eight GPUs for production inference and fine-tuning.
- Compute
- NVIDIA HGX B200: eight Blackwell GPUs with NVLink
- Form factor
- Rack-mounted server for your data centre or ours
- Cooling
- Air-cooled
Configure SoverAIn Server →
On the roadmapNVIDIA GB200 NVL72
SoverAIn Rack
Rack-scale AI for national and enterprise workloads.
- Compute
- 72 NVIDIA Blackwell GPUs and 36 Grace CPUs in one NVLink domain
- Form factor
- Full rack, delivered integrated
- Cooling
- Liquid-cooled
Configure SoverAIn Rack →
Product photos are illustrative NVIDIA hardware, not SoverAIn units. NVIDIA, DGX, HGX, Grace and Blackwell are trademarks of NVIDIA Corporation; their use here does not imply endorsement. Configurations are indicative and agreed per order.
Ownership
Buy it, have us host it, or start in our cloud.
Own
Buy the hardware
SoverAIn Node, Server or Rack, bought outright and installed in your own facility. The boxes, the keys and the logs are yours.
- On your premises, on your network
- Connected or fully air-gapped
- Run by your team, or supported by ours
Host
Your hardware, our data centre
Hardware dedicated to you, racked and operated by SoverAIn in an in-Kingdom data centre. Nothing is shared with another customer.
- Reserved GPUs, single tenant
- Your keys in your HSM
- Move it on-site later if you want
Start
SoverAIn Cloud
Start in days on shared in-Kingdom capacity, then move to your own hardware when the workload is proven.
- Per token, in riyals
- Same API as the hardware
- Logically isolated tenants
Why now
AI moved faster than the rules about where your data may go. The rules have caught up.
PDPL
Personal data has a home address
The Personal Data Protection Law, enforced since September 2024, restricts transfers of personal data outside the Kingdom to defined conditions. Every prompt that carries a name, an ID or a medical note is a transfer question.
NCA
Cyber controls reach the model
NCA Essential and Cloud Cybersecurity Controls expect asset inventories, access control, logging and third-party risk management. An offshore model API is a third party, and its logs live somewhere you do not control.
CST
Cloud is regulated in-Kingdom
CST's Cloud Computing Regulatory Framework sets the rules for cloud services offered in Saudi Arabia, and government data classification decides where workloads may run.
SDAIA
AI must be explainable and accountable
SDAIA AI Ethics Principles and its generative AI guidance ask for transparency, reliability, privacy and a named human accountable for outcomes.
The practical problem: the most useful AI work uses the most sensitive data. Contracts, case files, customer records and medical notes are exactly what cannot be pasted into an offshore chatbot.
What sovereign means
Not a data-centre address. A set of properties you can check.
Who holds the keys, who can be compelled, who operates the system, and what you can prove afterwards.
01
Data residency
Prompts, documents, embeddings, outputs and logs are stored and processed in the Kingdom. Nothing is sent to an offshore API unless you switch it on, in writing.
02
Model control
Open-weights and Arabic-first models you can inspect, pin by version and fine-tune. Weights trained on your data stay yours and never leave your tenancy.
03
Operational sovereignty
Operated from Saudi Arabia, with privileged access limited to named, vetted staff and every session recorded.
04
Your keys
Encryption keys held in an HSM you control. Revoke the key and the data is unreadable, including to us.
05
Saudi jurisdiction
Contracts, data processing agreements and dispute resolution under Saudi law, with no foreign parent able to compel access.
06
Evidence, not assurances
Every model call logged with the model version, policy applied, user and data sources, exportable to your SIEM and your auditors.
Every hop stays home
Follow one request through the stack.
One request, traced
0 hops abroad- 1Your userRiyadh office
- 2Inference gatewayIn-Kingdom
- 3Guardrails and PII redactionIn-Kingdom
- 4Retrieval over your documentsIn-Kingdom
- 5ModelIn-Kingdom GPU
- 6Audit logIn-Kingdom
The same request on an offshore API
Prompt, documents and output cross the border at step 5, and the log stays with the provider.
Outside the Kingdom
The difference
An offshore model API and SoverAIn, side by side
| Question | Offshore model API | SoverAIn |
|---|---|---|
| Where prompts and outputs are processed | Wherever the provider runs the model | In the Kingdom, in your chosen tenancy |
| Who can be compelled to disclose data | The provider, under its home-country law | No foreign parent; Saudi law only |
| Model version | Changes when the provider updates it | Pinned by you; upgrades tested on your evaluation set |
| Fine-tuning on your data | Weights stay with the provider | Weights stay in your tenancy |
| Encryption keys | The provider's | Yours, in an HSM you control |
| Audit trail | What the provider chooses to expose | Every call, policy and source, exported to your SIEM |
| Arabic quality | English-first models | Arabic-first models evaluated on your own Arabic content |
| Cost model | Per token, in foreign currency | Per token, or reserved capacity, in riyals |
Deployment
Three ways to run it. The same controls in each.
Managed, in-Kingdom
Design partners wantedSoverAIn Cloud
The platform as a service, from in-Kingdom data centres. Logically isolated tenants, customer-managed keys, no setup.
Best for: Teams that want to start quickly with public or restricted data.
Single-tenant
Design partners wantedSoverAIn Dedicated
Your own GPUs, network and storage in an in-Kingdom facility, operated by SoverAIn. Nothing is shared with another customer.
Best for: Regulated workloads that need physical isolation and reserved capacity.
Your data centre
Design partners wantedSoverAIn Private
SoverAIn hardware you own, installed in your own facility, connected or fully air-gapped, operated by your team or ours.
Best for: Classified environments and organisations that must hold the hardware.
Use cases
Built for the work that could not go to the cloud.
Government
Correspondence, policy and citizen services in Arabic, with classified data kept at home.
Data: Restricted to Top Secret
Banking & insurance
Read the documents, keep the customer data in the Kingdom.
Data: Restricted to Secret
Healthcare
Clinical notes and medical records never leave the Kingdom.
Data: Secret
Energy & industry
Decades of engineering documents, searchable in one place.
Data: Restricted to Secret
Legal & professional services
Client confidentiality that holds up to a client audit.
Data: Restricted
Education & research
AI for students and researchers on accredited, in-Kingdom infrastructure.
Data: Public to Restricted
Start here
A six-week design-partner pilot on one use case and your own data.
Week 1
Scope
- Use case, data classification and success measure agreed
- Deployment model and residency set out in writing
- DPA signed under Saudi law
Week 2
Connect
- Tenant and keys provisioned
- First documents or systems connected
- Your evaluation set assembled, in Arabic and English
Weeks 3 to 5
Prove
- Models compared on your evaluation set
- Guardrails and access policies tuned
- Pilot users working in the assistant or on the API
Week 6
Decide
- Quality, cost and latency report
- Security review with your team
- A go or no-go for production
Bring the workload you could not send abroad.
Tell us the use case and the data classification. We will tell you which deployment fits and what a pilot would prove.