Oracle's Always-Free Tier: The Server Everyone Forgets

Every guide to standing up your first server starts in the same place: pick a droplet, enter a card, pay five dollars a month, scale up when you outgrow it. That's fine advice, and for a solo builder pre-revenue it's also five dollars a month you didn't need to spend. Because there's a machine sitting one signup away that costs nothing and never stops being free — and almost nobody claims it, because the signup quietly rejects a large fraction of the people who try.

Oracle's Always Free tier is the most under-used piece of infrastructure available to an early-stage founder. Not a 12-month trial that flips to billing on month 13. A permanent grant, alive for as long as your account is alive. The spec is genuinely absurd for the price, and the price is zero.

What you actually get

The headline resource is an ARM server built on Ampere A1 cores. Oracle meters it by the hour — 3,000 OCPU-hours and 18,000 GB-hours per month — which sounds abstract until you do the division: it's exactly enough to run one always-on machine with 4 cores and 24GB of RAM, around the clock, forever. Add 200GB of block storage and 10TB of monthly outbound traffic, and you have a development box that most people would assume costs real money.

It does cost real money — somewhere else. Here's the same configuration priced on the majors:

You also get two small AMD x86 instances (about 1 core and 1GB each) as backups — handy for a bastion host or a tiny always-on cron runner that you don't want competing with your main box.

For a solo AI-native founder, this is the difference between "I'll spin up a server when I have something worth hosting" and "I already have a server, so what am I going to put on it." The second mindset ships more.

A permanent 4-core, 24GB box changes the question from can I afford a server to what am I going to run on the one I already have.

Why the signup rejects you

Here's the catch nobody warns you about, and the reason most people conclude the free tier is "not available in my country" and give up. Oracle runs an aggressive, undocumented fraud check at signup, and it fails silently. You fill in the form, enter a card, and get a vague error or an account that's flagged for review and never activates.

The community consensus — Oracle has never published this — is that the risk engine cross-checks three things and expects them to agree: the country your IP resolves to, the country that issued your card, and the billing address on that card. Call it the risk-control trinity. When those three tell a consistent story, you sail through. When they contradict each other — a VPN exit in one country, a card from another, an address from a third — you look exactly like the fraud patterns Oracle is screening out.

The practical implications are unglamorous but decisive:

• Turn off every VPN and proxy before you start. This is the single most common cause of rejection. Your IP needs to match your card's country.
• Use a mobile hotspot, not home WiFi. Residential and datacenter IP ranges sometimes get treated differently; a phone on 4G/5G presents as a clean consumer connection. Not strictly required, but it removes a variable when you're debugging a rejection.
• Use a real physical card carrying a Visa or Mastercard logo. Oracle places a roughly $1 pre-authorization to verify it — this is a hold, not a charge, and it reverses automatically. Virtual and prepaid cards are frequently declined.
• Make the billing address match the card's issuing country. Consistency is the whole game.

And the rule that saves you the most grief: if a card fails twice, stop. Trying the same card a third and fourth time doesn't wear down the risk engine — it hardens the flag against you. Switch to a different card or wait two to three days before trying again. If you're a founder who's just gone through the work of getting a US bank card without setting foot in America, make sure that card's billing country lines up with where you're signing up from before you burn an attempt on it.

The one choice you can't take back

Everything else in Oracle Cloud is reconfigurable. This one isn't: your Home Region, chosen once during signup, is permanent. You cannot move it later, and it silently determines something that matters enormously — whether you'll actually be able to create an ARM instance at all.

The Ampere A1 capacity is shared and contended. In popular regions, everyone wants the same free 4-core box, and Oracle simply runs out. So the region you pick isn't about latency the way it would be for a game server — it's about which queue you'll be standing in for the rest of your account's life.

The community-tested guidance:

• Phoenix (US West) — the safe default. Reliable ARM availability. Unless you have a hard latency requirement, pick this and move on.
• Mumbai, Jakarta — solid backups if you want to be geographically closer and Phoenix isn't ideal for you.
• Tokyo, Seoul, Singapore — avoid unless you must. ARM capacity in these is chronically contested; you may wait days or never get an instance.

A server isn't a game — a few dozen milliseconds of latency to your dev box is irrelevant. Reliably obtaining the machine beats shaving latency you'll never notice. Optimize for getting the hardware, not for pinging it fast. If you later need edge presence close to users, that's a job for a CDN or global edge compute, not for where your origin server happens to sit.

Getting through the flow

The signup itself is mechanical once the trinity lines up: go to oracle.com/cloud/free, enter your details in Latin characters, verify your email, set a password, and choose Individual as the account type. When the Home Region dropdown appears, select US West (Phoenix). Enter the billing address that matches your card, verify your phone, and add the card for its ~$1 hold. Thirty to sixty seconds later you land on a welcome page — that's success.

Then create the instance: Compute → Instances → Create Instance. Choose an Ubuntu 22.04 image marked "Always Free Eligible," pick the VM.Standard.A1.Flex shape and dial it to 4 cores and 24GB, set the boot volume to 200GB, and paste in an SSH public key (generate one locally with ssh-keygen first). See Oracle's own Always Free resources reference for the current eligibility labels, which occasionally shift.

When you hit "Out of Capacity"

You will probably see this at least once, and it is not a mistake on your end. "Out of Capacity" means the region's free ARM pool is momentarily exhausted — other people are grabbing the same boxes faster than Oracle releases them. Manually clicking "Create" over and over is a low-percentage game; capacity frees up in unpredictable seconds-long windows you'll almost never catch by hand.

The community solved this with automation. Two well-known open-source approaches let you set your instance parameters once and then poll for capacity every few dozen seconds, creating the instance the instant a slot opens:

# GitHub Actions approach — runs the retry loop in CI, no local machine needed
# github.com/maoucodes/oci-free-arm-instance

# Python approach — runs locally or on a tiny always-on box
# github.com/mohankumarpaluru/oracle-freetier-instance-creation

Configure it, walk away, and check back later. Success typically lands somewhere between a few hours and a few days. This is the correct amount of effort — set up a retry loop, not a vigil.

The reason this is worth the hassle is simple: you do it once. After the machine exists, it's yours indefinitely. A permanent 4-core, 24GB server for the cost of a careful signup and a little patience is one of the best deals in cloud infrastructure that almost nobody takes. The only thing standing between you and it is a fraud check you now know how to pass and a region choice you now know how to make — so make the region Phoenix, kill the VPN, and go claim the machine everyone forgets.

---

Part of the Vibe-entrepreneurs series on solo builder infrastructure. Next: Keeping Your Free Oracle VPS From Getting Reclaimed. See also Ship a Static Site With Nothing But git push and Deploy Global Infrastructure for Free on Cloudflare. More builder insights.