Honest about what's ready — and what's gated.
We tell you what's true today.
For healthcare and other regulated buyers, we're explicit about the line. What's true today: a medical or healthcare vertical is classified as requiring a dedicated instance and is refused a shared one outright — the router returns no endpoint rather than placing that tenant on the pool. Every action lands on a chained audit record you can export. Demos run on synthetic fixtures, and a test fails the build if a real name or a real vault path gets back into them.
What's gated: no live protected health information (PHI) flows through the system until a Business Associate Agreement (BAA) and PHI readiness clear. Be clear-eyed about what that gate is — it is sequencing and a signed agreement, carried out by people. The one piece of it the code holds is the refusal to put a medical tenant on the shared pool.
Medical verticals refuse the shared pool
Live todayClassified dedicated regardless of tier, and returned no endpoint at all rather than a shared one. A fail-safe, not a preference.
Non-medical dedicated tiers may fall back; medical does not
Synthetic demo fixtures, test-enforced
Live todayThe signed-out demo runs on synthetic data, and a regression test fails the build if a real identifier reappears in it — after that happened once, in production.
PHI gated behind a BAA
Gated postureNo live PHI pre-BAA. This is a delivery sequence and a signed agreement, not a switch in the product.
A dedicated instance actually stood up
RoadmapThe routing, the registry and the admin path exist; standing an instance up is a manual runbook, and no code provisions one inline.
The verifiability claim is always one click from a way to check it — no account, no trust required.