Skip to content

Now selecting the first cohort of facilities in Sierra Leone. Request a briefing

Deployment

Three ways to run it. One codebase.

How HealthOS is hosted is a procurement and sovereignty decision, not a product decision. The platform is designed to be the same in all three.

Choose a deployment model

Clinics and hospital groups

Managed cloud

HealthOS will run it. Designed as the fastest path to production: no infrastructure team required, regional hosting.

Insurers and large networks

In-country cloud

Designed to be deployed to a national or regional cloud region, so data residency requirements are satisfied by architecture, not by policy promise.

Ministries and public health systems

Sovereign / on-premise

Designed to run inside government infrastructure, operated by your team with our support, with full control of data, keys and upgrade cadence.

Managed cloud

Illustrative: A simplified diagram, not an architecture specification.

Inside the country

  • Your infrastructure

    Government or institutional

    • —

  • In-country cloud region

    National or regional provider

    • —

  • HealthOS

    Regional hosting and operations

    • Data
    • Keys
    • Operations team

Data and keys will sit in HealthOS's regional hosting, the keys in a key service separate from application access. HealthOS will operate it.

  • Migration from existing systems will be part of onboarding, not a separate project.
  • Facility operations are designed to continue during connectivity loss and reconcile automatically.
  • Full data export in open formats will be available on request, at any time.

If it runs where you are, the next step is a conversation. Not a procurement process. We are selecting the first cohort of facilities now.

Request a briefing