Skip to content

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 and the EU, and for documents and speech in the US.

Architecture

Safe and secured compute.

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

01

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, and Azure in the US for OCR, speech-to-text and text-to-speech (US chat, vision and embeddings PHI are not available). Non-eligible providers carry general traffic only.

02

No training by CloudSitus

CloudSitus never trains on your data and stores no prompts or responses — requests pass through in memory. PHI only reaches providers whose DPA or BAA we have reviewed; general traffic is governed by each vendor’s own API terms, and we send a vendor’s per-request training opt-out where one exists (Deepgram).

03

Regional pinning

Each request routes only among providers that serve the jurisdiction you select. PHI goes only to resident, PHI-eligible hosts in CH, the EU or the US and never crosses a border. For general traffic the resident provider ranks first in CH, the EU and the US; global clouds that serve the region (and process globally) are later fail-overs there, and serve the other regions. Pin a model to keep a call on that model.

04

Audit-ready headers

Every routed 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, each with its own routing. In CH, the EU and the US the first provider is resident in that region — Infomaniak in CH, Scaleway in the EU, Together AI in the US, Azure for PHI documents and speech. The other named regions are served by Google, which processes globally, and WORLD has no resident provider and runs in price order.

  • CHPHI

    Switzerland

    Infomaniak · Azure

  • EUPHI

    European Union

    Scaleway · Azure

  • USPHI

    United States

    Together AI · Azure

  • UKGeneral

    United Kingdom

    Google

  • INDIAGeneral

    India

    Google

  • MENAGeneral

    Middle East · N. Africa

    Google

  • ASIAGeneral

    Asia-Pacific

    Google

  • ANZGeneral

    Australia · New Zealand

    Google

  • LATAMGeneral

    Latin America

    Google

  • CHINASoon

    China (PRC)

    no eligible host

  • WORLDDefault

    Other

    OpenAI

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

Refused, never rerouted: 403 phi_blocked when only a PHI host is missing, 422 no_route when nothing in the region serves that modality. No silent hop to another region.

The vendor matrix

See exactly who sits behind each region.

PHI and general-purpose status, the regulations that apply, and who serves each region — all on one page.

One network, every region

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

Pick a region per call. The router serves it only from providers for that region, keeps PHI on resident hosts, and names the model that answered on the response.

Prepaid credits from $10 · No subscription · No data retained