Reversible cloud: the cloud you can take back

A reversible cloud meets three conditions.

• Open-source end to end: no proprietary building block holds you, you can inspect and replay every layer.
• Open standards: Kubernetes for orchestration, S3 for object storage, PostgreSQL for data, the same APIs as everywhere else.
• Real reclaim: you can run the platform on your own servers or another host, without rewriting your applications.

The first two conditions make the third possible. Without open source and open standards, reclaim stays theoretical.

Many providers promise reversibility on paper. The Data Act strengthens that right, with data export within 30 days and capped egress fees. That is necessary, but not enough.

Exporting your data is not enough if the application itself only runs at that provider. You get files back, not a platform that restarts elsewhere. Real reversibility covers the whole: the data, the applications and the infrastructure that runs them. A reversible cloud closes this gap between the right to leave and the ability to leave.

Vendor lock-in has a price, often invisible while everything is fine. Egress fees bill every terabyte that leaves the provider. Proprietary managed services have no equivalent elsewhere, so changing host turns into a rewrite project. And once you depend on them, you take price increases with no negotiating leverage.

Reversibility flips that balance of power. Being able to leave, concretely, is the best argument for staying on good terms, and an insurance of resilience if the provider changes course.

Bunker builds a reversible platform by design. The sovereign cloud runs on managed Kubernetes and open-source managed services (PostgreSQL, S3 object storage, monitoring, CI/CD), with no proprietary layer.

You can bring your platform back onto your own servers, or move it to another compatible host, without rewriting your code. Everything is hosted in Europe, GDPR-compliant and outside the reach of the US CLOUD Act. That is what separates a sovereign cloud from one that is both sovereign and reclaimable. Sovereignty protects your data, reversibility protects your freedom to leave. To put it into practice, follow our cloud repatriation guide.

Reversibility only matters if you can exercise it alone, without the provider's green light. With Bunker, no approval from us is required to take back or move your infrastructure, and there is no switch we keep on our side. You do not have to notify us or wait for us to act.

Leaving comes down to three concrete steps. You recover your data through exports and database dumps. You redeploy the platform wherever you want, on your servers or another host, because it rests on open standards. Then you point your DNS at the new hosting: the IP addresses stay ours, but your domain name stays yours, and switching over is a matter of changing where the DNS points. An infrastructure agent can even replay that redeployment for you. It is the same autonomy you can promise your own clients if you resell Bunker.