Netlify just sent me a $104k bill for a simple static site

Original Article ↗ Hacker News Discussion ↗

A hobbyist running a small static site on Netlify reports receiving an unexpected $104,000 bandwidth bill after a DDoS-style traffic spike, triggering wider scrutiny of “pay as you go” cloud pricing with no hard spending caps. Commenters argue that unbounded liability for traffic outside a customer’s control is effectively a denial‑of‑money risk, compare Netlify’s high egress rates to cheaper VPS/CDN options, and highlight providers that cap usage or simply suspend service instead of billing unlimited overages. The incident also prompts calls for clearer pricing UX, optional budget limits or regulatory safeguards, and leads many to consider alternatives such as Cloudflare Pages, traditional VPS hosting, or self‑hosting for small sites.

Unbounded billing & DDoS risk

  • Core concern: Netlify’s free/starter plan has no hard cap on bandwidth costs. A sudden spike (e.g., DDoS or bots) can turn a hobby site into a 5‑ or 6‑figure bill without any prior blocking.
  • Many see this as “unbounded liability”: user has no way to say “shut my site off after $X” and is instead asked to beg for discounts after the fact.
  • Conflict-of-interest worry: Netlify profits from attack traffic; its incentives for strong DDoS protection and real-time cutoffs are questioned.

Reactions & migration

  • Numerous commenters say they are deleting Netlify projects or planning to migrate, especially hobby and small-business sites.
  • Cloudflare Pages is the most-cited alternative (unmetered static bandwidth on free tier, built-in DDoS, no surprise egress bills).
  • Others recommend GitHub Pages, Hetzner, BunnyCDN, Render, Firebase Hosting, DigitalOcean/OVH/Contabo VPS, or simple shared/managed hosting.

Pricing comparisons & fairness

  • Netlify’s overage rate (~$55 per 100GB) is repeatedly contrasted with:
    • Cloud providers like AWS/CloudFront (roughly an order of magnitude cheaper for egress).
    • VPS/dedicated hosts like Hetzner (around €1/TB over generous free quotas, often just null-route under DDoS).
    • CDNs like BunnyCDN and BlazingCDN (orders of magnitude cheaper per TB, with prepay/credit and hard bandwidth limits).
  • Some argue Netlify’s margins on bandwidth are “gouging”; others note they also pay upstream (e.g., AWS) and sell a “value-added platform,” not raw transit.

Spend limits, UX, and regulation

  • Strong consensus that providers should offer:
    • User-set hard and soft spend limits.
    • Clear default caps on free tiers.
    • Fast alerts when usage deviates from baseline.
  • Several note that some vendors (e.g., Vercel, Azure, GCP budgets) offer partial mechanisms, but often only notifications or webhook-based DIY shutdowns, not hard guarantees.
  • A number of commenters explicitly call for regulation mandating spend caps for postpaid, usage-based services, likening this to telecom roaming rules.

Self‑hosting & simpler setups

  • Many advocate “old-fashioned” VPS or dedicated servers with nginx as safer and cheaper for most small sites; if overloaded, they just slow down or go offline rather than generating huge bills.
  • Suggested stacks: Hetzner/DigitalOcean/OVH/Contabo + nginx, sometimes fronted by Cloudflare; or self-hosting at home for personal blogs (with awareness of IP/NAT/ISP constraints).

Netlify response & trust

  • A Netlify representative states the user will not be charged and describes an internal policy of forgiving bills from “legitimate mistakes,” claiming they aim not to shut down free sites during spikes.
  • Commenters highlight a mismatch between that statement and support emails mentioning “normal” discounts of 20% and then 5%, not 100%.
  • As a result, many view the resolution as PR-driven and discretionary rather than a reliable guarantee, and say they no longer trust the platform for anything that can’t tolerate surprise bills.

Broader cloud/serverless critique

  • Thread widens into criticism of “serverless” and pay‑as‑you‑go platforms that:
    • Turn scaling problems into billing problems.
    • Market beginner-friendly “free tiers” while hiding complex, risky overage models in fine print.
  • Several conclude that such platforms are better suited to well-funded organizations with FinOps expertise, not individuals or tiny projects.