Solution · Medical transcription

Transcription at scale, without leaving the region.

Whisper-class transcription on the OpenAI audio shape, per-minute billed, pinned to Switzerland, the EU or the US with no cross-border failover.

Get started Read the docs

The problem

Why this is hard

Dictation and consult recordings are high-volume and unambiguously PHI. Transcription vendors often process audio wherever capacity is cheapest — which is exactly what a regulator asks about. CloudSitus gives you Whisper-class transcription that resolves to a same-jurisdiction host, bills by the minute, and returns the subtitle formats your tooling already expects.

How it works

The pipeline, end to end

Step 1: Send the audio
POST /v1/audio/transcriptions
Multipart upload with model=whisper, X-Region and X-PHI:true. Choose json, text, srt, vtt or verbose_json depending on what you need downstream.
Step 2: Stay in jurisdiction
Residency-separate
PHI transcription runs on Microsoft Azure in CH, Scaleway in EU and Microsoft Azure in US. There is no cross-border failover — a failed CH call is a CH error, not a quiet EU completion.
Step 3: Summarise (optional)
POST /v1/chat/completions
Pipe the transcript into a resident chat model for a structured summary, action items or coding suggestions — same region, same PHI gate.
Step 4: Pay per minute
x-phi-cost-micro
Billing is per minute of audio. Every response reports its exact cost.

Built on:Speech (STT)Summarisation (chat)

Why CloudSitus

What makes it compliant

Whisper-class accuracy

The whisper canonical maps to Microsoft Azure (US, CH, EU) and Scaleway (EU), depending on region.

No cross-border failover

Speech is residency-separate by design; audio never completes in another jurisdiction.

Per-minute billing

Transparent, usage-based pricing with the cost reported on every call — no seats, no subscription.

Subtitle-ready output

srt, vtt and verbose_json drop straight into existing transcription tooling.

In code

A representative call

Transcribe a consult in the EU with timestamps and segments — pinned, PHI-gated, per-minute billed.

Compliance posture

CH transcription → Azure Speech (Switzerland), HIPAA BAA + nFADP/GDPR.
EU transcription → Scaleway (EU), GDPR Art. 28 DPA. Voxtral (Mistral) carries general traffic only.
US transcription → Azure Speech (US), HIPAA BAA.
X-Region: WORLD reaches Deepgram (global, general traffic only) — reach, not residency; X-PHI:true there returns phi_blocked.
Every other named region (UK, ASIA, ANZ, INDIA, LATAM, MENA) returns no_route — residency-pinned transcription is limited to verified jurisdictions.

curl

curl https://cloudsitus.com/api/v1/audio/transcriptions \
  -H "Authorization: Bearer $PHI_API_KEY" \
  -H "X-Region: EU" -H "X-PHI: true" \
  -F file=@dictation.wav \
  -F model=whisper \
  -F response_format=verbose_json

response

x-phi-routed: scaleway-whisper-v3/EU/phi
x-phi-tier: phi
x-phi-cost-micro: 660   # ~3.3 min @ per-minute rate

FAQ

Common questions

Clinical documentation Speech capability Pricing

What if my region’s transcription provider is temporarily down?

The call fails in-region. Speech is residency-separate with no cross-border failover — we will not complete a Swiss transcription on an EU host to paper over an outage. That is a deliberate compliance guarantee.

Is transcription available outside CH, EU and US?

For PHI, no — the residency-pinned, PHI-eligible hosts are in CH, EU and US, and every other named region returns no_route or phi_blocked. For general (non-PHI) traffic you can pin X-Region: WORLD, which reaches Deepgram globally; it carries no residency guarantee and X-PHI:true there is refused.

Ready when you are

Build medical transcription on a gateway that survives the audit.

Prepaid credits from $10, no subscription. The residency and PHI posture is the same on your first call as in production.

Get started See the compliance posture

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