starter.wikiSearch⌘K

Frontend application platform

Netlify

A managed frontend deployment platform with Git workflows, previews, functions, delivery, and OpenNext-based Next.js support.

Visit official site

Editorial verdict

Choose Netlify when its frontend workflow is a deliberate fit and the application's required framework behavior is verified against the current adapter.12

Best for

  • Teams that value Netlify deploy previews and Git workflow
  • Applications supported by the current OpenNext integration
  • Request-driven web workloads that fit Netlify functions and delivery
12

Not ideal for

  • Persistent services or arbitrary containers
  • Applications assuming unverified Vercel runtime parity
  • Teams that have not modeled credit use across deploy, compute, bandwidth, and requests
12
Main trade-off

A cohesive frontend workflow is gained while framework behavior, billing, runtime limits, and migration remain Netlify-specific.12

Product boundary

Whether Netlify's deployment workflow and current framework adapter fit the application's runtime and billing requirements.

Netlify is a frontend/full-stack application platform, not a persistent-process host or container orchestrator; Next.js behavior depends on current OpenNext support.12

For: Web teams intentionally choosing Netlify's frontend deployment, preview, and delivery workflow

  • Required Next.js behavior is unsupported by the current adapter.
  • Credit-based production usage is materially worse than another platform.
  • The workload needs a persistent process or arbitrary container.

Why teams consider Netlify

  • Frontend workflowGit deployment and previews are integrated with delivery.12
  • Next.js adapterCurrent support is documented through OpenNext.12
  • Managed runtimeFunctions, edge middleware, caching, and image delivery are platform-managed where supported.12

Pricing

Newer accounts use credit-based plans spanning production deploys, compute, bandwidth, requests, and other products; legacy account billing can differ.2

Current account cohort

Credit-based or legacy plan

Model account cohort, included credits, production deploys, compute, bandwidth, requests, and enabled products.2

Billing boundary
Account cohort and multiple credit-consuming products2
Free-plan boundary
Credit exhaustion can pause projects under documented behavior2
Pricing checked View official pricing

Netlify vs alternatives

Vercel

Choose when
Choose the first-party Next.js platform route.
Compared with Netlify
Runtime and usage economics remain Vercel-specific.4

Cloudflare Workers

Choose when
Choose an application designed for the Workers runtime and bindings.
Compared with Netlify
The isolate runtime is not a conventional Node server.56

Railway

Choose when
Choose persistent services and containers.
Compared with Netlify
The team owns more runtime and resource operations.78

Resources and sources

Official product, policy, and pricing

  • Next.js on Netlify
    Open
  • Netlify pricing
    Open
  • How Netlify credits work
    Open
  1. 1
    Next.js on Netlify

    Netlify · Accessed Official

  2. 2
    Netlify pricing

    Netlify · Accessed Official

  3. 3
    How Netlify credits work

    Netlify · Accessed Official

  4. 4
    Vercel documentation

    Vercel · Accessed Official

  5. 5
    Cloudflare Workers documentation

    Cloudflare · Accessed Official

  6. 6
    Workers Node.js compatibility

    Cloudflare · Accessed Official

  7. 7
    Railway services

    Railway · Accessed Official

  8. 8
    Railway pricing

    Railway · Accessed Official