Netlify
Platform for building and deploying web projects from Git to a global CDN, with serverless and edge functions.
- frontend serverless
- Yes
- $9/month for 1,000 credits/month
- Not documented
Who it suits.
Teams that want Git-driven deploys onto a global CDN with a managed Postgres database built into the same platform. The free tier is 300 credits a month with a hard limit, so spend cannot surprise you.
Consider something else if…
You need to run containers or long-lived processes — Netlify does not document either.
Editorial · Palash Bagchi · approved
What the documentation says.
Each value below links to the page it was read from, with the sentence it came from. Criteria Netlify does not publish are not listed.
Pricing
Free tier
Yes
Sources (1) →Sources ↓
- Credit-based pricing plans | Netlify Docs ↗
“$0/month, forever, for 300 credits/month with a hard limit and no auto recharge option.”
Read 2026-09-05 · official docs
Entry paid plan
$9/month for 1,000 credits/month
Sources (1) →Sources ↓
- Credit-based pricing plans | Netlify Docs ↗
“$9/month for 1,000 credits/month, with an auto recharge option (500 credits for $5) if you go over your monthly credits.”
Read 2026-09-05 · official docs
Pricing model
Monthly plan credits are included with your plan each billing cycle and reset at the start of each cycle.
Sources (1) →Sources ↓
- Credit-based pricing plans | Netlify Docs ↗
“By using credits to measure and bill for usage, Netlify users have fewer metrics to track and more flexibility on how to optimize their spending.”
Read 2026-09-05 · official docs
Egress over allowance
20 credits per GB ($0.13 per GB)
Sources (1) →Sources ↓
- Pricing | Netlify ↗
“Bandwidth | 20 credits per GB [...] Bandwidth | 20 | $0.13 per GB”
Read 2026-09-05 · official pricing
When you exceed a cap
Suspended: when credits run out every project is paused and visitors see a Site not available page, unless auto recharge is enabled to buy more credits automatically
Sources (1) →Sources ↓
- How credits work ↗
“Once your credit balance is completely used up, all of your web projects (sites/apps) are paused and visitors to your web projects will find a `Site not available` page at each of your web project's URLs.”
Read 2026-09-05 · official docs
Limits
Memory (entry plan)
1024 MB (1 GB) default memory per function; raising it to 4096 MB (4 GB) requires a Credit-based Pro or Enterprise plan, so Personal is capped at the 1024 MB default
Sources (1) →Sources ↓
- Functions usage and billing | Netlify Docs ↗
“The default memory allocation for Netlify Functions is 1024 MB (1 GB). If you have a Credit-based Pro or Enterprise plan, you can increase the memory allocation of a function up to 4096 MB (4 GB), which also provides a proportionally higher vCPU allocation.”
Read 2026-09-05 · official docs
Sites or apps included
500 projects on the Personal plan (same limit on Free and Pro)
Sources (1) →Sources ↓
- Credit-based pricing plans | Netlify Docs ↗
“Project count limit — Personal: 500 projects”
Read 2026-09-05 · official docs
Monthly visits cap
No fixed visit cap; traffic is metered against the Personal plan's 1,000 credits/month at 2 credits per 10,000 web requests and 20 credits per GB of bandwidth
Sources (1) →Sources ↓
- How credits work ↗
“| Web requests | 2 credits per 10,000 requests | Web traffic requests to your site or app, includes page views, API calls, redirects, requests to serverless functions, asset requests | ... | Bandwidth | 20 credits per GB | Data sent out to the internet, such as assets hosted on Netlify or files downloaded from your site/app. |”
Read 2026-09-05 · official docs
File or inode limit
No limit on files per deploy, but a hard limit of 54,000 files per directory (platform-wide)
Sources (1) →Sources ↓
- Deploy overview ↗
“While Netlify doesn't have a limit on the number of files per deploy, we do have a limit of 54,000 files per directory. If any directory within your publish directory has more than 54,000 files, your deploys will fail.”
Read 2026-09-05 · official docs
Concurrent builds
Personal: 1 concurrent build included, purchasable up to a maximum of 3, at $40/month per additional build
Sources (1) →Sources ↓
- Credit-based pricing plans | Netlify Docs ↗
“1 concurrent build included in plan with option to purchase more. Limited to 3 concurrent builds, meaning up to 3 builds can run at the same time. Ideal for using multiple agents and running projects that depend on each other. Add 1 additional concurrent build as an add-on at $40/month”
Read 2026-09-05 · official docs
Max request duration
60 seconds (synchronous); 30 seconds (scheduled); 15 minutes (background)
Sources (1) →Sources ↓
- Configuration for functions | Netlify Docs ↗
“Synchronous execution limit | 60 seconds | No — Scheduled execution limit | 30 seconds | No — Background execution limit | 15 minutes | No”
Read 2026-09-05 · official docs
Execution
CPU time limit
50 ms of CPU execution time per request for Edge Functions, explicitly excluding time spent waiting on resources or responses. Listed under operation limits with no plan differentiation (applies on the cheapest paid plan).
Sources (1) →Sources ↓
- Edge Functions limits ↗
“CPU execution time per request: 50 ms — This tracks all time spent running your scripts. Execution time does not include time spent waiting for resources or responses.”
Read 2026-09-05 · official docs
Edge function timeout
Response header timeout of 40 s for Edge Functions (the documented time limit on the edge runtime, alongside the separate 50 ms CPU cap). Listed under operation limits with no plan differentiation.
Sources (1) →Sources ↓
- Edge Functions limits ↗
“Operation limits — Edge functions have limits for their size and the amount of memory and execution time they can use: Code size limit: 20 MB after compression … Memory per set of deployed edge functions: 512 MB … CPU execution time per request: 50 ms … Response header timeout: 40 s”
Read 2026-09-05 · official docs
Streaming response limit
Streaming (non-edge) Functions: 60-second execution limit and 20 MB response size limit. Stated without plan differentiation (applies on the cheapest paid plan).
Sources (1) →Sources ↓
- Functions API reference ↗
“A function can stream data to clients as it becomes available, instead of returning a buffered payload after the function finishes. To stream a response, return a ReadableStream as the body of the Response. Streaming functions have a 60-second execution limit and a 20 MB response size limit.”
Read 2026-09-05 · official docs
Deployment
Git deployment
Supported
Sources (1) →Sources ↓
- Git workflows overview | Netlify Docs ↗
“When you push changes to your site's Git repository, Netlify detects your changes and triggers automated deploys, functions, and more across our global CDN.”
Read 2026-09-05 · official docs
Scheduled jobs
Supported
Sources (1) →Sources ↓
- Scheduled Functions | Netlify Docs ↗
“Scheduled Functions is a feature of Netlify Functions that enables you to run functions on a regular and consistent schedule, much like a cron job.”
Read 2026-09-05 · official docs
Infrastructure
Persistent processes
Not supported
Sources (1) →Sources ↓
- Functions overview — Netlify Docs ↗
“When the event happens, Netlify hands your code the event payload, runs it in an ephemeral runtime environment, and acts on whatever it returns. The infrastructure automatically scales according to the volume of traffic to your site, so that the performance stays consistent no matter the load.”
Read 2026-09-05 · official docs
Managed databases
Supported
Sources (1) →Sources ↓
- Netlify Database | Netlify Docs ↗
“Netlify Database is a fully managed Postgres database built into the Netlify platform.”
Read 2026-09-05 · official docs
Edge network
Supported
Sources (1) →Sources ↓
- Edge Functions overview | Netlify Docs ↗
“All this dynamic processing happens in a secure runtime based on Deno directly from the worldwide network edge location closest to each user for fast response times.”
Read 2026-09-05 · official docs