Repatriate your cloud. Take back control.
Leaving AWS, Azure or a public cloud means taking back control of your infrastructure on an open-source suite hosted in Europe, run as a managed sovereign cloud or brought fully back in-house.
Cloud repatriation (or re-internalisation) means moving some or all of your workloads off a hyperscaler and back onto infrastructure you control. Gartner expects most large European organisations to have started such a move by the end of the decade, up from a handful in 2025.
The reasons keep recurring: a bill drifting up by around 10% a year, a Cloud Act exposure legal teams no longer sign off on, and dependence on a vendor you cannot leave without rebuilding everything. Bunker is built to make that move practical, without walking straight into the same trap somewhere else.
The signals you should not ignore
Your cloud bill grows faster than your usage
Hyperscaler prices rise by roughly 10% a year, and data egress fees make any attempt to leave more expensive. When cost climbs without value following, the repatriation maths starts to add up.
The Cloud Act blocks your compliance
The US Cloud Act and FISA 702 let US authorities demand access to your data, including when it sits in Europe. For healthcare, the public sector or finance, that legal risk now blocks entire projects.
You cannot leave without rebuilding everything
Proprietary services, closed formats, vendor-specific APIs: the longer you stay, the higher the exit cost. If leaving your provider looks like a multi-month project, lock-in has already done its work.
A contract milestone is coming up
End of commitment, renewal, expiry of the migration credits offered upfront: these moments are the best window to repatriate, before re-signing for three more years of the same dependence.
How repatriation works with Bunker
Audit of the existing setup
We map your workloads, your dependencies on proprietary services and your data volumes. The goal is to identify what repatriates easily, what needs work, and what can stay where it is during the transition.
Target definition
Managed sovereign cloud, on-premise on your own hardware, or hybrid: we pick the right balance based on your sovereignty, cost and team constraints. Because the suite is open source, the target is never dictated by the vendor.
Gradual migration
We move workloads in batches, starting with the least risky, with a transparent network switchover. Europe's strong fixed network keeps latency painless between your sites and the target infrastructure.
Re-internalisation at your own pace
You keep the option to bring everything back in-house later, with no further migration: the code is yours, the formats are open. The sovereign cloud serves as a launchpad towards your own infrastructure.
Why repatriation is no longer a step backwards
For years, leaving the public cloud meant giving up flexibility and cutting yourself off. That is no longer true. Europe has dense, well-connected infrastructure, and a repatriated setup stays fully connected and can burst to a sovereign cloud when load demands it.
Modern repatriation makes on-premise and cloud coexist. You keep sensitive data in-house, pool the rest on European infrastructure, and arbitrate on your own constraints rather than a hyperscaler's.
Promised reversibility vs proven re-internalisation
Most cloud providers now sign portability commitments (the SWIPO code, for instance). Reversibility has become a regulatory box everyone ticks. But a contractual promise that you can leave stays a long way from infrastructure technically designed to be taken back.
With Bunker, portability is built into the technology. The suite is open source, you can run it yourself, and your data lives in standard formats. The day you want to bring everything back in-house, the code is already yours. That is the whole difference between a clause and a property.
Frequently asked questions
What is cloud repatriation?
Cloud repatriation means moving workloads off a public cloud (AWS, Azure, Google Cloud) back onto infrastructure you control: a European sovereign cloud, your own on-premise hardware, or a mix of both. It is also called re-internalisation. The goal is to take back control of cost, sovereignty and vendor dependence.
Does repatriating my cloud cost more than staying on a hyperscaler?
Not over time. Hyperscaler bills rise by around 10% a year and egress fees add up on every exit. The right calculation is total cost over several years, sovereignty and reversibility included. An open-source suite hosted in Europe removes lock-in and makes spending predictable.
Do I have to repatriate everything at once?
No, and it is rarely advisable. Migration happens in batches, starting with the least risky workloads. You can keep some workloads in the public cloud during the transition and move at your own pace. A hybrid approach is often the starting point.
After repatriating to Bunker, am I locked in again?
No, and that is the whole point. The Bunker suite is open source and your data stays in open formats. You can bring the infrastructure fully back in-house whenever you decide, with no further migration and no proprietary format. You replace a dependence with infrastructure you own.
Ready to take back control of your infrastructure?
We audit your existing setup and build your repatriation path, from sovereign cloud to on-premise.