Short answer. No Plugsky region is live in Switzerland. The nearest live region is eu-central-1 in Frankfurt, so Swiss personal data would be disclosed to the EU rather than kept in-country. Private VPC, on-premises and air-gapped deployments are contract-only. Plugsky does not claim a Swiss data centre, office, FINMA approval or residency guarantee.
2027 planning guide — evidence checked 20 November 2026.
Availability at a glance
Switzerland is a cross-border market for Plugsky, and the page should say so before a buyer spends time on an architecture. The table separates the nearest live region from the contract-only routes.
| Option | What is available | Status | Buyer note |
|---|---|---|---|
| Live region in Switzerland | None | not claimed | No Swiss region is live. |
| Nearest region | eu-central-1, Frankfurt | nearest | Closest live region; a disclosure from Switzerland to the EU. |
| Private VPC | Dedicated endpoint in a live region; location agreed in writing | contract | Scope, network boundary and price are agreed in writing. |
| On-premises | Plugsky runtime in your facility | contract | Hardware, updates and support are part of the order. |
| Air-gapped | No outbound connectivity | contract | Update and support paths are designed into the contract. |
| Swiss residency guarantee | Only what the DPA and order form state | contract | Frankfurt is not a Swiss location; no blanket guarantee is made. |
| Swiss office or data centre | None claimed | not claimed | No office, subsidiary or owned facility in Switzerland is claimed. |
Status key. live means production traffic today; nearest means the closest live region, not a local presence; contract means a signed order; not claimed means no claim is made. No local row is marked live because no local region is live.
What Frankfurt means for a Swiss data transfer
Private AI means running inference under a contract that fixes the processing location, access and deletion terms. It is not a synonym for a local data centre.
Frankfurt is inside the EU, not inside Switzerland. A Swiss controller that sends personal data to an API endpoint there is making a disclosure abroad under the FADP, even though the distance is short and the legal systems are close. The transfer needs a lawful basis, a processor agreement and appropriate safeguards.
The EU lists Switzerland as adequate, and Swiss law maintains its own list of states with adequate protection, where the EU is treated as adequate subject to the current annex. That helps, but it does not remove the documentation duty. Ask for the DPA, the subprocessor list and a Swiss addendum if your counsel wants one. The data residency guide sets out the difference between a processing location and a legal guarantee.
None of this makes Plugsky a Swiss provider. No Swiss entity or facility is claimed, and no Swiss-based support is promised. The honest reading is that Frankfurt is a near, EU-based option for Swiss workloads that can accept an EU processing location, and that on-premises or air-gapped deployment is the route for workloads that cannot.
Swiss framework: FADP, FDPIC and FINMA
This is a buyer's map, not legal advice. Verify with counsel before relying on it.
FADP and the FDPIC
The revised Federal Act on Data Protection has applied since 1 September 2023. It sets rules for lawful processing, transparency, data security and disclosure abroad. The Federal Data Protection and Information Commissioner publishes guidance and supervises federal bodies; cantonal authorities handle much of the private-sector supervision. The FDPIC does not certify vendors or issue AI approvals.
For an API buyer the practical questions are the same as elsewhere, with a Swiss accent: what personal data is in the prompt, where is it processed, who can access it, how long is it kept and what happens on deletion. A vendor questionnaire and a signed DPA answer those questions; a badge does not.
FINMA, only where it applies
If you are a FINMA-supervised bank, insurer or financial institution, outsourcing and AI governance expectations apply. FINMA Circular 2018/3 covers outsourcing, including audit access, sub-outsourcing and exit arrangements. FINMA Guidance 08/2024 sets out governance and risk-management expectations for AI use.
Plugsky does not claim FINMA approval, a Swiss banking reference or a pre-approved outsourcing package. A regulated buyer should bring the circular and the guidance into the vendor review, then ask for the contract terms that satisfy them. That is a counsel-led exercise, not a product toggle.
No single Swiss AI statute
Switzerland has relied on sector-specific rules and data protection law rather than one comprehensive AI statute. That may change, and the federal position has been under review. Confirm the current status with counsel before you write a compliance representation into a contract.
A procurement path for Swiss buyers
Swiss enterprise reviews tend to be compact but evidence-heavy. A sequence that works:
- Map the data flow. Identify whether personal data leaves Switzerland and which entity is the controller.
- Request the DPA, subprocessor list and transfer terms. Ask directly whether a Swiss addendum is available.
- Decide whether Frankfurt is acceptable. If not, move to private VPC, on-premises or air-gapped, all contract-only.
- For regulated financial buyers, map FINMA Circular 2018/3 and Guidance 08/2024 onto the contract and the operating model.
- Run a pilot and measure latency from your own network. Do not rely on a vendor page for p95.
The security procurement guide lists the documents to request. Pricing for self-serve plans is on the pricing page; private deployment is quoted because scope drives cost.
Where the Swiss demand is
Three cities dominate the conversations, for different reasons. No Plugsky office is claimed in any of them.
Zurich: banking, insurance and asset management
Zurich is the centre of Swiss banking, insurance and asset management, with a dense fintech and cloud-supplier ecosystem around them. Buyers here start with outsourcing rules, not model benchmarks, and they will ask for audit access, subprocessor names and an exit plan before a pilot. Frankfurt is a short hop, but the transfer analysis still has to be written down. The next step is a joint review with legal, procurement and the model owner, using the FINMA circular as the agenda.
Geneva: wealth, commodities and international organisations
Geneva mixes private banking, commodity trading, international organisations and a growing data-and-AI services sector. Procurement is often international, with headquarters, counsel and data subjects in different jurisdictions. That makes the transfer map more important than the latency map, because the buyer, the data subjects and the support team may sit in three different countries. A useful next step is a written architecture review that names every jurisdiction in the flow, then tests whether Frankfurt is acceptable or whether a private deployment is the only workable route.
Basel: life sciences, chemicals and logistics
Basel is a life-sciences and chemicals cluster with logistics and a strong cross-border labour market. Document-heavy work is common: regulatory files, trial documentation, supplier contracts and quality records. Buyers often ask for validation evidence that Plugsky does not publish, so establish early what is actually required and what the contract can support. A pilot can be scoped to a single regulatory document type. Start there, keep personal data out of the pilot where possible, and measure quality and latency before expanding.
Local search phrases to validate
These are research candidates for Swiss German and Swiss French demand, not approved copy. No volume or ranking is claimed.
| Phrase | English gloss | Likely intent |
|---|---|---|
| private KI Schweiz | private AI Switzerland | Commercial research |
| LLM hosting Schweiz | LLM hosting Switzerland | Local vendor search |
| DSG-konforme KI API | FADP-compliant AI API | Compliance-led |
| FINMA KI Governance | FINMA AI governance | Regulated financial buyer |
| Datenresidenz Schweiz | Swiss data residency | Residency-led |
| IA privée Suisse | private AI Switzerland | Commercial research |
| hébergement LLM Suisse | LLM hosting Switzerland | Local vendor search |
| nLPD et IA | FADP and AI | Compliance-led |
Validate with a native reviewer; not published as localized copy.
What we did not verify
- No Swiss customer, reference or case study is claimed.
- No Swiss office, subsidiary or facility is claimed in Zurich, Geneva or Basel; local staffing is not confirmed.
- No Swiss region is live, and no Swiss data centre is claimed. Frankfurt is in the EU.
- No FINMA approval, ISO 27001 certification or SOC 2 attestation. SOC 2 is described as readiness or in progress.
- No confirmation that the DPA includes a Swiss addendum. Ask for the current terms.
- No measured latency from Swiss networks and no benchmark against other providers.
- No validated search volume or native review for the phrases above.
Frequently asked questions
Is there a Plugsky region in Switzerland?
No. No Plugsky region is live in Switzerland. The nearest live region is eu-central-1 in Frankfurt, and private VPC, on-premises and air-gapped deployments are contract-only.
Does using Frankfurt comply with the Swiss FADP?
It can, but sending personal data to Frankfurt is a disclosure abroad under the FADP. The transfer needs a lawful basis and appropriate safeguards. Plugsky offers GDPR Article 28 terms and EU standard contractual clauses; ask whether a Swiss addendum is included. Counsel must confirm your position.
Can Plugsky serve FINMA-regulated banks and insurers?
It can be assessed, but FINMA Circular 2018/3 on outsourcing and Guidance 08/2024 on AI governance set expectations for supervised institutions. No FINMA approval or certification is claimed. The contract needs audit rights, sub-outsourcing terms and an exit plan.
Is there a Swiss data centre or office?
No. Plugsky does not claim a Swiss data centre, office or subsidiary. The Frankfurt region is the nearest live option, and it is in the EU.
Which deployments are contract-only?
Private VPC, on-premises and air-gapped deployments are contract-only. They are scoped, priced and supported under a signed agreement, not through the self-serve checkout.
Does Plugsky guarantee Swiss data residency?
No blanket guarantee is made. Residency is only what the signed DPA and order form state. Frankfurt processing is an EU location, not a Swiss one, and support or subprocessors can involve other countries.
How should we test latency from Switzerland?
Run a pilot from your Zurich, Geneva or Basel network and measure p50 and p95 for your own prompts. No Swiss latency benchmark is published, and this page makes no millisecond claim.
Sources
Last checked 20 November 2026.
- Federal Act on Data Protection, Fedlex — checked 20 November 2026.
- Federal Data Protection and Information Commissioner — checked 20 November 2026.
- FINMA circulars, including Circular 2018/3 on outsourcing — checked 20 November 2026.
- FINMA Guidance 08/2024 on AI governance — checked 20 November 2026.
- European Commission adequacy decisions — checked 20 November 2026.
For the wider product picture, see sovereign AI. For isolation options, read the private VPC and air-gapped pages.
Put the Swiss transfer question in writing
Start with the data flow, the DPA and the deployment route. Then test the model.
Request architecture review