Host a compatible static export as a free static site, or evaluate the Node.js server on a free web service. Choose the route that matches the Next.js features your app uses.
Static exports are free. Each server instance has a fixed monthly price, prorated by the second.
Capability | Render | |||
|---|---|---|---|---|
How Next.js runs | Node.js server or compatible static export | Native Next.js on Functions and the CDN | OpenNext adapter on Functions and Edge Functions | Long-running containers |
Free tier | Free static sites. Free web services spin down | Hobby plan, non-commercial only | 300 credits/month. Sites pause at the limit | $5 trial for 30 days, then $1/month credit |
Static sites | Free, served from a CDN | Served from Vercel's CDN | Global CDN on every plan | Runs as a service, optional CDN caching |
Server rendering | Long-running Node.js web service | Functions, 300s Hobby, 800s Pro, 1800s beta | Functions, 60s limit | Long-running container |
Preview deploys | PR previews. Full-stack preview environments on Pro | Preview deployments | Deploy Previews, unlimited on Free | PR environments |
Managed Postgres and Redis | Postgres from $6 with PITR, plus Key Value | Third-party, via Marketplace | Netlify Database (Postgres) | Maintained databases. HA and Postgres PITR opt-in |
Background workers | Workers and cron jobs | Cron and Workflows. Queues and Daemons in beta | Background functions (15 min) and scheduled functions | Workers and cron jobs |
Competitor details as of November 2026.
Run the Next.js server alongside Postgres and workers, defined in one render.yaml Blueprint.
Run the framework’s production Node.js server for server rendering and route handlers, with instance resources you choose.
Use free static hosting when the app can be fully exported. Select a web service when it needs request-time server features.
Keep server-to-database traffic on the private network in the same workspace and region. Browser requests still use public endpoints.
Move long-running tasks to a worker instead of holding open a page request. Workers and queue storage are separate resources.
Configure a health endpoint so traffic moves after the new server is ready. Keep database migrations compatible with rolling releases.
Plan shared cache and invalidation behavior before adding server instances. Local runtime caches do not automatically become shared state.
Create a Web Service and connect your Next.js repository. Select a Node.js version compatible with your project.


Install dependencies and build with your project scripts, then start the production Next.js server. Make it listen on 0.0.0.0 and the configured service port.
Deploy the first build and test pages, API routes, and authentication. Review cache behavior before adding multiple server instances.