STOP AWS: After 6+ Years, Here’s Why I’m Quitting It

🛑 STOP AWS: After more than 6 years of using it, here’s why I’m quitting (and why you should too).

AWS is powerful, essential for large enterprises… But for most projects, it’s more of a burden than an asset.

1. Unnecessary Complexity

Want to deploy an app? AWS buries you under dozens of services: EC2, EKS, IAM, VPC… You spend more time configuring than coding.
With Vercel, Railway, or Cloudflare, it’s plug & play.

2. An Overwhelming and Paralyzing Offer

Too many choices kill action. Need a simple scalable backend? You’re stuck choosing between Lambda, Fargate, EKS, Lightsail…
Meanwhile, solutions like Supabase or Resend get the job done without the headache.

3. Opaque and Risky Pricing

AWS charges for everything: storage, requests, data transfers. You expect a $10 bill and end up with $150.
With Vercel or Cloudflare R2, pricing is transparent and predictable.

4. A Bottleneck to Speed and Execution

AWS slows you down with its complexity.
Today, you can ship a product in a few hours with Vercel or Supabase—no heavy infrastructure needed.

Who is AWS for?

If you’re a large company with a dedicated DevOps team, AWS might make sense.
But if you want to move fast and scale easily, better options exist.

What do you think?