Skip to content
CloudSitus

Alternatives

CloudSitus vs AWS Bedrock — picking your jurisdiction.

Bedrock ships a mature, hyperscaler-grade BAA under the AWS umbrella. CloudSitus ships an OpenAI-compatible API with per-request residency and a Swiss/EU-resident PHI tier (with HIPAA BAA coverage available via its Azure routes). The decision is rarely either/or — here is the honest framing.

Get an API keyRead the docs

At a glance

Side-by-side, on the dimensions a security review asks about.

Bedrock is the AWS-managed model marketplace; CloudSitus is a stateless gateway. The rows below compare what each one actually ships today — not what either roadmap might bring.

  • Drop-in OpenAI API shape

    AWS Bedrock
    No:Bedrock has its own SDK and request shape. OpenAI clients do not work as-is.
    CloudSitus
    Yes:Yes — swap base_url to https://cloudsitus.com/api/v1 and the OpenAI SDK works.

  • HIPAA BAA program

    AWS Bedrock
    Yes:BAA covered under the standard AWS BAA at the account level.
    CloudSitus
    Partly:HIPAA BAA coverage via Azure routes — in the US, OCR, speech-to-text and text-to-speech only; US chat, vision and embeddings PHI are not available. Infomaniak & Scaleway PHI routes are nFADP/GDPR (DPA), not HIPAA.

  • Data residency model

    AWS Bedrock
    Partly:AWS Region-scoped: chosen per account/endpoint. Not per request.
    CloudSitus
    Yes:X-Region header pins each request to a jurisdiction at the edge.

  • PHI vs general gate per call

    AWS Bedrock
    No:Not enforced per request. You set the boundary in your own code.
    CloudSitus
    Yes:X-PHI: true filters to PHI-eligible routes; refused (403) if none.

  • Audit headers on every response

    AWS Bedrock
    No:CloudTrail at the account level; nothing on the response itself.
    CloudSitus
    Yes:x-phi-tier, x-phi-routed, x-phi-attempts on every call.

  • Where the proxy sits

    AWS Bedrock
    Partly:AWS-operated, US-headquartered. CLOUD Act applies.
    CloudSitus
    Yes:PHI pins to region-resident providers (CH: Infomaniak/Azure; EU: Scaleway/Azure; US: Azure). Swiss/EU data law.

  • Sub-processor transparency

    AWS Bedrock
    Partly:Per-model terms inside the AWS BAA umbrella.
    CloudSitus
    Yes:Named PHI sub-processors per region (Infomaniak, Scaleway, Azure) under reviewed DPAs / BAA.

  • Pricing model

    AWS Bedrock
    Yes:Per-model token pricing plus AWS account billing.
    CloudSitus
    Yes:Per-model token pricing from prepaid credits. No subscription, no seats.

  • Procurement on-ramp

    AWS Bedrock
    Partly:Requires an AWS account, IAM, and BAA acceptance.
    CloudSitus
    Yes:Self-serve key in minutes. Stripe billing, no account negotiation.

Fair caveat: AWS Bedrock covers HIPAA broadly at the account level under the standard AWS BAA, across its full model lineup. CloudSitus's HIPAA coverage is narrower — it rides the Azure routes for specific modalities. CloudSitus's edge is per-request residency and a Swiss/EU-resident PHI tier — useful when AWS's jurisdictional surface is the constraint, not when it is acceptable.

When to pick each

Jurisdiction first — model second.

The choice between Bedrock and CloudSitus is mostly about where you need the data to sit and under whose law. Models, pricing, and SDK ergonomics are secondary — both stacks can carry the workload.

  • Pick AWS Bedrock when…

    • You are already on AWS, have an account-level BAA, and want everything under one bill.
    • A US-region-scoped BAA satisfies your data residency and procurement constraints.
    • You can absorb the Bedrock SDK (or its OpenAI-compat adapter) into your stack.

  • Pick CloudSitus when…

    • You need data resident outside the US (Switzerland, EU) under nFADP/GDPR DPAs, not under the AWS BAA umbrella.
    • Per-request residency matters — the same key serves CH, EU, and US traffic without account juggling.
    • You want a single drop-in OpenAI base URL across providers and a hard PHI vs general gate per call.

  • Hybrid pattern

    • Route US-resident PHI to Bedrock under your AWS BAA — that posture is mature and well-understood.
    • Route CH or EU-resident PHI to CloudSitus (X-PHI: true) — it pins to a region-resident PHI-eligible provider.
    • Use CloudSitus's OpenAI shape as the unified client surface; the router picks the right backend.
    See the routing contract

FAQ

Questions a procurement team will ask.

Is CloudSitus HIPAA-compliant today?
Partly, and only via specific routes. HIPAA BAA coverage exists for CloudSitus PHI traffic that runs on Azure (Swiss North, EU, or US Azure regions) for the modalities hosted there — OCR, speech-to-text and text-to-speech; in the US those are the only PHI modalities, and US chat, vision and embeddings PHI are not available. The Infomaniak (CH) and Scaleway (EU) PHI routes are not HIPAA — they handle health data under Swiss nFADP and GDPR via reviewed DPAs, and those providers make no HIPAA representation. So CloudSitus is not a blanket "HIPAA-compliant gateway"; it is a Swiss/EU nFADP+GDPR-resident gateway with HIPAA-BAA coverage available on the Azure routes. In all cases the router refuses (403 phi_blocked) rather than spill PHI to a non-eligible provider. AWS, by contrast, covers Bedrock broadly under its standard account-level BAA.
Why pick a Swiss/EU-resident gateway over the AWS BAA?
The AWS BAA is excellent for US-resident PHI. It is not the right answer when your regulator wants data resident outside the US, or when the CLOUD Act creates an unacceptable disclosure surface. CloudSitus pins PHI to region-resident providers under Swiss/EU data law (nFADP + GDPR) — a different jurisdictional posture, not a better-or-worse one. Where HIPAA specifically is required, CloudSitus carries that on its Azure routes.
Is Bedrock OpenAI-compatible?
Not by default. Bedrock exposes its own InvokeModel / Converse APIs and uses its own SDK. OpenAI clients require an adapter layer to translate. CloudSitus, in contrast, is OpenAI-compatible by design — your existing SDK works after a base_url swap.
Can I use AWS Bedrock and CloudSitus together?
Yes. A workable pattern is Bedrock for US-resident PHI under the AWS BAA, plus CloudSitus for CH or EU-resident traffic where Swiss/EU-law sub-processing is required. Both can sit behind one application-level router; CloudSitus's OpenAI shape often becomes the unified client surface.
How does per-request residency differ from picking an AWS Region?
In Bedrock you pick a Region per account or per endpoint. To serve EU and US traffic under different residencies you provision separately. With CloudSitus the X-Region header is set per request, the router pins on every call, and a wrongly tagged request fails closed instead of silently crossing a border.

Next step

Read the posture before you file the questionnaire.

The compliance page lists what is earned, what is in progress, and where the sub-processor sits. The signup page gives you a key you can paste into the OpenAI SDK in under a minute.

See the live postureGet an API key

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