Oracle's Quiet Nerf to the Always Free Tier: What You Need to Do Before June 15th

Editors Note: As of June 16th, 2026, the status of this change remains murky. No charges have been officially hitting accounts yet.

For years, home lab enthusiasts, developers, and self-hosters have treated Oracle Cloud Infrastructure (OCI) like a tech cheat code. The "Always Free" tier, which generously served up 4 ARM Ampere CPUs and 24 GB of RAM, was practically unrivaled.

That era has officially come to an end.

Without sending a single notification email to its users, Oracle has updated its official documentation and support channels to reflect a massive resource slash. The new Always Free ARM limit is now 2 OCPUs and 12 GB of RAM.

Even worse? The changes take effect on June 15th, 2026. That gives the community less than 48 hours to fix their stacks before things break.

The Silent Drop and Why It’s Defensible but Distasteful

Let’s be realistic: Oracle has every right to alter the terms of its free services. Running millions of free, beefy ARM instances costs serious money, and a correction wasn’t completely unexpected.

What is genuinely pulling the community's collective hair out is the absolute lack of communication.

As a case in point, the very site you are reading this article on runs on an OCI backend. As of publication, we have received exactly zero official emails, dashboard alerts, or advance warnings regarding this change. To find out that your infrastructure is about to change via Reddit threads and buried documentation updates is an incredibly dark pattern.

Under the hood, the documentation previously calculated the free tier limits at 3,000 OCPU hours and 18,000 GB hours per month. The updated terms cut those numbers dead in half to 1,500 OCPU hours and 9,000 GB hours.

What Happens on June 15th?

According to confirmations from Oracle Support and active community testing, how this hits you depends entirely on your account type:

• Pure Free Tier Users: If your active instances exceed the new 2 CPU / 12 GB RAM threshold, Oracle will simply shut them down without warning.
• Pay-As-You-Go (PAYG) Users: Many users upgraded to PAYG purely to avoid having their inactive accounts randomly reclaimed by Oracle's automated systems. If you have a 4 CPU / 24 GB RAM instance on a PAYG account, your instance will keep running, but you will instantly start seeing charges on your credit card for the excess usage starting June 15th.

If you are running a monolithic setup—like a heavy Jellyfin media server, a Pterodactyl game panel, or multiple Docker environments—you need to log into your OCI dashboard immediately, navigate to your instances, and use the Edit Shape tool to slide those sliders down to 2 OCPUs and 12 GB of RAM.

The Legal and Cultural Fallout

For a company that frequently courts enterprise clients, treating the developer sandbox community with this much opacity is a bad look. In fact, pulling the rug out on resource allocations with a two-day notice and zero direct user communication might cross more than just ethical lines. Legal minds in the community are already pointing out that executing a silent change that automatically triggers financial billing on consumer credit cards without explicit prior notice heavily flouts consumer protection guidelines, particularly under stringent EU law.

Time to Migrate?

If your projects simply cannot survive the resource downgrade, it might be time to pack your bags. While nothing on the market truly matches what Oracle used to offer for zero dollars, there are stable, budget-friendly options that won't surprise you with unannounced billing changes.

If you need a reliable alternative where you actually get what you pay for without dark patterns, providers like Interserver offer highly competitive, predictable pricing on VPS slices that can comfortably pick up the slack of your downgraded OCI instances.

Go check your OCI dashboards. You have until Monday.