Skip to main content

Netlify

Platform · PaaS

Managed deployment for websites and web apps with built-in functions and CDN delivery.

Managed deployment for websites and web apps with built-in functions and CDN delivery.

Best for

Teams building framework-based web applications that want managed deployment and isolated previews for application and database changes.

Watch out for

Production deploys, requests and runtime usage share a team credit balance. Running out of credits can take every site on the team offline.

Workloads
  • APIs
  • Backend Services
  • Background Workers
  • Edge Request Processing
  • Scheduled Jobs
  • Static Sites
  • Web Applications
Services
  • Authentication
  • CDN
  • Edge Functions
  • Functions
  • Managed Databases
  • Object Storage
  • Workflows
Hosting model
  • Managed
Netlify builds and deploys websites and web apps from a Git repository. Static assets, server-rendered pages, Functions and Edge Functions ship together as one versioned deploy, with a separate preview URL for each pull request. Netlify Database adds Postgres branches for deploy previews and can suspend database compute when idle. Async Workloads adds durable workflows through a first-party extension. Netlify Server adds long-lived Node.js execution in Early Access.

Development & Execution

Supported platform capabilities, execution environments, development technologies, deployment models, integrations, and triggers.

Runtimes

  • Node.js
  • Deno
  • WebAssembly

Languages

  • Go
  • JavaScript
  • TypeScript

Frameworks

  • Angular
  • Astro
  • Express.js
  • Gatsby
  • Next.js
  • Nuxt
  • Qwik
  • React
  • Remix
  • SvelteKit
  • TanStack Start
  • Vue

Capabilities

  • Compute Autoscaling
  • Scale to Zero
  • Zero-Downtime Application Deployments
  • Deployment Rollbacks
  • Preview Environments
  • Database Branching
  • Automated Backups

Database support

  • PostgreSQL

Deployment & packaging

  • Serverless (Managed Runtime)

Integrations

  • Auth0
  • GitHub
  • GitLab
  • Stripe

Triggers

  • Scheduled Invocation
  • HTTP Requests

Pricing

Published pricing structure, representative costs, and material billing factors.

Starting Price
$9 / month Personal
Primary Billing
Plan based Netlify Credit-Based Plans
Free Tier
Recurring free allowances
Commitment
Monthly plan fees optional credit packs or auto recharge on paid plans. Purchased credits carry forward

Netlify Credit-Based Plans

Primary Pricing

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.

Free

$0 / month

Recurring credits with a hard spending limit.

  • 300 credits per month
  • One Team Owner
  • No credit purchases or auto recharge
Personal

$9 / month

Paid plan with additional credit purchases.

  • 1,000 credits per month
  • One Team Owner
  • $5 per 500 additional credits; optional auto recharge
Pro

From $20 / month

Team collaboration and configurable credit tiers.

  • 3,000 credits at $20 per month
  • Unlimited team members
  • $10 per 1,500 additional credits; optional auto recharge
Credit consumption Additional Usage Cost

Current self-serve credit rates. All meters draw from the shared team balance; these are not independent USD rates.

ResourceBilling UnitPrice
Production deployments No deploy charge for previews, branch deploys, failed deploys or rollbacks; runtime and traffic can still consume creditsper successful production deploy15 credits
Functions compute Scheduled and background Functions included; requests and web bandwidth also count where applicableper allocated GB-hour10 credits
Web requests Includes Edge Functions, previews and branch trafficper 10,000 web requests2 credits
Web bandwidthper GB20 credits
Database compute One unit reserves 0.25 vCPU and 1 GB RAMper active compute unit-hour10 credits
Database outbound traffic Includes output to Netlify Functionsper GB20 credits
Database storage Storage limits still apply; pricing may changeat restNo charge currently
AI model usage Separate environment compute may applyper USD of model usage180 credits
Netlify Server compute Other web meters still apply; GA compute rates not publishedEarly AccessNo charge during Early Access

Free Tier

All team web projects can pause when the shared credit balance is exhausted. Free teams must wait for renewal or upgrade.

  • Shared team credits: 300 credits per month

Enterprise Pricing

Custom contract and credit terms; published Enterprise credit meters apply only to credit-enabled plans.

Billing Commitment

Monthly plan fees; optional credit packs or auto recharge on paid plans. Purchased credits carry forward; regular monthly credits typically reset.

Pricing reference

Function pricing at scale

Includes Netlify Functions.

Monthly requests

1M 10M 100M
  • Short API requests
  • CPU-intensive functions

9 products · 2 workloads

Infrastructure & Availability

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.

Netlify Functions

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.

Applies to

  • Functions

Execution

  • Single Region

Placement

  • Automatic Placement
  • Customer-Selected

Deployment scope

  • Regional

Infrastructure providers

  • Amazon Web Services

Available Regions (14)

LocationRegion 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

Netlify Functions source

Netlify Edge Functions

Request-time execution at the network edge. No complete execution-location inventory or count is published in the reviewed sources.

Applies to

  • Edge Functions

Execution

  • Edge

Placement

  • Nearest Edge

Deployment scope

  • Global

Netlify Edge Functions source

Netlify CDN

Global delivery for static assets, cached responses and Image CDN. No verified public standard-network total.

