$0 / month
Recurring credits with a hard spending limit.
- 300 credits per month
- One Team Owner
- No credit purchases or auto recharge
Managed deployment for websites and web apps with built-in functions and CDN delivery.
Teams building framework-based web applications that want managed deployment and isolated previews for application and database changes.
Production deploys, requests and runtime usage share a team credit balance. Running out of credits can take every site on the team offline.
Supported platform capabilities, execution environments, development technologies, deployment models, integrations, and triggers.
Published pricing structure, representative costs, and material billing factors.
Monthly team plans share a credit balance across projects. Paid plans require a stored payment method. Eligible older accounts may remain on Legacy pricing; switching to credits is irreversible.
$0 / month
Recurring credits with a hard spending limit.
$9 / month
Paid plan with additional credit purchases.
From $20 / month
Team collaboration and configurable credit tiers.
Current self-serve credit rates. All meters draw from the shared team balance; these are not independent USD rates.
| Resource | Billing Unit | Price |
|---|---|---|
| Production deployments | per successful production deploy | 15 credits |
| Functions compute | per allocated GB-hour | 10 credits |
| Web requests | per 10,000 web requests | 2 credits |
| Web bandwidth | per GB | 20 credits |
| Database compute | per active compute unit-hour | 10 credits |
| Database outbound traffic | per GB | 20 credits |
| Database storage | at rest | No charge currently |
| AI model usage | per USD of model usage | 180 credits |
| Netlify Server compute | Early Access | No charge during Early Access |
All team web projects can pause when the shared credit balance is exhausted. Free teams must wait for renewal or upgrade.
Custom contract and credit terms; published Enterprise credit meters apply only to credit-enabled plans.
Monthly plan fees; optional credit packs or auto recharge on paid plans. Purchased credits carry forward; regular monthly credits typically reset.
Where workloads run, how deployment is scoped, and what underlying infrastructure the platform depends on.
Regional Functions, edge execution, CDN delivery, data placement and Early Access Server have distinct availability footprints.
One region per function. New sites default to Ohio; Pro and Enterprise allow site defaults and per-function overrides. Paris and Milan require support. Region changes require redeployment.
| Location | Region ID |
|---|---|
North America
5 regions
| |
| US East (Ohio) Default for new sites. | cmh |
| US East (N. Virginia) | iad |
| US West (Oregon) | pdx |
| US West (N. California) | sfo |
| Canada (Central) | yul |
Latin America
1 region
| |
| South America (São Paulo) | gru |
Europe
5 regions
| |
| EU (Ireland) | dub |
| EU (Frankfurt) | fra |
| EU (London) Provider-native label; London is in the United Kingdom, outside the EU. | lhr |
| EU (Paris) Support-assisted region selection. | cdg |
| EU (Milan) Support-assisted region selection. | mxp |
Asia Pacific
3 regions
| |
| Asia Pacific (Tokyo) | nrt |
| Asia Pacific (Singapore) | sin |
| Asia Pacific (Sydney) | syd |
Request-time execution at the network edge. No complete execution-location inventory or count is published in the reviewed sources.
Global delivery for static assets, cached responses and Image CDN. No verified public standard-network total.
Enterprise delivery network with dynamic request routing; Netlify publishes 70+ global PoPs. This is not an Edge Functions execution count.
The site-scoped API defaults to the Functions region and accepts a region override. Supported region values, tier-specific placement and replica geography remain unverified.
Each store has one origin region. Deploy stores default to the Functions region; site-wide stores default to Ohio. Changing the region argument does not migrate existing objects. Edge caching is separate from origin placement.
| Location | Area | Region ID |
|---|---|---|
| US East (N. Virginia) | North America | us-east-1 |
| US East (Ohio) | North America | us-east-2 |
| EU (Frankfurt) | Europe | eu-central-1 |
| Asia Pacific (Singapore) | Asia Pacific | ap-southeast-1 |
| Asia Pacific (Sydney) | Asia Pacific | ap-southeast-2 |
Early Access on credit-based and eligible credit-enabled Enterprise plans. One region per configured server; Ohio is the default.
| Location | Area | Region ID |
|---|---|---|
| US East (Ohio) Default region. | North America | cmh |
| EU (Frankfurt) | Europe | fra |
Availability reviewed
60 s synchronous; 30 s scheduled; 15 min background
1,024 MB default; up to 4,096 MB
Configurable on credit-based Pro/Enterprise
6 MB buffered; 20 MB streamed response; 256 KB background
Binary inbound payload may be smaller
50 ms CPU; 40 s response-header timeout
Per request
512 MB memory; 20 MB compressed bundle
Per deployed set
5 GB
Per object
5 GB Free; 100 GB Personal/Pro
Per database; Enterprise has no published storage cap