After the strikes on Kyiv data centres in autumn 2026, many companies are asking themselves again: keep systems in a Ukrainian cloud or move them to a European one? There is no universal answer. It depends on what data you hold, who your regulator is, where your users work and how much downtime you can afford.
Below: the criteria to compare by, and the steps to reach a decision.
In short
| Criterion | Cloud in Ukraine | Cloud in the EU |
|---|---|---|
| Physical risks | data centres are being hit — in autumn 2026 several Kyiv sites were put out of action | outside the combat zone |
| Personal data under Ukrainian law | no cross-border transfer needed | transfers to European Economic Area states are allowed |
| GDPR | doesn’t apply merely because of where data is hosted | hosting in the EU alone doesn’t make you subject to the GDPR, but an EU provider is subject to it as a processor |
| Public sector and CII operators | the provider must be on the list of cloud service providers | the same: the list requirement doesn’t depend on where the data centre is |
| Financial institutions (NBU No. 99) | allowed, with requirements on risks, continuity and the contract | allowed on the same terms |
| Latency for users in Ukraine | lower | higher — test it in a pilot |
Resilience after the strikes
What happened to Kyiv data centres is covered in “Strikes on data centres: how to protect your IT”. The main lesson: what matters is not the country’s flag but whether there is a second site. Operators that had standby sites kept working; one of them, Parkovyi, said it deployed client data to standby sites in the EU.
So compare not just “Ukraine or the EU”, but setups:
- main infrastructure in Ukraine, the standby site and copies in the EU;
- main infrastructure in the EU, copies in Ukraine or in another EU country;
- everything in one place — the cheapest, but with no protection against losing the site.
Personal data and the GDPR
- Ukrainian law. Article 29 of the Law “On Personal Data Protection” allows personal data to be transferred abroad if the receiving state ensures adequate protection. The law recognises European Economic Area states as such.
- The GDPR. Using a provider in the EU does not on its own make you subject to the GDPR — this is how the European Data Protection Board (EDPB) explains it. But a provider processing data in the EU is itself subject to the GDPR as a processor, including the rules on transfers outside the EU. Ukraine is not on the list of countries the European Commission has recognised as adequate, so returning data to Ukraine will need a transfer mechanism — for example, standard contractual clauses.
- Your customers in the EU. If you offer goods or services to people in the EU, the GDPR may apply to you regardless of where your servers are — see “GDPR for Ukrainian companies: when it applies”.
A legal opinion on your data should come from a lawyer, not an IT contractor.
Regulated companies
- The public sector and critical information infrastructure operators choose cloud and data centre service providers from the list of providers. The transition period, during which services can be bought from providers not on the list, runs until 31 December 2026 — see “Ukraine’s cloud provider list after 2026”.
- Financial institutions work under NBU Resolution No. 99. It allows public, private and hybrid clouds and an independent choice of provider, but bans providers linked to the aggressor state, as well as processing data on its territory, in temporarily occupied territories and in data centres owned by sanctioned persons. More in “NBU Resolution 99: cloud for banks and fintech”.
Latency, connectivity and cost
- Latency. For users in Ukraine, a Ukrainian data centre is closer. How noticeable the difference with the EU is depends on the application. Those that constantly exchange data with a database are more sensitive: move them together with the database, not separately. Test it in a pilot with real users.
- Connectivity. A site abroad needs reliable links and a backup route. How to connect sites — see “Hybrid cloud: what it is and when you need it”.
- Cost. Compare the full cost, not the price of a virtual machine: traffic, links, licences, backups, support. How to calculate it — see “Cloud costs: how to estimate and not overpay”.
Sovereign clouds
Large providers offer separate clouds for EU data sovereignty requirements. For example, on 14 January 2026 AWS opened the AWS European Sovereign Cloud to all customers. Its first Region is in the state of Brandenburg, Germany. The cloud is physically and logically separate from other AWS Regions and is operated by EU residents. For a Ukrainian company this option makes sense if your customers or partners in the EU require it.
Ukrainian providers with sites in the EU
The choice is not always either-or. Some Ukrainian providers have equipment both in Ukraine and in the EU. For example, GigaCloud says its equipment is hosted in five data centres — three in Ukraine and two in Poland — and in June 2026 the company was added to the list of cloud service providers. With such a provider you can consider a setup with sites in both countries. But check the same things as with any provider: where exactly your data is, how the standby works and how to get your data back.
How to decide
- Classify data and systems. Personal, regulated, business-critical, everything else.
- Check the requirements. The personal data law, your regulator, the provider list, your customers’ requirements.
- Set RTO and RPO for each critical system — see “Disaster recovery: RTO, RPO and a recovery plan”.
- Choose a setup. Ukraine, the EU or both sites — and what runs where.
- Run a pilot. Move a non-critical system and measure latency, cost and recovery time.
Checklist
- Data and systems are classified
- There is a legal opinion on transferring personal data abroad
- Regulator and provider-list requirements are checked, if they apply to you
- RTO and RPO are set for critical systems
- A setup is chosen: where the main site is, where the standby site is and where the copies are
- Latency and cost have been tested in a pilot
- The provider contract covers where data is stored, the standby and data return
How Bereg-IT can help
We have moved our own infrastructure from Ukraine to the EU and helped our clients do the same. Together with you we classify systems, set RTO and RPO and prepare the technical part of the decision for your lawyer. We choose a site — with a European provider, in Microsoft Azure or in AWS — and move all your systems or only the critical ones. We work with European providers; GigaCloud is our partner. More on the IT infrastructure migration to the EU page; the move itself is described in “Moving servers to the EU: when it makes sense”.
The first consultation is free. Send a request and we’ll suggest where to place your systems.
Sources
- Law of Ukraine “On Personal Data Protection” of 01.06.2010 No. 2297-VI, Article 29: https://zakon.rada.gov.ua/laws/show/2297-17
- Regulation (EU) 2016/679 (GDPR), Articles 3 and 28, Chapter V: https://eur-lex.europa.eu/eli/reg/2016/679/oj
- EDPB, Guidelines 3/2018 on the territorial scope of the GDPR (Article 3), version 2.1, adopted 12.11.2019: https://www.edpb.europa.eu/documents/guideline/guidelines-32018-on-the-territorial-scope-of-the-gdpr-article-3-version-adopted_en
- European Commission, Adequacy decisions: https://commission.europa.eu/law/law-topic/data-protection/international-dimension-data-protection/adequacy-decisions_en
- Resolution of the Cabinet of Ministers of Ukraine of 17.12.2025 No. 1691 — transition period for the provider list (in Ukrainian): https://www.kmu.gov.ua/storage/app/uploads/public/694/9a7/aac/6949a7aacc998182705582.pdf
- Resolution of the NBU Board of 25.08.2025 No. 99 (in Ukrainian): https://bank.gov.ua/admin_uploads/law/25082025_99.pdf
- AWS News Blog, Opening the AWS European Sovereign Cloud (14.01.2026): https://aws.amazon.com/blogs/aws/opening-the-aws-european-sovereign-cloud/
- GigaCloud — where its equipment is hosted and its inclusion in the provider list (in Ukrainian): https://gigacloud.ua/
- LB.ua, Parkovyi data centre fully stopped operating after enemy attacks (in Ukrainian, 01.10.2026): https://lb.ua/society/2026/10/01/770394_datatsentr_parkoviy_povnistyu.html