Hima · Pitch Deck
Defence & Security · SOVEREIGN INFRASTRUCTURE
Himaحِمى
Sovereign landing zones for classified workloads — air-gap-capable, with no public-cloud dependency.
neuriya.ai — Sovereign, Arabic-first enterprise AI
Problem
Standing up an accredited environment for classified workloads is a slow, one-off project every time
- Each new classified workload starts its accreditation process from a blank architecture, instead of a pre-validated design for its classification tier.
- Public-cloud control planes sit outside sovereign infrastructure by default, creating a foreign-dependency question that has to be resolved case by case.
- Air-gapping a workload when the mission requires it is typically a custom engineering exercise, not a standard deployment option.
- Accreditation status is usually confirmed at a point-in-time review, so a control that quietly drifts out of compliance can go unnoticed for months.
Solution
Sovereign landing zones for classified workloads — air-gap-capable, with no public-cloud dependency
Product
Hima in action
How it works
From first touch to outcome
Design
A reference architecture is selected or adapted to the workload’s required classification tier.
Provision
The landing zone is stood up within sovereign infrastructure, air-gapped if the mission requires it.
Accredit
Network segregation review and independent penetration testing proceed before workloads go live.
Sustain
Scheduled scans and control checks keep the accreditation posture current for as long as the zone runs.
Market
Sizing the opportunity
- TAM — $3.4B. GCC sovereign & classified cloud-infrastructure market
- SAM — $420M. Saudi accredited landing-zone & classified workload hosting spend
- SOM — $28M. 3-year obtainable share via accredited design-partner entities
NDMO and NCA ECC-2 mandates for sovereign hosting of classified workloads, combined with Vision 2030's push to reduce reliance on foreign hyperscalers for sensitive government infrastructure, are turning accredited landing zones into a standing procurement category rather than a one-off project.
Business model
How Hima makes money
Per-landing-zone license
Priced by the number and classification tier of landing zones provisioned.
Continuous accreditation subscription
Recurring fee for scheduled vulnerability scans and control checks that keep accreditation posture current.
Design & provisioning fee
One-time fee to design and stand up the reference-architecture landing zone.
Revenue streams
Where the revenue actually comes from
Competition
Where we win
Our edge
- Pre-validated reference architectures per classification tier shorten the path from request to accreditation, instead of starting from a blank design each time.
- Zero control-plane dependency on public cloud providers — provisioning and orchestration run entirely within sovereign infrastructure.
- Air-gap-capable by design, with no functional compromise, for missions that require full disconnection.
- Founding team combines Saudi sovereign-infrastructure delivery experience with cloud and security engineering.
Traction
Early validation, built for pilot readiness
- Full sovereign landing-zone experience designed and built end-to-end: landing-zone dashboard, workload registry, and accreditation request workflow.
- Architecture pre-aligned to NDMO Classification, NCA ECC-2, CCC, and ISO 27001.
- Actively selecting design-partner entities for a first accredited landing-zone pilot cohort.
Go-to-market
Land on one landing zone, expand across classification tiers
- 1Land with 1-2 design-partner entities standing up a first accredited landing zone for a single classification tier.
- 2Prove accreditation-cycle time and continuous-posture accuracy over a pilot deployment against the entity's prior accreditation process.
- 3Expand to additional classification tiers and workloads within the same entity, then to further entities through the accreditation relationships built.
Team
Built by operators, not just builders
The ask
Raising a seed round to reach first accredited landing-zone pilots
We're raising to fund reference-architecture development, accreditation-review tooling, and the core infrastructure team through first-revenue pilot deployments.