The AWS Free Tier Account, Honestly: A Broke Founder's Guide (2026)

The Day My AWS Advice Expired

Late in 2025, someone in a builder Discord I lurk in asked a simple question: “Is the AWS free tier still 12 months, or did they change it?” And I, the guy who writes a whole blog about not overpaying for infrastructure, typed out a confident answer before checking anything. “Yeah, 12 months on the paid-eligible services, plus the always-free stuff forever. Been that way for years.”

I was wrong. Not a little wrong. Wrong in the specific, embarrassing way where you’re certain, because the fact used to be true and you never noticed it stopped being true.

So I did the thing I should have done before opening my mouth: I went and signed up for a fresh AWS account to see what actually happens in 2026. And the thing that greeted me was not the twelve-month runway I’d been carrying around in my head since forever. It was a credit balance, a countdown, and a note that my account would eventually close itself. AWS had changed the entire shape of the free tier in July 2025, and most of the internet — including me, apparently — hadn’t caught up.

This post is me catching up in public, so you don’t repeat my Discord moment. What the AWS free tier actually is now. What’s genuinely free versus what just looks free until the invoice lands. And the honest answer to the question underneath the question: should a broke founder start here at all? (Spoiler, and it won’t surprise you if you’ve read anything else on this site: no.)

---

What “Free” Used to Mean — and Still Does, If You’re Old

Here’s the part that tripped me up, so let me be precise. There are now two completely different AWS free tiers, and which one you get depends entirely on when you made your account.

If you created your AWS account before July 15, 2025, congratulations — you’re grandfathered. You still have the classic deal everyone remembers: 12 months of free usage on the popular services (a t2.micro or t3.micro EC2 box, some S3 storage, a chunk of RDS), plus the “Always Free” services that never expire — a slab of Lambda invocations a month, DynamoDB storage, and so on. That’s the free tier the tutorials were written about. That’s the one living rent-free in the collective memory of every developer who signed up in the 2010s.

If you made your account after July 15, 2025, none of that applies to you. You’re on the new model. And the new model is a different animal entirely.

---

The New Deal: A Credit Clock That Self-Destructs

Here’s what a brand-new AWS account gets in 2026.

When you sign up, you pick a Free plan or a Paid plan. Choose Free, and AWS hands you $100 in credits up front. You can earn up to $100 more — bringing you to $200 — by poking at a handful of “foundational” services during onboarding: launch an EC2 instance, try Bedrock, that kind of thing. Do the tasks, you top up. That’s the carrot.

Then the clock starts. Your Free plan lasts six months from signup, or until you burn through the credits — whichever comes first. When that window closes, the account doesn’t gently downgrade. It closes. You get a grace period to convert to the Paid plan and keep your stuff, but if you do nothing, the account shuts and the resources get wiped. AWS won’t charge you a cent on the Free plan unless you actively upgrade to Paid — which is genuinely the fairer part of the redesign, credit where it’s due.

There are still 30-plus “always free” services floating around the new plan too, so it’s not nothing after six months. But the headline mental model has flipped. The old free tier was a runway: twelve months to build and learn on real, if small, infrastructure. The new one is a sample platter: two hundred dollars of credit and a half-year to decide whether you’re becoming a paying customer. It’s a sales funnel wearing the costume of a free tier.

That’s not a criticism, exactly. It’s honestly a cleaner deal than the old one in one respect — a Free plan that can’t bill you without an explicit upgrade is safer than the legacy tier, where forgetting to tear something down at month 13 quietly started charging you. But it’s a different promise, and if you walk in expecting the twelve-month runway your favorite 2019 YouTube tutorial described, you’re going to have a bad, confusing time.

---

What’s Actually Free vs What Just Looks Free

The dangerous thing about any hyperscaler free tier isn’t the part that’s free. It’s the seam where free ends and metered begins, because on AWS that seam is invisible until you’re past it.

The old 12-month tier is the classic offender, and legacy-account holders still live with it. Your EC2 free allowance is 750 hours a month of a micro instance. Run one small box around the clock, that’s roughly 730 hours — you’re fine. Spin up a second box “just to test something,” or pick a t3.small instead of micro because the dropdown was right there, and you’ve silently stepped off the free path. Nothing warns you in the moment. There’s no “you are now spending money” banner. The instance just runs, and the meter just counts, and you find out on the first of the month.

S3 is the same story with a different mask. A few gigabytes of storage and a set number of requests are free; go over on requests because you wired up something chatty, and each additional call is a fraction of a cent that adds up in the dark. Data transfer out — egress — is the one that ambushes almost everyone, because it’s easy to forget you’re even paying for bytes leaving the building until a file gets popular.

The pattern, on every AWS service, is the same: the free allowance is a threshold, not a ceiling. Cross it and nothing stops. The meter simply starts charging. Compare that to a $5 flat box, where a bot hammering you all night still costs $5, and you’ll feel in your gut why I keep hammering this point. On AWS, “free” and “$400” are separated by one checkbox you didn’t understand.

---

The Traps That Turn Free Into a Bill

Beyond the metering, there are three specific things that catch bootstrappers on the AWS free tier. I’ve watched all three happen — to me, to friends, to strangers posting screenshots of $600 invoices with the caption “I was on the FREE tier??”

