Quick answer up front: repatriation pays off when your load is stable and predictable and you’re paying, month after month, for elasticity you don’t actually need — not because “cloud exit” happens to be trendy right now. And most companies aren’t going all-in either: according to IDC, only 8–9 percent plan to fully repatriate all their workloads; the rest bring back specific pieces, not everything (IDC, 2024).
Right now “cloud repatriation” is the phrase of the moment. First everyone moved into the cloud, now some are moving back out, and in between, consultants make money off both trends. I’ll keep it short: it depends. But not on what people usually argue about.
What the Big Cloud Was Built For
Hyperscalers are brilliant at exactly one thing: load spikes. If your traffic sits at zero today and a million tomorrow, elasticity is worth its weight in gold. You pay a premium for being able to scale up at any moment — and for a moody, unpredictable workload, that premium is worth it.
The problem: most workloads aren’t moody. They’re boring. They run roughly the same, day after day.
And paying a round-the-clock cloud premium for a boring, predictable workload is like renting a Ferrari to drive to the bakery every morning. It works. It’s just a strange way to spend money.
When Going Back Makes Sense
Bring it back — onto your own hardware or rented servers with a European provider — if your situation looks more like the left column. If it looks more like the right one, the cloud is still the more honest choice:
| Going back pays off when … | Staying in the cloud makes sense when … |
|---|---|
| your load is stable and predictable | you’re still experimenting |
| the cloud bill looks about the same month after month (you’re paying for elasticity you’re not using) | your load swings sharply |
| egress fees or lock-in are increasingly getting on your nerves | you simply don’t have the hands to keep operations reliable |
By the way, the worst reason for a repatriation is “on principle.” Just as bad as “move to the cloud because everyone’s doing it now.” Both are trends, not decisions.
Two things make the way back easier today than it was a few years ago: the EU Data Act obliges providers to actively support a switch instead of punishing it with egress fees. And if all you’re missing is the hands to run things, you can get them — selfhosting as a service means someone runs the servers while the control stays with you.
Do the math. Look at what you actually use, not what you’ve provisioned. The answer is usually already sitting in your last invoice — you just have to look.
Want to know whether a repatriation would actually pay off for you? Get in touch — we’ll run the numbers honestly, no trends attached. And if the way back does pay off, I’ll take over hosting & operations too, if you want.