Case study · Specialise

Healthcare changed
the starting point.

The African Healthcare Cloud did not begin with the virtual machine. It began with what healthcare demands — sovereignty, identity, auditability, controlled access, local recovery — and the same Oasis Stack foundation that runs YallaCloud was shaped around them.

Talk to us All case studies
African Healthcare CloudIndustry cloudDelivered
A white hospital and a frosted-glass data hall side by side under a translucent protective dome, connected to a glass cloud above
Role
Specialise
Model
Industry cloud
Operator
Healthcare ecosystem
Infrastructure
Sovereign, local
Primary need
Governance and adaptation
Status
Delivered
The question

Can the same foundation adapt around healthcare sovereignty and governance?

Most clouds are built compute-first and made compliant afterwards. Healthcare cannot work that way round. Patient data, clinical systems and the people allowed to reach them set the rules before a single workload is placed — so the platform had to start from those rules, not bolt them on.

Start with the constraints

Five requirements came first.

Each one is a design decision the architecture had to answer before anything else was built.

Data sovereignty
Patient and clinical data kept under local jurisdiction, with the platform deciding where it may live — and customer data never moving automatically.
Security and identity
Every person and system identified, every privilege granted deliberately, and access decided inside the boundary.
Auditability and availability
A record of who touched what and when, and clinical services that stay up when it matters.
Controlled data access
Access granted per role, per purpose and per dataset, rather than per environment.
Local deployment and recovery
Infrastructure and recovery that stay in the region the data belongs to.
Shape the operating foundation

One platform, shaped around the requirements.

Nothing here is a separate build. It is the same Oasis Stack foundation, configured from healthcare’s constraints outward.

Infrastructure
Local compute, storage and networking, published as governed services rather than handed over as hardware.
Governance
Identity, policy and audit enforced on every service, with the evidence produced by the platform itself.
Operations
Monitoring, lifecycle management and support treated as part of the product, not an afterthought.
Ecosystem enablement
A way for providers and partners to take part, each inside the rules the cloud enforces.
Service lifecycle
Services defined, ordered, provisioned, operated and billed through one lifecycle.
Delivered

What the healthcare cloud runs.

An industry cloud, not a hosting contract: the services a healthcare ecosystem actually consumes.

  • Healthcare applications
  • Provider participation
  • Data services
  • AI workloads
  • Managed services

Deployment metrics are published only once they are approved for external use. Until then, this study describes what was built, not how much of it.

What it proves

Two deployments. One platform.

The same foundation supports different operators, ownership models and outcomes. That is the point of a platform rather than a project.

YallaCloudAfrican Healthcare Cloud
RoleOperate & federateSpecialise
Operating modelOperator cloud, federated across locationsIndustry cloud
OperatorCloudHostHealthcare ecosystem
InfrastructureCloudHost-operated, multiple locationsSovereign, local
Primary needCommercial operations and federationGovernance and adaptation
StatusIn productionDelivered
Operate. Federate. Specialise.

Building a cloud for one industry?

Start from the constraints your sector cannot bend. We will show how the same foundation shapes around them.

Talk to us All case studies