Region-resident, compliant infrastructure

The PHI network for
cloud compute.

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. PHI is live in Switzerland, the EU, and the US today.

Architecture

Safe and secured compute.

How we guarantee your data remains yours, everywhere in the world.

PHI routing enforced

Every request is classified per call, and PHI traffic routes only to provider/region pairs flagged PHI-eligible in our registry — Infomaniak and Azure in Switzerland, Scaleway and Azure in the EU, Azure in the US. Non-eligible providers carry general traffic only.

Zero training policy

Every compute node operates under a strict zero-training mandate. Your data is processed in memory and immediately discarded. Never logged, never learned.

Regional pinning

Data sovereignty is guaranteed. Requests are hard-routed to compute nodes physically residing in your selected jurisdiction (e.g. CH, EU, US) — a failover never spills across the border.

Audit-ready headers

Every API response carries machine-readable audit headers — x-phi-tier, x-phi-routed, x-phi-attempts — recording the routing decision so compliance reviews are trivial.

Residency

Every call has a postcode.

Eleven jurisdictions, region-resident. Each caller maps to a provider that physically lives inside their region — Infomaniak in CH, Scaleway in the EU, Together AI in the US, Azure for PHI, Google elsewhere.

PHI
CH
Switzerland
Infomaniak · Azure
PHI
EU
European Union
Scaleway · Azure
PHI
US
United States
Azure (PHI) · Together
General
UK
United Kingdom
Google
General
INDIA
India
Google
General
MENA
Middle East · N. Africa
Google
General
ASIA
Asia-Pacific
Google
General
ANZ
Australia · New Zealand
Google
General
LATAM
Latin America
Google
Soon
CHINA
China (PRC)
no eligible host
Fallback
WORLD
Other
Google · worker fallback
PHI request

Must land on a phi_eligible provider in the caller’s region. Anything else returns 403.

No region header

Defaults to the WORLD bucket — never inferred from the IP. Pin the jurisdiction per call with X-Region.

No provider in region

For PHI: hard fail. For general: fall back to the nearest provider, audited in the response headers.

The vendor matrix

See exactly who sits behind each region.

PHI-eligible rows, general-purpose rows, frameworks, and the providers we’re onboarding next — all on one page.

Open the vendor matrix

One network, every region

Spin up a key — the residency posture comes built in.

Pick a region per call. The network keeps every request inside the jurisdiction you named, and proves it on the response.

Free to test · Prepaid credits, no subscription · No data retained