Regions & availability
Nine regions on three continents — choose where your data lives and how to stay online when a site fails.
On this page
Regions#
Each region is an independent data center with its own power, cooling and network edge. Resources are created in exactly one region and never move unless you migrate them.
| Code | City | Best for |
|---|---|---|
| MOW1, MOW2 | Moscow | Russia and CIS |
| LED1 | Saint Petersburg | North-west Russia, Baltics |
| IST1 | Istanbul | Türkiye, Balkans, Middle East |
| AYT1 | Antalya | Southern Türkiye, disaster recovery |
| FRA1 | Frankfurt | Western Europe |
| BER1 | Berlin | Germany, Central Europe |
| AMS1 | Amsterdam | Benelux, transatlantic traffic |
Shell
avenlith region list
avenlith server create --name api-01 --plan vps-pro --region fra1 --image ubuntu-26.04
Designing for availability#
A single server is only as available as its host. For production workloads we recommend:
- Run at least two instances behind a load balancer in the same region.
- Keep a warm standby or replicated database in a second region — for example IST1 + AYT1 or MOW1 + LED1.
- Store backups in a different region from the primary data.
Data residency#
Data stays in the region you select. Russian personal data should be stored in MOW1, MOW2 or LED1 to comply with Federal Law 152-FZ.
Was this page helpful?
Still need help?
Our engineers answer tickets 24/7 — average first response in 7 minutes.