1. The credit card is mandatory. Even for the new Free plan, even though it can’t charge you without an upgrade — AWS requires a valid credit or debit card at signup. They run a small verification charge (about $1) and refund it. The reasoning is fraud prevention and it’s fair enough, but understand what it means: your card is on file from minute one. The barrier between “learning project” and “billed account” is a single click. On a truly free tier, there’s no card to worry about because there’s no card at all. (And once you’re in, the security surface is its own job — I covered the IAM and public-bucket traps in AWS cloud security for founders.)

2. Nothing tears itself down. This is the big one. You spin up an instance to follow a tutorial, or a NAT Gateway for one migration, or a load balancer to test something — and then you close the tab and forget. On the legacy tier, that forgotten resource clicks past the free limit and starts billing hourly. I wrote a whole post about the day I opened AWS Cost Explorer to hunt exactly this kind of ghost — a NAT Gateway nobody remembered creating, charging by the hour and the gigabyte for traffic that didn’t need to exist. The tool found it in twenty minutes. The point of that post, and this one, is that I only needed the tool because I was on AWS. Free resources you forget aren’t free. They’re deferred bills.

3. “Free tier eligible” is per-service, not per-account. People read “free tier” as a mode the whole account is in. It isn’t. It’s a set of allowances attached to specific services and specific instance sizes. Use a service that was never in the free tier, or a size that isn’t eligible, and you’re paying — while the console still cheerfully says you have a free tier. The free tier is a coupon book, not a force field.

None of these are AWS being evil. They’re the natural consequence of a platform built to meter everything for enterprises that want everything metered. It’s just a spectacularly bad fit for one person trying to reach their first paying customer without a finance department watching the console.

---

The Free Tiers That Don’t Need a Watchtower

Here’s the reframe I wish someone had handed me before that Discord message. A free tier is only worth anything to a broke founder if it lets you stop thinking about it. The whole value of “free” is that it removes a worry. An AWS free tier account that you have to guard with billing alerts, anomaly detectors, and a mental note to tear everything down doesn’t remove the worry — it adds one. You’ve traded a monthly fee for a background hum of anxiety, which for a solopreneur is a worse deal, not a better one.

So here’s what I actually run on, and every one of them is either genuinely free or flat-fee cheap, with a ceiling you can see:

• Vercel for the frontend. The Hobby plan is free forever for non-commercial projects — 100 GB of bandwidth a month, and if you blow past a limit it locks the feature rather than silently billing you. When you go commercial you pay $20, and you can set a hard spend cap so a traffic spike bills you a pause, not a four-figure invoice. That cap is the single setting AWS doesn’t really have.
• Neon for Postgres. The free plan carries you absurdly far — up to 100 projects, and in late 2025 they doubled the free compute allowance. I quietly run seven databases on it for $0. It pauses when idle, so a quiet database costs nothing, and it scales to pay-as-you-go with no monthly minimum when you actually have load.
• Cloudflare for the CDN and edge. Their free plan is genuinely generous — a global CDN, free SSL, and Workers at 100,000 requests a day before you pay anything. I don’t use them for everything (I prefer Bunny for storage-heavy work), but the free tier is real and it’s not a trial.
• Railway or Koyeb when I need a backend running 24/7. Railway isn’t truly free anymore — you get a small trial credit, then it’s usage-based from about $5 a month — but it’s flat and predictable. A bot can hammer that box all night and the bill is still five bucks, because I rented the box, not the electricity. That’s the whole difference from AWS in one sentence.

If you genuinely, absolutely must touch AWS — a client makes you, a job requires it — then Lightsail is the least painful corner of it: fixed monthly pricing for a VPS, which is AWS pretending to be DigitalOcean. But if it’s your own project on your own dime, you don’t need the free tier account at all. You need a stack that can’t surprise you. (I ranked the whole field in 7 cheap places to deploy your SaaS, and compared Azure vs AWS for a broke founder — the answer there is the same as here: not yet, probably not ever.)

---

The Bottom Line

The AWS free tier account in 2026 is not the thing your memory says it is. New accounts get $100–$200 in credits and a six-month clock that ends in the account closing itself, not the old twelve-month runway. Only accounts made before July 15, 2025 keep the classic 12-month-plus-Always-Free deal. There’s a mandatory card on file, the meter never stops once you cross an allowance, and every resource you forget is a bill you haven’t received yet.

Learn all of that so nobody can bluff you, and so you don’t confidently give bad advice in a Discord like I did. But then step back and ask the real question. You’re not trying to learn cloud infrastructure. You’re trying to ship something and find someone who’ll pay for it. Every hour spent understanding which EC2 size is free-tier-eligible is an hour not spent on distribution, which is the only thing that was ever going to save you. I added up what a lean SaaS actually costs per month, and there’s no AWS line on it — not because AWS can’t do the job, but because doing the job on AWS requires the exact vigilance a free tier is supposed to spare you.

The best free tier is the one you can forget about. AWS built the opposite: a free tier that demands your attention. So take the two hundred dollars if you’re curious, poke around, learn what the console feels like — then close the tabs before the six months are up, and go build on something that fits in your head.

This is the Broken Engineer Guide — I over-engineer everything, fail at business, and occasionally give wrong advice in Discords so you don’t have to. Now go build something that can’t bill you in your sleep.