Two different free things.
Oracle Cloud's free offering is two distinct programmes that are easy to confuse. The first is Always Free, a set of resources that remain free indefinitely and never expire. The second is the free trial, a block of credits valid for a limited window that converts to paid consumption when the credits are exhausted or the window closes. Understanding which one you are using is the difference between a free learning environment and an unexpected invoice. The buyer side discipline starts with knowing exactly which programme governs each resource you provision, because the two have completely different cost consequences.
What Always Free includes.
The Always Free tier is designed to let developers learn the platform and run small workloads at no cost. It typically includes a pair of small virtual machine compute instances, a limited allocation of Autonomous Database, a quantity of block and object storage, a load balancer, and a monthly outbound data transfer allowance. The resources are deliberately modest. They are sufficient for a personal project, a learning environment, or a small always on service, but they are not sufficient for a production workload of any meaningful scale. The Always Free tier is real and it does not expire, which makes it genuinely useful, but its limits are firm and Oracle adjusts the included resources over time.
Where the trial credits behave differently.
The free trial gives a new account a block of credits to spend on any OCI service for a fixed period, commonly thirty days, with the credits also subject to a total dollar cap. During the trial you can provision resources far larger than the Always Free limits. This is where the cost risk begins. When the trial period ends or the credits run out, any resource that exceeds the Always Free limits begins to bill at standard rates unless the account is upgraded to pay as you go or the resources are torn down. A proof of concept built on trial credits will start charging the moment the trial converts, and the resources do not automatically stop. The buyer side discipline is to set a hard calendar reminder for the trial expiry and to decommission or downsize every non Always Free resource before that date.
Free tier cost control checklist
- Identify which resources are Always Free and which run on trial credits.
- Document the trial expiry date and set a reminder two weeks ahead.
- Tag every resource provisioned during the trial for later teardown.
- Set budget alerts on the tenancy before provisioning anything.
- Confirm the data egress allowance against the workload's transfer profile.
- Decide before the trial ends whether the workload justifies a paid commit.
- Tear down or downsize non Always Free resources before conversion.
The egress limit that surprises people.
Outbound data transfer is the limit that catches most teams off guard. Both the Always Free tier and the trial include an egress allowance, and OCI's egress pricing is favourable compared to the hyperscalers, but a data intensive proof of concept can exhaust the allowance quickly. Once the allowance is gone, egress bills at the standard rate. A workload that moves large volumes of data out of OCI to users, to another cloud, or to an on premises system can generate egress charges that dwarf the compute cost. The buyer side discipline is to model the workload's egress profile before provisioning, not after the first bill arrives.
Using the free tier as a negotiation input.
The free tier is not itself a negotiation lever, but the proof of concept it enables is. A successful proof of concept demonstrates that the workload runs well on OCI and gives you the technical confidence to negotiate a paid commit from a position of knowledge rather than vendor assurance. It also tells you the real consumption profile of the workload, which is the single most important input to sizing a Universal Credits commit correctly. The buyer side discipline is to use the free period to gather consumption data, then to size the commit to that data rather than to Oracle's forecast. We cover commit sizing in our list versus real pricing article and the broader strategy in the cloud negotiation pillar guide.
When to graduate off the free tier.
The decision to move from free to paid should be a financial one. If the proof of concept demonstrates clear value and the consumption is predictable, a paid commit with a negotiated discount is the right next step, and the free tier has done its job. If the workload is small and intermittent, pay as you go beyond the Always Free limits may be more economical than any commit. If the proof of concept reveals that the workload does not fit OCI well, the free tier has saved you from an expensive mistake. The buyer side discipline is to make the graduation decision deliberately and to negotiate the paid arrangement properly. Before signing any consumption commit, have the terms reviewed in a formal contract review and the platform fit assessed through cloud migration advisory.
Related resources.
- Cloud Negotiation pillar guide
- Cloud Migration Advisory service
- Contract Review service
- OCI Universal Credits deal type page
- Oracle OCI product page
- Oracle Negotiation Playbook 58 page reference paper.
- When Oracle Cloud Makes Sense related sub article.