HIPAA-compliant infrastructure
We rebuilt the AI infrastructure layer from the ground up for healthcare and highly regulated industries. Run advanced models on a network where security, reliability, and international compliance are enforced at the router level.
10 named jurisdictions plus a WORLD fallback. Switzerland anchors the PHI tier today.
Architecture
How we guarantee your data remains yours, everywhere in the world.
Every request is classified per call and PHI traffic is routed only to provider/region pairs flagged PHI-eligible in our registry. Today that means Infomaniak (CH) is the sole PHI sub-processor; non-eligible providers carry general traffic only.
Every compute node operates under a strict zero-training mandate. Your data is processed in memory and immediately discarded. Never logged, never learned.
Data sovereignty is guaranteed. Requests are hard-routed to compute nodes physically residing in your selected jurisdiction (e.g., CH, EU, US).
Every API response includes machine-readable audit headers — x-phi-tier, x-phi-routed, x-phi-attempts — recording the routing decision so compliance audits are trivial.
Residency
Eleven jurisdictions, vendor-direct. Each caller maps to a provider that physically lives inside their region — no Bedrock, no Vertex, no Azure OpenAI in the middle.
Must land on a phi_eligible provider in the caller’s region. Anything else returns 403.
We infer from the account country, never from the IP. Override per call with X-Region.
For PHI: hard fail. For general: fall back to the nearest provider, audited in the response headers.
PHI-eligible rows, general-purpose rows, frameworks, and the providers we’re onboarding next — all on one page.