Swiss RAG and US cloud RAG differ in exactly one thing that cannot be configured away: who has legal control over your documents. Both retrieve passages from your corpus and generate cited answers. Only one of them keeps the entire data path — questions, documents, embeddings, backups and logs — outside the reach of foreign legal process. Everything else in this comparison follows from that.
The side-by-side
| US cloud RAG | Swiss RAG | |
|---|---|---|
| Legal control | US-incorporated provider; CLOUD Act applies to data it controls, wherever stored | Swiss provider under Swiss law only |
| Where inference runs | Usually a US model API, even when storage is regional | Swiss AI cloud, inside Switzerland |
| Embeddings | Frequently a separate US API — often overlooked in the transfer analysis | Same Swiss data path as everything else |
| Backups & logs | Region and retention often unspecified in the contract | Same Swiss bucket, contractual retention |
| Encryption | Provider-managed keys; provider can technically read content | Per-tenant AES-256-GCM applied before storage; operator-blind |
| nFADP / nDSG position | Cross-border disclosure requiring safeguards | No cross-border disclosure to assess |
| Sub-processor chain | Long, changes without notice | Short, Swiss, enumerable |
“Swiss region” is not Swiss control
The most common misunderstanding in Swiss AI procurement is treating a datacenter location as a jurisdiction. Under the US CLOUD Act, a US-incorporated company can be ordered to produce data it controls, regardless of which country the disk sits in. A Zurich region operated by a US hyperscaler therefore does not remove US legal exposure — it only moves the hardware. Sovereignty requires Swiss infrastructure and a Swiss-controlled operator at every step, which is precisely what a Swiss RAG platform is defined by.
Three things buyers usually miss
- Embeddings are personal data too. An embedding is a lossy but far from anonymous representation of the source text; published inversion research reconstructs substantial parts of the original from vectors alone. Sending embeddings abroad is a disclosure, not a technicality.
- Prompts and logs leak the corpus. Retrieved passages travel inside the prompt. If the model API is foreign, the sensitive text crosses the border on every single query, even when the document archive never does.
- The sub-processor chain moves. Reranking, OCR, translation and evaluation services are frequently bolted on later. Each addition is a new transfer to assess — unless the whole path is contractually confined to one jurisdiction from the start.
What you do not give up
The honest part of this comparison: a Swiss RAG platform is not a downgrade in capability. Open-weight models served from Swiss datacenters now handle enterprise document work — extraction, comparison, synthesis, multilingual retrieval — at the quality level these tasks require, and retrieval quality is dominated by the retrieval architecture, not by which frontier model sits at the end of it. A well-built GraphRAG pipeline with agentic reasoning on Swiss infrastructure beats a single-pass vector search on a US frontier model for the questions enterprises actually ask.
What you do trade is access to the newest closed frontier model within days of its release, and the very lowest per-token price. For a regulated corpus, that is usually the cheaper trade.
When US cloud RAG is the right answer
It genuinely is, for public marketing material, open documentation, published research and anything you would put on your website anyway. Sovereignty is a property you pay for where it matters; applying it to a public FAQ corpus is waste. The decision rule is simple: if a disclosure of this corpus to a foreign authority would be a legal or commercial incident, the data path must stay Swiss.
How to verify a claim of Swiss RAG
Ask for the four locations in writing — inference, embeddings, storage, backups — plus the incorporation country of every sub-processor and whether the operator can technically decrypt customer content. Vendors who cannot produce that list in one page are describing a hosting choice, not sovereignty. Our Swiss RAG evaluation checklist turns this into twelve questions you can send verbatim.