Skip to main content
Hydor Health

Platform · Deployment

Onenode,onecountry.Oronehealthsystem.Oronemilitarydepartment.

The Sovereign Health Node is the unit of deployment for everything Hydor builds. It runs inside a national data center, inside a hospital network, on-premise in a federal facility, or in a hybrid configuration. The operator picks the substrate. Data residency is the default.

Deployment topology

One node, one operator

Each node runs the full Hydor stack. Identity, MIM family, Dr. Kai, governance, communication, and the marketplace. Nodes can federate. Two nodes can share specific data under explicit, auditable consent. Federation is opt-in. The default state of any node is isolation.

The five-phase deployment

Deployment follows the same five phases whether the customer is a country, a federal department, or a health system. The phases are designed so value shows up early, inside the first six months, and grows compounding from there.

  • Phase 1 · Alignment (0–3 months)MOU, governance setup, the clinical and regulatory leadership who will sit on the Oversight Panel. Trust is the deliverable.
  • Phase 2 · Pilot (3–6 months)First clinical sites go live with a defined cohort and a defined readout. Proof is the deliverable.
  • Phase 3 · Scale-up (6–18 months)Major hospitals and ministry data flow into the node. Scale is the deliverable.
  • Phase 4 · Platform economy (Year 2–3)Apps, devices, and insurers list inside the country marketplace. Economy is the deliverable.
  • Phase 5 · Federation (Year 3+)The country joins the wider Hydor federation on its own terms. A cross-border health intelligence network is the deliverable.

The four deployment modes

Hydor sizes the node to the operator. Same platform. Different posture.

  • National Sovereign NodeFor a ministry of health. Anchored in-country. Governed by local clinical and regulatory boards.
  • Federal Sovereign NodeFor a US federal department or military health command. Air-gapped or controlled-network configurations available.
  • System Sovereign NodeFor a health system or large provider network. Sits inside the system's existing private cloud or on-prem environment.
  • Humanitarian MeshA deployment mode designed for crisis response. Portable, satellite-fallback, runs disconnected when needed.

What the operator controls

Every Hydor deployment lets the operator decide, on the record, which MIMs are activated, which Clinical Circuits run, which data may be federated, which AI models may be called, and which audit reports go to which regulator. The platform makes these choices explicit and reviewable, not buried in configuration.

Five phases

Value at six months. Compounding from there.

The deployment model is the same whether the customer is a country, a federal department, or a health system.

From MOU to federation. One model, every customer.

Deployment modes

Four deployment shapes. One platform underneath.

The same Hydor OS adapts to ministry, federal, provider, and crisis environments. Each shape carries the same governance posture.

  • National Sovereign Node

    For a ministry of health. Anchored in-country, governed by local clinical and regulatory boards.

    Ministry

  • Federal Sovereign Node

    For a US federal department or military health command. Air-gapped or controlled-network configurations available.

    Federal

  • System Sovereign Node

    For a health system or large provider network. Sits inside the system's existing private cloud or on-prem environment.

    Provider

  • Humanitarian Mesh

    A deployment mode designed for crisis response. Portable, satellite-fallback, runs disconnected when needed.

    Crisis

Topology at a glance

Same platform behaviour. Different sovereignty boundary.

Left: an on-prem Sovereign Node inside the ministry boundary. Right: the same node inside a private-cloud tenant. The clinical and governance surface is identical. The sovereignty posture is the variable.

What the operator controls

Every choice on the record.

The operator decides what runs on their sovereign node. Not Hydor. Not a vendor. The operator, on the record, with a full audit trail.

Five decisions. Five accountable signatures.

  • Which MIMs are activated
  • Which Clinical Circuits run
  • Which data may be federated
  • Which AI models may be called
  • Which audit reports go to which regulator

The platform is built to make these choices explicit and reviewable, not buried in configuration.

How a deployment goes

Four phases. Six months to first clinical pilot.

Four named phases. Pacific Health Resilience and the federal AI governance program already run through this exact flow. Nothing custom on the first deployment.

01

Sovereign briefing

A scoped conversation with the Office of the CIO. We map the ministry, agency, or health system context against the Hydor OS deployment model.

02

Node design

Architecture review and Sovereign Health Node provisioning. Data residency, federation rules, and the HealthID identity layer are defined with your team.

03

THIA governance

Truth Checker, AutoRAG, Clinical Oversight Panels, and the Five Ethics Pillars are configured to your regulatory and clinical posture before any model goes live.

04

Deployment & oversight

Dr. Kai, MyVoice, and the platform products go live with continuous audit. Cryptographic attestations make every consent and every clinical decision provable.

Next step

Continue with Hydor Health.

Request a deployment briefing