How it deploys
One codebase. Your boundary. Your model.
HealthNext deploys as per-customer, single-tenant isolated instances. There is no shared production data plane. Choose where it runs — your cloud, a dedicated instance we run for you, or a synthetic sandbox to evaluate — and the boundary, gate, and audit model are identical across all three.
BYOC
Your own cloud
HealthNext runs inside your cloud account. The control plane is managed; the data plane lives entirely in your boundary. PHI and PHI-derived artifacts never leave your account — only de-identified operational metrics do. This is the production posture for payers and providers who need their data to stay home.
- Data plane in your cloud, control plane managed
- Single-tenant isolation — no shared data plane
- PHI never leaves your account
- Your model, served on an endpoint you control
Managed-dedicated
A dedicated instance, run for you
When you want to move fast without standing up cloud infrastructure first, HealthNext runs a dedicated, single-tenant instance on your behalf. It is isolated per customer — not a shared tenant — and is built to migrate to BYOC when you are ready, without re-platforming.
- Single-tenant, isolated per customer
- No cloud setup required to begin
- Designed to graduate to BYOC cleanly
- Same boundary, gate, and audit model
Demo
A synthetic sandbox
The demo plane is public and runs on synthetic data only — no PHI, ever. It is where you and your team can walk the workflows, see the bridge run end-to-end, and pressure-test the experience before a single integration is wired.
- Synthetic data only — no PHI
- Public, no procurement required
- Full workflow walkthroughs
- Separate from any customer instance
Two planes
The marketing plane and the product plane never mix.
The public site and the demo are one plane, carrying no PHI. Every real deployment is its own isolated instance on the product plane. The separation is deliberate — it keeps your data in your boundary and keeps the public surface clean.
Marketing + demo plane
Public. One site. Synthetic data only.
Product plane
Per-customer, single-tenant, isolated instances.
Start in the sandbox. Graduate to your boundary.
Walk the demo on synthetic data, then move to a dedicated instance or your own cloud — same product, same controls, no re-platforming.