Applies to

  • Netlify CDN
  • Image CDN

Execution

  • Edge

Placement

  • Request-Routed

Deployment scope

  • Global

Netlify CDN source

High-Performance Edge (Enterprise)

Enterprise delivery network with dynamic request routing; Netlify publishes 70+ global PoPs. This is not an Edge Functions execution count.

Applies to

  • High-Performance Edge (Enterprise)

Execution

  • Edge

Placement

  • Request-Routed

Deployment scope

  • Global

Availability footprint

PoPs
70+ Lower Bound

High-Performance Edge (Enterprise) source

Netlify Database

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.

Applies to

  • Netlify Database

Placement

  • Automatic Placement

Deployment scope

  • Regional

Netlify Database source

Netlify Blobs

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.

Applies to

  • Netlify Blobs

Execution

  • Single Region

Placement

  • Automatic Placement
  • Customer-Selected

Deployment scope

  • Regional

Geographic availability

North America
2
Europe
1
Asia Pacific
2

Infrastructure providers

  • Amazon Web Services

Availability footprint

Regions
5

Available Regions

LocationAreaRegion ID
US East (N. Virginia)North Americaus-east-1
US East (Ohio)North Americaus-east-2
EU (Frankfurt)Europeeu-central-1
Asia Pacific (Singapore)Asia Pacificap-southeast-1
Asia Pacific (Sydney)Asia Pacificap-southeast-2

Netlify Blobs source

Netlify Server (Early Access)

Early Access on credit-based and eligible credit-enabled Enterprise plans. One region per configured server; Ohio is the default.

Applies to

  • Netlify Server (Early Access)

Execution

  • Single Region

Placement

  • Automatic Placement
  • Customer-Selected

Deployment scope

  • Regional

Geographic availability

North America
1
Europe
1

Availability footprint

Regions
2

Lifecycle

  • Early Access

Available Regions

LocationAreaRegion ID
US East (Ohio) Default region.North Americacmh
EU (Frankfurt)Europefra

Netlify Server (Early Access) source

Availability reviewed

Resource & Execution Limits

Function execution

60 s synchronous; 30 s scheduled; 15 min background

Function memory

1,024 MB default; up to 4,096 MB

Configurable on credit-based Pro/Enterprise

Function payloads

6 MB buffered; 20 MB streamed response; 256 KB background

Binary inbound payload may be smaller

Edge CPU and response headers

50 ms CPU; 40 s response-header timeout

Per request

Edge memory and bundle

512 MB memory; 20 MB compressed bundle

Per deployed set

Blob object size

5 GB

Per object

Database storage

5 GB Free; 100 GB Personal/Pro

Per database; Enterprise has no published storage cap

Security & Compliance

Security Controls

Access Control
Team and project roles Site protection varies by plan
Audit Logging
Team audit log Pro and Enterprise
DDoS Protection
Automated mitigation Hosted delivery
Encryption at Rest
AES-256 or stronger Platform security scope
Encryption in Transit
TLS 1.2+ Platform security scope
IP Allow List
Firewall Traffic Rules IP and geography filtering; plan limits apply
Multi-Factor Authentication (MFA)
Two-factor authentication Team enforcement on Pro and Enterprise
Private Networking
Private Connectivity Eligible Enterprise add-on for builds and Functions
Secrets Management
Environment variables and secret detection Smart detection on Personal and above
Single Sign-On
SAML Eligible Enterprise teams
Web Application Firewall
Managed WAF ruleset Enterprise High-Performance Edge

Audits & Certifications

ISO Certifications
ISO 27001 and ISO 27018 Netlify assurance scope
PCI DSS
PCI DSS v4.0 Netlify platform; Database excludes regulated cardholder data
SOC Reports
SOC 2 Type II Netlify assurance scope

Compliance

HIPAA
BAA and compliant-service add-on Enterprise approved configuration; Edge Functions excluded; Database requires compliant setup

FAQ

Can Netlify run a persistent Node.js backend or WebSockets?
Netlify Server can run a long-lived Node.js process and handle WebSockets and server-sent events in Early Access. Idle instances stop, and connections are subject to request-duration and connection limits. Use the Server configuration for this path. Ordinary Functions and Edge Functions are separate execution services.
Does a Netlify Deploy Preview share the production database?
Netlify Database gives a Deploy Preview its own branch, initially copied from production. Schema and data changes made in the preview stay on that branch.
Does rolling back a Netlify deploy also restore the database?
No. Netlify Database restores data through a separate backup operation. A Team Owner can restore a retained backup, which can discard production data and schema changes made since that backup.
What happens to my sites if one Netlify project uses the team’s credits?
All web projects on the team can pause once the shared balance is exhausted. Free users can wait for renewal or upgrade. Personal and Pro can also add credits.
Can I go back to Legacy pricing after switching to credits?
No. Switching to a credit-based plan is irreversible through Netlify’s documented flow. Eligible legacy teams can stay on their existing plan, and moving a project to a credit-based team also prevents transferring that project back to a legacy plan.
Will moving my Netlify Functions to Europe move my existing Blobs?
No. Netlify Blobs keeps existing objects in the region where they were written. Site-wide stores default to Ohio unless you pass another supported region, and moving objects requires copying them into a store opened in the new region.

Explore