Pilae Cloud regions: 12 locations, six in Switzerland and the EU

Run your apps on dedicated machines in any of 12 Pilae Cloud regions, six of them in Switzerland and the EU, or on your own premises anywhere. The location is chosen with you and written into your contract.

Start with one workloadBook a 30-minute briefing

Switzerland
Zurich
European Union
Frankfurt, Falkenstein, Gravelines, Amsterdam, Helsinki
Worldwide
London, Ashburn, Hillsboro, Singapore, Tokyo, Sydney
On premises
Your datacentre, in any country
Datacentres
ISO 27001-certified, in every region

A location you choose and can name

Where a machine sits decides which law reaches it, how far a request travels and what you can tell a client or regulator. Pilae gives each deployment a named location, for the apps and for the backups.

Zurich, Switzerland

The default for data that must stay in Switzerland: public administrations, banks, insurers, health and legal work under Swiss rules.

Five EU regions

Frankfurt, Falkenstein, Gravelines, Amsterdam and Helsinki, for EU residency under the GDPR.

Six worldwide regions

London, Ashburn, Hillsboro, Singapore, Tokyo and Sydney, for teams and users outside Switzerland and the EU.

Your premises, anywhere

Your datacentre, your server room or an air-gapped site, in whatever country you operate. Pilae runs the same platform there.

Backups in the same jurisdiction

Daily encrypted backups go offsite to a second site in the same jurisdiction as the region you chose, with a restore test every month.

One private network across regions

Machines in different regions join one private mesh, so a multi-region estate stays private end to end.

Why the location matters

A region is not only a latency figure. It decides which courts and authorities can reach the machine, what you can promise your own clients and what a regulator will accept. Our jurisdiction page explains how Swiss and EU law apply, and our data residency page sets out what stays where.

The 12 regions

Region Code Country Jurisdiction
Zurich zur1 Switzerland Switzerland
Frankfurt fra1 Germany European Union
Falkenstein fal1 Germany European Union
Gravelines gra1 France European Union
Amsterdam ams1 Netherlands European Union
Helsinki hel1 Finland European Union
London lon1 United Kingdom Worldwide
Ashburn ash1 United States Worldwide
Hillsboro hil1 United States Worldwide
Singapore sin1 Singapore Worldwide
Tokyo tok1 Japan Worldwide
Sydney syd1 Australia Worldwide
Your premises – Any Your own

You choose the region. Your data, backups and logs stay in it, backups go to a second site in the same jurisdiction, and the contract names the region. New locations can be provisioned on request.

Switzerland and the EU first, the world when you need it

Zurich is the default for data under the Swiss nLPD and sector rules such as those described on our FINMA page. The five EU regions suit organisations bound by the GDPR that want EU residency. The six worldwide regions serve teams and users elsewhere. Pilae SA is a Swiss company with no US parent, but a workload placed in a US region is stored in the US and subject to US law on data held there. When no datacentre outside your walls will do, Pilae runs the same platform on your premises, including air-gapped sites.

One estate across several locations

An estate can span more than one location: sensitive apps on premises, the rest in Zurich, a copy of a service in Frankfurt for EU colleagues or in Singapore for a team in Asia. A hybrid deployment keeps them in one console, on one private network, under one contract. Every hosting provider is listed in the data processing agreement. To choose your locations, book a scoping call.

How your location is chosen

  1. State the rules

    You tell us what applies: Swiss residency, EU residency, a client requirement, a sector rule or a latency need.

  2. Match a region

    We propose a region for each app and for its backups, and explain the provider, the datacentre and the reasoning.

  3. Write it down

    The region and datacentre for every machine and backup target go into your contract and data processing agreement.

  4. Provision

    Dedicated machines are set up in that location, hardened and joined to your private mesh.

  5. Keep it there

    Your data does not move to another location without your written approval. The console shows where each app runs.

What your contract includes

Machine location
The country and datacentre for each machine, named per app.
Backup location
The country and datacentre for your offsite backups, at a second site in the same jurisdiction.
No silent moves
Data moves to another location only with your written approval.
Datacentres
ISO 27001-certified in every region, with notice before any change of hosting provider.
Governing law
Swiss law, with Pilae SA in Lausanne as your contracting party, whatever region you choose.

The apps behind it

Questions

Which regions does Pilae Cloud offer?

Twelve: Zurich in Switzerland; Frankfurt, Falkenstein, Gravelines, Amsterdam and Helsinki in the EU; and London, Ashburn, Hillsboro, Singapore, Tokyo and Sydney worldwide. New locations can be provisioned on request. On premises, Pilae operates your apps in your own datacentre in any country.

What standard do the datacentres meet?

Every Pilae Cloud region runs in ISO 27001-certified datacentres. Your contract names the region for each machine and backup, and we give notice before any change of hosting provider.

Can different apps run in different regions?

Yes. Each app has its own location in the contract. A private network joins the regions, so apps in Zurich and Frankfurt reach each other without a public address.

Are backups kept in the same jurisdiction as the app?

Yes. Backups are daily, encrypted and stored offsite at a second site in the same jurisdiction as the region you chose. Restore tests run every month and are recorded in the console.

Can we change region after signing?

Yes. A region change is planned with you, approved in writing, and carried out in your window with a verified backup taken first. The contract is updated to name the new location.

Related

Pick the right region for each app.

Thirty minutes with an engineer to match your residency rules to a location and put it in writing.