Sahab · Pitch Deck
Healthcare · SOVEREIGN INFRASTRUCTURE
Sahabسحاب
In-Kingdom landing zones built for the EMR, not around it.
neuriya.ai — Sovereign, Arabic-first enterprise AI
Problem
Hospital cluster operators bolt analytics onto the EMR instead of governing the data underneath it
- Clinical records, imaging, claims, and population data sit in silos across the EMR, PACS, and NPHIES feeds with no shared, governed data layer connecting them.
- Building a FHIR ingestion pipeline from scratch for every new analytics or research initiative delays each project by months.
- Access to sensitive clinical data is typically controlled at the application level, not enforced at the field level against its actual classification tier.
- Multi-facility cluster operators re-architect their data infrastructure each time they add a hospital, instead of scaling a reference design.
Solution
An in-Kingdom landing zone built around the EMR, with governance enforced at ingest
Product
Sahab in action
How it works
From first touch to outcome
Provision
A landing zone is stood up in-Kingdom, sized to the cluster and its expected workloads.
Ingest
EMR, PACS, and NPHIES data streams in continuously over HL7 FHIR R4 into classification-tagged lakes.
Govern
PDPL-aligned access policies are enforced automatically at the field level, not by manual review.
Operate
Clinical, analytics, and research teams draw from governed data without ever moving it outside the zone.
Market
Sizing the opportunity
- TAM — $1.2B. MENA sovereign healthcare data infrastructure & cloud market
- SAM — $130M. Saudi in-Kingdom hospital data-platform market
- SOM — $9M. 3-year obtainable share via design-partner cluster operators
NDMO's classification requirements, alongside the Kingdom's Vision 2030-driven hospital-cluster consolidation, are pushing cluster operators to replace ad hoc, per-project data integration with a governed, in-Kingdom platform they can scale as new facilities join.
Business model
How Sahab makes money
Per-facility landing-zone subscription
Recurring fee per hospital facility connected to the landing zone, scaled to data volume and workload.
Cluster-operator platform license
Enterprise pricing for multi-facility cluster operators covering the full reference architecture.
Implementation & FHIR-integration fee
One-time fee to provision the landing zone and connect EMR, PACS, and NPHIES feeds at each site.
Revenue streams
Where the revenue actually comes from
Competition
Where we win
Our edge
- Purpose-built reference architecture for hospital clusters, not a bespoke systems-integrator build repeated at every new facility.
- NDMO classification and field-level access control enforced at ingest, not bolted on after the data lake already exists.
- True in-Kingdom hosting for every landing zone and replica, not a regional presence of a foreign-parent hyperscaler.
- Founding team pairs Saudi enterprise data-platform delivery experience with hands-on cloud engineering.
Traction
Architecture proven, one facility away from live data
- The sovereign data-platform product is built end-to-end: landing-zone provisioning, data lake registry, and FHIR ingestion monitoring, not a reference-architecture slide deck.
- Architecture pre-aligned to PDPL, NDMO Classification, MoH Standards, HL7 FHIR R4, NPHIES, and ISO 27001.
- Actively selecting design-partner cluster operators for a first hospital cloud cohort.
Go-to-market
One facility first, cluster-wide on the same reference architecture
- 1Land with 1-2 design-partner cluster operators, starting with a single facility's EMR, PACS, and NPHIES feeds.
- 2Prove ingestion reliability and field-level access compliance over a pilot period against the cluster's existing manual processes.
- 3Expand facility by facility across the cluster operator's network using the same reference architecture.
Team
Built by operators, not just builders
The ask
Raising a seed round to stand up the first design-partner landing zone
We're raising to fund landing-zone deployment tooling, NPHIES/FHIR integration work, and the core data-platform and engineering team through first-revenue.