If you want a free virtual server in 2026, the choice comes down to two names: Oracle Cloud and AWS. They work in opposite ways. Oracle's Always Free tier gives you a fixed server allowance with no end date. AWS gives new accounts up to $200 in credits that expire after six months. One is a permanent home for a small project, the other is a trial with a generous budget. The right pick depends on what you are building and how long it needs to live.

Oracle's headline allowance is 2 Arm Ampere cores and 12 GB of RAM, plus two small AMD micro VMs, 200 GB of block storage, and 10 TB of outbound data a month. That is a genuinely capable server: it runs Docker, a database, a web app, and a few background services at the same time. The catch is that Oracle quietly cut this allowance in half in June 2026, from 4 cores and 24 GB, without a public announcement. Guides that still quote four cores describe a machine you can no longer create, and instances over the new limit were terminated after August 2026.

AWS's new free tier works differently. Accounts created after July 2025 get $100 in credits at signup and can earn up to $100 more by completing onboarding steps, to spend on any eligible service for up to six months. There is no fixed free EC2 instance anymore for new accounts; your server simply draws down the credit balance. The advantage is flexibility: you can spend the credits on any instance type, any region, and any of the 30-plus always-free services. The disadvantage is the clock: after six months or when the credits run out, the server starts billing at full price.

The practical comparison is about lifetime cost. An Oracle Always Free server that fits your workload costs $0 forever, which over five years saves thousands compared with even a cheap $5 VPS. An AWS credit account costs $0 for six months and then whatever the instance costs, which for a small t4g instance is roughly $30 to $60 a month with storage and data transfer. If your project needs to run for years on no budget, Oracle wins outright. If you need six months to learn AWS, build a prototype, or pass a certification, the AWS credits are the better classroom.

Both have traps. Oracle reclaims idle Always Free instances, so a server you forget about can disappear, and getting an Arm instance allocated can take persistence because capacity is limited in popular regions. AWS bills the card on file the moment credits expire, so a forgotten instance becomes a monthly charge. Both require a card to sign up. The defense is the same for both: set a billing alert at $1, check the usage dashboard monthly, and treat the free tier as a rented room with house rules rather than a gift with no strings.

The verdict is simple. Choose Oracle if you want a permanent free server for a real project and you can live with Arm architecture and occasional capacity quirks. Choose AWS if you want to learn the platform, prototype for a few months, or need services Oracle does not offer. Many experienced developers run both: Oracle hosts the always-on side project, and AWS credits fund the experiment. That combination costs nothing and teaches you both clouds.

Region choice matters more than most comparisons mention. Oracle's Arm capacity is scarce in popular regions, and new accounts sometimes wait days for an instance to become available in their first-choice region. Trying a less popular region often succeeds immediately, and for a side project the region rarely matters. AWS has the opposite problem: capacity is rarely the issue, but prices vary by region, and the cheapest region for a given instance type is not always the one closest to you. Check both the price and the availability before you commit to a region, and remember that moving a server between regions later is a migration, not a setting.