AWS to Bare Metal Two Years Later: Answering Your Questions About Leaving AWS

Ditching AWS sparks meme war: millions saved, faster apps, and big questions about cheap servers

TLDR: A company says leaving AWS for its own servers saved $1.2M a year and sped things up, sparking a fiery debate. Commenters split between loving the cost control and warning about cheap hardware risks, while many argue small teams should just buy managed services instead of running their own gear.

The internet’s “cloud vs. metal” drama just got a sequel, and the comments are wilder than the cost charts. After moving off Amazon’s cloud, this team claims $1.2M/year saved, 99.993% uptime, 19% faster apps, and a backup rack in another city. Fans on Hacker News and Reddit crowned them heroes for beating the dreaded egress fees and the meme-worthy “NAT tax.” The victory lap: they’re plowing savings into AI servers to auto-summarize outages and even suggest code fixes.

But the comments? Spicy. One founder says Amazon execs admitted they watch your usage and copy your product, turning the thread into a trust-issues confessional. Pragmatists argue small teams should buy managed services (think PlanetScale or Databricks) instead of babysitting hardware, while “metalheads” cheer the team’s light ops load (about 24 hours a quarter) and no on-site admins. Skeptics throw cold water with a hardware reality check: those super-cheap hosts some people pitch can lack critical memory protection, which is a big nope for databases.

Best joke: calling “Savings Plans” the IKEA manual of cloud bills—still leaves you assembling fees. And for the “single rack” fear? They turned it into romance: Paris-Frankfurt is now a long-distance, dual-rack relationship. The vibe: freedom from the cloud—if your workload fits, and you can handle the heat.

Key Points

  • Measured 99.993% availability over 730+ days on a MicroK8s + Ceph bare-metal stack.
  • Annual savings grew from $230,000 to over $1.2 million, with ~76% savings versus AWS for a steady 24/7 workload.
  • Latency dropped by 19% due to local NVMe storage and elimination of noisy neighbors.
  • Migration effort attributable to bare metal was about one week; ongoing ops require ~24 engineer-hours per quarter plus minimal remote hands.
  • Redundancy added via a second rack in Frankfurt connected to Paris with redundant DWDM, mirrored Ceph pools, and plans to move cluster management to Talos.

Hottest takes

"Amazon execs told us to our face that they use your AWS usage to decide if they were going to copy your services" — pbiggar
"shifting much more towards buying services vs renting infrastructure" — JCM9
"comes without ECC memory... It’s a disaster waiting to happen" — nik736
Made with <3 by @siedrix and @shesho from CDMX. Powered by Forge&Hive.