Your Infrastructure Should Not Need Permission

You deployed a workload on a free tier. The vendor changed their policy. Your workload disappeared.

This is not a failure of planning. It is a failure of ownership.

Infrastructure you do not control is not infrastructure. It is a dependency with an expiration date you cannot read. The vendor decides when the terms change. You decide whether to comply or migrate.

The alternative is not to avoid cloud entirely. It is to build so that migration is a decision, not a crisis.

Principles that protect you:

• If it cannot run on two providers, it is locked in.
• If the data cannot be exported in a standard format, it is hostage.
• If the deployment requires a proprietary tool, the tool owns your workflow.
• If the free tier is the only reason it works financially, the business model is the vendor's, not yours.

Sovereignty is not about rejecting services. It is about retaining the ability to leave.

The question is not whether you use cloud. The question is whether the cloud uses you.

References

• Nrupala. (2026). Oracle Cloud OCI account closure correspondence. Personal communication regarding ARM capacity unavailability in Montreal region.
• Cloud Native Computing Foundation. (2023). "Cloud Native Definition." https://www.cncf.io/about/who-we-are/
• Stallman, R. (2010). "Who Does That Server Really Serve?" GNU Project. https://www.gnu.org/philosophy/who-does-that-server-really-serve.html

devinfo.dev. (2026). "Your Infrastructure Should Not Need Permission." devinfo.dev:2026.0005. https://devinfo.dev/d/2026.0005