Oracle Cloud: Strong Free Tier, Serious Database

The always-free tier is unusually generous

Most providers offer a trial credit that expires. Oracle offers that too, but it also offers a set of always-free resources that do not expire while the account remains active. The allocation has historically included Arm-based Ampere compute with a meaningful amount of OCPU and memory, a couple of small AMD instances, block volumes, object storage, a load balancer and two autonomous databases.

For a personal project, a small always-on service or a lab, this is the most capacity anyone gives away. The caveat is capacity: free Ampere shapes are heavily subscribed and can be unavailable in a given region, so provisioning sometimes needs patience or a different home region.

The database is the point

If your organisation runs Oracle Database, OCI is where it runs best — Exadata infrastructure, Autonomous Database with self-patching and self-tuning, and licensing terms that are more favourable on Oracle’s own cloud than on someone else’s. That is the commercial logic of the platform and it is a genuine advantage rather than marketing.

Autonomous Database is also worth a look on its own merits for teams with no Oracle history. It is a managed database that handles indexing, patching and scaling with very little operator input, and there is a free instance in the always-free tier to try it on.

Compartments: OCI’s organising idea

Where AWS has accounts and GCP has projects, OCI has compartments — logical containers inside a tenancy that hold resources and carry policy. They can nest. Policies are written as readable statements, for example allowing a group to manage instances in a named compartment.

A tenancy also has a home region, chosen at signup, where identity resources live. You can subscribe to other regions afterwards, but the home region cannot be changed, so pick it deliberately.

Free trial versus pay-as-you-go

This distinction is the main reason the Oracle Cloud configurations are labelled either as free trial or pay-as-you-go, and by region. The two behave differently enough that it changes what you can deploy.

Regions and why they are listed

OCI region names are geographic — Ashburn, Phoenix, Frankfurt, London, Singapore, Tokyo, Osaka, Bogotá and others. Because the home region is fixed at creation and identity lives there, an account’s region is a real attribute rather than a preference, which is why it is stated on each configuration.

Latency follows geography as usual. Free-tier capacity also varies by region, so a less busy region can be the difference between provisioning an Ampere instance immediately and retrying for days.

Getting started on OCI

1. Sign in and change the password; enable multi-factor authentication.
2. Review Identity → Users and Groups, and check for API keys attached to any user.
3. Create a compartment for your work rather than building in the root compartment.
4. Create a Virtual Cloud Network with the wizard — it sets up subnets, gateways and route tables correctly.
5. Launch an instance into your compartment, attaching an SSH key at creation.
6. Open only the ports you need in the security list or network security group.
7. Set a budget under Billing → Cost Management so usage beyond free tier is visible.

One OCI-specific gotcha: instances have both a cloud-level security list and the operating system firewall, and Oracle Linux images ship with a restrictive firewalld configuration. If a port is open in the console and still unreachable, check the OS firewall next.

Common questions

Where to go next

For where OCI sits against the larger clouds, see Oracle Cloud versus AWS. Available accounts by region and type are on the Oracle Cloud account page.