What if you could run a small database, a couple of virtual machines, and a chunk of storage without paying a monthly bill? That is the promise behind the Oracle Cloud Infrastructure free tier, and it is one of the more generous permanent free offerings among major cloud providers. The catch is that the details matter, the limits shift over time, and a lot of people sign up expecting one thing and get another.
This guide walks through how the free tier is structured, what the Always Free resources typically include, where people trip up, and how to decide whether it fits a real project or just a weekend experiment.
Two Different Things Called “Free”
The first thing to understand is that OCI splits its free offering into two parts, and they behave very differently.
The Always Free tier is a set of resources that do not expire. You keep them for as long as your account stays in good standing. The Free Trial is a separate, time-limited pool of credits that lets you try paid services for a short window, commonly described as 30 days. When the trial ends, anything outside the Always Free limits starts costing money.
That distinction sounds obvious, but it is the single most common source of surprise. People spin up a powerful shape during the trial, forget it is not part of Always Free, and get a bill when the credits run out. If you are new to how cloud regions and service availability are announced, it helps to read up on how to read a cloud region announcement before you commit, because free tier resources are tied to your account’s home region. (Cloud computing)
What Always Free Typically Includes
Oracle has revised these limits more than once, so treat every number here as a starting point rather than gospel. Check the live documentation on the day you sign up.
| Resource | Commonly offered Always Free allowance |
|---|---|
| AMD compute | Two small VM instances (VM.Standard.E2.1.Micro class) |
| Arm compute (Ampere A1) | Up to 4 OCPUs and 24 GB of memory in total, subject to capacity |
| Block storage | Around 200 GB total, with boot volumes counting toward it |
| Object and archive storage | A modest allowance of each |
| Autonomous Database | Two instances with limited OCPU and storage |
The Arm allowance is the main draw. Four OCPUs and 24 GB of RAM can run a real workload instead of only a toy example. The AMD micro instances are much smaller, suitable for a lightweight web server or a jump box and little else.
The database allowance matters too. Two small Autonomous Database instances give you a managed relational database without a bill, which is unusual in the free tier world. If you want to understand how the compute layer underneath all this fits together, the broader picture of AI chips and computing infrastructure is a useful companion read, since Arm-based instances now sit alongside GPU and other accelerators in most cloud catalogs.
The Capacity Problem Nobody Warns You About
Here is where reality intrudes. The Arm allowance is generous on paper, but it is not guaranteed in every region or availability domain. Users routinely report “out of capacity” errors when trying to launch an Ampere A1 instance, sometimes for days or weeks.
This is not a bug. Free tier capacity is opportunistic. Oracle fills it when paid demand leaves room. A few practical approaches actually work:
- Try multiple availability domains within your region rather than repeatedly hammering the same one.
- Attempt launches at quieter hours, since capacity frees up unpredictably.
- Start with a smaller Arm shape and resize later if the full allowance will not provision.
- Keep the AMD micro instances as a fallback so your project is not blocked entirely.
What does not work is assuming a specific region will always have room. Anyone planning production-adjacent workloads on free Arm capacity is building on sand.
Idle Reclamation: The Rule That Bites
Oracle has documented that Always Free compute instances may be reclaimed if they sit idle. Low CPU, low network, and low memory use over an extended period can trigger it. The exact thresholds have changed over time and are not something to rely on memory for.
The practical fix is simple: give your instance something to do. A small scheduled job, a monitoring agent, or a modest background process keeps utilization above the floor. People who spin up an instance, configure it, and leave it untouched for a month are the ones who come back to find it gone.
This is a reasonable policy from Oracle’s side. Free capacity is scarce, and idle instances waste it. But it does mean the free tier rewards active projects and punishes set-and-forget ones.
Storage Limits and the Boot Volume Trap
The block storage allowance sounds roomy until you realize boot volumes count against it. Every compute instance carries a boot volume, and those add up quickly. A couple of instances with generous boot volumes can eat a large share of the total before you have stored a single file.
Two habits help. First, keep boot volumes small and attach separate block volumes only when you genuinely need them. Second, audit regularly. Orphaned boot volumes from deleted instances are a classic way to hit the ceiling without noticing. Tracking what you actually consume is the same discipline that makes a clearer way to track cloud data transfer costs worthwhile on paid accounts, and it applies just as much when the ceiling is a free tier limit rather than a bill.
Object storage and archive storage have their own allowances. They are useful for backups and static assets, but they are not a substitute for block storage when you need a mounted filesystem.
Eligibility, Payment Cards, and Home Region
Signing up requires a payment card for identity verification. Always Free resources are not charged, but the card is required, and this surprises people who expected a card-free signup. It is a fraud-prevention measure more than anything else.
Always Free resources are also tied to your account’s home region. Changing the home region later comes with restrictions, so pick carefully at signup. If your users are in Europe and you pick a US home region, you may be stuck with higher latency or a migration project you did not plan for.
The region choice also affects capacity. Some regions are more contested than others for Arm instances. There is no official capacity map, but community reports are worth scanning before you commit.
Where the Free Tier Fits and Where It Does Not
The honest answer is that OCI’s free tier is excellent for learning, side projects, small personal services, and proof-of-concept work. It is genuinely useful for anyone who wants hands-on time with cloud infrastructure without a credit card bill.
It is a poor fit for anything that needs guarantees. No capacity guarantee, no uptime commitment beyond the standard service level, and a reclamation policy that can remove idle instances. If a project matters, the free tier is a stepping stone, not a foundation.
For teams thinking about how free tier experimentation scales into real architecture, the transition from a couple of micro instances to a designed environment is where most of the learning happens. That journey is covered well in the material on cloud infrastructure and architecture, which lays out how compute, storage, and networking fit together once you outgrow the sandbox.
Practical Tips That Save Frustration
A few habits separate people who get value from the free tier from those who give up.
Set a budget alert immediately. Even on Always Free, a misconfigured paid resource can accrue charges. Budgets and alerts are free and take two minutes.
Label everything. Free tier accounts accumulate orphaned resources fast. Tags make cleanup possible.
Document what you provision. A short note on what each instance does and which limits it consumes prevents the slow drift into a confusing, half-broken environment. This is the same reason technical writing supports enterprise infrastructure teams so well: written records beat memory every time.
Test the reclamation behavior deliberately. Before you rely on an instance, confirm it stays alive under your normal usage pattern. Better to find out in week one than month three.
Read the docs on the day you sign up. Limits change. A guide written a year ago may describe an allowance that no longer exists.
How It Compares in Spirit to Paid Cloud
The free tier is a genuine sample of the paid platform, not a stripped-down toy version. The same console, the same APIs, the same identity model. That is its real value. Skills learned on Always Free resources transfer directly to paid OCI accounts, and much of the operational thinking transfers to other clouds too.
That portability is worth emphasizing. Reliability practices, cost discipline, and architecture patterns do not change when you move from free to paid. They just get higher stakes. The thinking behind how cloud reliability skills transfer to AI infrastructure applies here: the fundamentals of running systems well are consistent regardless of which tier or platform you are on.
What does not transfer is the assumption of free capacity. Paid accounts get priority, and that is the whole point of the model.
Conclusion
The Oracle Cloud Infrastructure free tier is one of the better permanent free offerings available, mostly because the Arm compute and database allowances are large enough to run something real. It rewards people who read the documentation, keep their instances active, watch their storage consumption, and plan for capacity shortages. It punishes people who assume free means unlimited or permanent without conditions.
Treat it as a laboratory rather than a home. Use it to learn the platform, build small things, and develop the habits that will serve you when the bill is real. Check the current limits before you build, keep your boot volumes lean, and give your instances a reason to stay busy.
FAQ
Is the Oracle Cloud free tier really free forever?
The Always Free portion is designed to be permanent, with no expiry date, as long as your account stays in good standing and you stay within the resource limits. The Free Trial is separate and time-limited. The word “forever” comes with conditions: idle instances can be reclaimed, and limits can be revised by Oracle.
Why can’t I launch an Arm instance on the free tier?
Capacity for the Ampere A1 allowance is not guaranteed in every region or availability domain. Free tier capacity is filled opportunistically when paid demand leaves room. Trying different availability domains, launching at quieter times, or starting with a smaller shape often helps.
Do I need a credit card to sign up?
Yes. A payment card is required for identity verification even though Always Free resources are not charged. It is a fraud-prevention measure rather than a billing requirement.
What happens to my instances if I don’t use them?
Always Free compute instances may be reclaimed if they remain idle for an extended period, based on low CPU, network, and memory activity. Running a small scheduled job or monitoring agent keeps utilization above the threshold and avoids this.
Can I change my home region later?
Changing the home region comes with restrictions, so it is best to choose carefully at signup. Free tier resources are tied to the home region, and moving later may not be straightforward or may require recreating resources.
Is the free tier good enough for a real project?
For learning, side projects, and proof-of-concept work, yes. For anything needing guaranteed capacity or uptime, no. The lack of capacity guarantees and the idle reclamation policy make it a stepping stone rather than a production foundation.
