Every cloud has a free tier, and most of them are marketing devices: twelve months of small instances designed to expire into paid consumption. OCI took a different approach. The Always Free program has no expiry date, and the headline resources, four Ampere A1 OCPUs with 24 GB of memory, two Autonomous Databases, and around 200 GB of block storage, are large enough to run real software, not just hello world. That generosity is strategic, and it works: a meaningful number of OCI evaluations start as a free tier experiment that proved the platform. But the program has real boundaries, some of them poorly understood, and teams that treat Always Free as a production hosting plan discover those boundaries at the worst possible moment.
This article is part of our complete guide to OCI pricing and TCO. For what the paid meters look like once you cross over, start with OCI pricing explained.
What you actually get, and for how long
The OCI free tier is really two distinct programs stapled together, and conflating them causes most of the confusion. The first is the trial: roughly 300 US dollars of credits valid for 30 days, usable against almost any OCI service at list rates. The second is Always Free: a defined set of resources that remain free indefinitely, before, during, and after the trial. When the trial ends or the credits run out, anything outside the Always Free set stops unless you upgrade to a paid account. Anything inside it keeps running.
| Program | What it includes | Duration | The catch |
|---|---|---|---|
| Trial credits | About 300 dollars across nearly all services at list rates | 30 days | Short window, some capacity types restricted in trial accounts |
| Always Free compute | Up to 4 Ampere A1 OCPUs and 24 GB memory, plus two small AMD micro instances | Indefinite | Capacity is not reserved, idle instances can be reclaimed |
| Always Free database | Two Autonomous Databases with modest compute and around 20 GB storage each | Indefinite | Stops when idle for extended periods, must be restarted |
| Always Free storage and network | About 200 GB block volume allowance, object and archive storage allowances, one flexible load balancer, generous outbound transfer | Indefinite | Allowances sized for small estates, overage requires paid upgrade |
The limits that actually bite
Ampere capacity is contended. The Arm shapes that make Always Free interesting are popular, and in busy home regions the launch request for a free A1 instance can fail with an out of capacity message for days at a time. Paid accounts get priority; free tenancies queue behind them. If your home region is a popular one, this is the single most common frustration, and your home region cannot be changed after signup, so choose it deliberately.
Idle resources are reclaimable. Oracle reserves the right to stop or reclaim Always Free compute that sits idle for an extended period, and Always Free Autonomous Databases stop automatically after days of inactivity. For a lab this is a mild nuisance. For the small internal tool someone quietly promoted to production, it is an outage with no SLA behind it.
No SLA, limited support. Always Free resources carry no service level agreement and free tenancies get community support, not Oracle support. The moment something matters enough to need a response time, it has outgrown the program.
The ceilings are exactly production sized. Four OCPUs, 24 GB of memory, and 20 GB per database is enough to demonstrate almost anything and to operate very little. That is not an accident; it is good product design. The graduation path is the point.
The quiet allowances: network, monitoring, and the rest
Beyond the headline compute and database resources, the program includes a set of less advertised allowances that make the free estate surprisingly complete. Outbound data transfer is generous enough that a small public application can serve real traffic without a network bill, a posture consistent with OCI's famously generous egress pricing stance. One flexible load balancer at modest bandwidth is included, which means the free tier can front a properly load balanced pair of services rather than a single exposed instance. Object and archive storage allowances handle backups and static assets. Monitoring, notifications, and a meaningful slice of the observability stack cost nothing at small scale, and the identity, compartment, and policy machinery of a paid tenancy is all present and free by nature. The practical consequence is that the free tier is not a sandbox with toy semantics. It is a real tenancy with real controls, which is exactly why it works as an architectural rehearsal space: the compartment design, tagging discipline, and policy structure you prototype there transfer unchanged to a paid estate.
Failure stories worth learning from cheaply
Three patterns account for most free tier disappointment, and all three are avoidable with foreknowledge. The first is the production creep story: a free instance hosts a team tool, the tool becomes load bearing, and months later it stops, reclaimed for idleness or simply unlucky, with no SLA and no support path. The fix is honest classification, anything that would page a human if it died does not belong on Always Free. The second is the capacity ambush: a team plans a demo for Thursday, tries to launch an A1 instance on Wednesday, and meets the out of capacity message in their region. The fix is to provision ahead of need and hold the instance, or upgrade to paid where capacity priority changes. The third is the trial cliff: a proof of concept built carelessly across trial credits dies on day 31 because nobody checked which resources were Always Free eligible. The fix is to build inside the Always Free envelope deliberately from the first hour, treating trial credits as expansion room rather than foundation. Each story costs a real team a real week; reading this paragraph is the cheaper version.
Smart uses for the free tier
Used for what it is, the free tier is excellent, and we use it ourselves in client work more often than you might expect.
- Platform evaluation with real workloads. Four Arm OCPUs is enough to containerize a representative service and measure how it behaves on OCI before any commercial conversation starts.
- Proofs of concept that outlive the trial. A demo built inside Always Free limits does not die when the 30 days end, which makes it the right place to build anything a stakeholder might want to revisit in month three.
- Learning Autonomous Database honestly. The two free databases are real Autonomous Databases. Teams evaluating the platform against alternatives can run weeks of unhurried testing, the kind of evaluation we describe in our Autonomous Database practice, before a single dollar is committed.
- Permanent low stakes tooling. A monitoring relay, a webhook receiver, a small internal dashboard. Things that are useful, stateless or easily rebuilt, and tolerant of the no SLA reality.
- Testing the meters themselves. A trial account is the cheapest way to validate calculator assumptions against real billing data before sizing a commitment, a discipline we recommend throughout our cost calculator guide.
A graduation framework: from free to paid without surprises
- Choose the home region carefully at signup. It cannot be changed later, it determines where Always Free capacity is contended, and it should match where a future paid estate would live.
- Inventory what the free tier is actually running. Before upgrading, list every resource and decide which are lab debris and which have quietly become load bearing.
- Upgrade the account, keep the freebies. Converting to Pay As You Go keeps Always Free allowances in place, removes the capacity queueing problem for new paid resources, and unlocks support. It is the lowest friction first step and there is no monthly minimum.
- Promote production candidates onto paid shapes. Anything that needs an SLA, backups with teeth, or room to grow moves to right sized paid resources, costed honestly with the meters from our compute pricing deep dive.
- Set budgets and alerts on day one of paid. The account that was incapable of spending money yesterday can spend it today. A budget with alert thresholds is five minutes of work that prevents the classic first invoice surprise described in hidden costs on OCI.
- Commit only when consumption is measured. Run on Pay As You Go until the workload's real run rate is visible, then size any Universal Credits commitment from data rather than enthusiasm.
Where the free tier fits in a commercial evaluation
For an enterprise weighing OCI, the free tier is the zero risk first move in a sequence: prove the platform free, measure a pilot on Pay As You Go, then negotiate a commitment from evidence. Skipping the middle steps and signing a commitment from a slide deck is how teams end up in the oversizing statistics. The free tier costs nothing to use and removes the last excuse for sizing a deal on guesswork. When the evaluation gets serious enough to involve architecture, landing zones, and a migration plan, that is the point where independent help pays for itself, whether as a fixed fee project, a Managed Monthly arrangement once the estate is live, or an Optimization engagement where our fee is a percentage of verified savings.
The honest summary: OCI Always Free is genuinely free, genuinely useful, and genuinely limited. Use it to learn, to prove, and to host the small things that tolerate its terms. Graduate deliberately, with budgets on and meters understood, and the free tier becomes what it should be, the cheapest good decision in the whole OCI journey.
Free white paper
Go deeper on this topic with The OCI Pricing Decoder, Universal Credits, Support Rewards, and the discounts Oracle does not volunteer. An independent analyst style report with comparison tables and recommendations, free with a work email. Prefer a monthly summary instead? The OCI Brief delivers one practical OCI briefing a month.
Moving Oracle workloads to OCI, or already running on OCI and not sure the architecture or the spend is right? Most teams bring in a specialist before they commit to a region, a shape, or a Universal Credits number. OCISpecialists.com plans the landing zone, runs the migration, and manages the estate after go live, on a fixed project fee, a managed monthly retainer, or a cost optimization fee paid only on verified savings.