Netlify Review

Plans & pricing

Prices last verified Nov 11, 2026

Free plan limits

Free includes 300 credits a month as a hard limit: once they run out, all projects are paused until the next cycle. A production deploy costs 15 credits, bandwidth 20 credits/GB, compute 10 credits/GB-hour and 10,000 web requests 2 credits.

Free trial

No free trial

Netlify alternatives

VSNetlify vs Render

7.8/10

DigitalOcean

Simple cloud with transparent pricing for developers and small teams

Paid

7.5/10

Cloudflare Workers

Serverless platform on Cloudflare’s global network, billed by CPU time

Freemium

Controversies & incidents

Issues documented by the press, regulators, courts or the vendor itself. Every item is sourced; unproven claims are labelled as allegations. Last researched: Nov 11, 2026

• Medium impactResolvedBilling · Feb 1, 2024

  $104,500 bandwidth invoice for a DDoS-hit static site

  According to the site owner, a small static site received a $104,500 invoice after a DDoS attack; after the case spread publicly, Netlify's CEO said the user would not be charged.

  Read the full account

  According to GIGAZINE (28 Feb 2024), the site owner, Atsh, said the site normally gets about 200 visitors a day, but a DDoS attack generated roughly 190 TB of traffic over four days, peaking at 60.7 TB on 16 Feb 2024, producing a $104,500 invoice at the bandwidth overage rate. GIGAZINE wrote that Netlify normally offers a 20% reduction for DDoS-related overage, but given the size of the bill, support offered to cut it to $5,000. All figures come from the site owner. On the forum, Netlify staff said the company was "deeply sorry" for the impact on users; Netlify's CEO is quoted describing a policy of not shutting down free sites during traffic spikes and instead forgiving bills from legitimate mistakes, and he apologised that the first support reply did not reflect this. The site owner said he had paid nothing, was later told the charge was waived, and moved to Cloudflare. Many forum users asked for spend caps or a kill switch. The case involved a legacy plan; per current docs, credit plans (for accounts created from 4 Sep 2025) pause projects when credits run out instead of billing overage.

  Vendor response

  Netlify staff apologised on the forum on 27 Feb 2024, linking a company statement that its internal systems "should have identified this rare case" before the invoice went out; the CEO said the user would not be charged.

  Sources:Netlify Support Forums: Netlify billing horror storyGIGAZINE: request of 15 million yen after a DDoS attack (2024-02-28)

• Low impactResolvedOutage · Jan 12, 2016

  January 2016 DDoS attacks left sites unresponsive in several regions

  Netlify said a DDoS attack on 12 Jan 2016 caused on-and-off unresponsiveness for about 30 minutes, and a second attack on 13 Jan caused regional downtime.

  Read the full account

  According to Netlify's own postmortem, the first attack targeted CDN nodes in New York, San Francisco, Amsterdam and Chicago at once. Because of an edge case in the failover rules, the DNS servers returned empty records to users in the affected region instead of rerouting them. Netlify called it the first service outage since it began operating and said it fixed the rules; the second attack caused edge nodes to repeatedly leave and rejoin rotation until the traffic director was forced to route around them. This is an old incident and the only source is Netlify itself.

  Vendor response

  Netlify published a postmortem on 13 Jan 2016 and said it fixed the failover rules.

  Sources:Netlify blog: DDoS postmortem (2016-01-13)