Node.js on Render
Render publishes its own guide for deploying Node.js.
JavaScript runtime used to run servers and build tooling outside the browser.
What Node.js needs.
Every host claims to run Node.js, so the claim on its own decides nothing. These are the things Node.js actually requires from the platform underneath it, and what Render publishes about each. Render documents 3 of the 4.
Persistent processes
Supported
A long-running process is the point: WebSocket connections, in-memory caches and job queues all die with it. A host that only runs functions cannot keep one alive.
Sources (1) →Sources ↓
- Background Workers – Render Docs ↗
“Background workers are services that run continuously (like a web service or a private service), but they don't receive any incoming network traffic.”
Read 2026-09-05 · official docs
Max request duration
Not documented
Anything the process does inside a request — a large upload, a slow query, a streamed response — is bounded by this ceiling.
Docker deployment
Supported
Node apps routinely need a system binary the platform's buildpack does not ship. A Dockerfile is the escape hatch when they do.
Sources (1) →Sources ↓
- Docker on Render – Render Docs ↗
“Render fully supports Docker-based deploys.”
Read 2026-09-05 · official docs
Scales to zero
Supported
An always-on process bills while idle. Scaling to zero removes that cost and adds a cold start to the next request instead.
Sources (1) →Sources ↓
- Free Instances – Render Docs ↗
“Render spins down a Free web service that goes 15 minutes without receiving any inbound traffic.”
Read 2026-09-05 · official docs
What Render documents.
Render publishes its own guide for deploying Node.js.
You can deploy a Node.js Express application on Render in just a few clicks.
Sources (1) →Sources ↓
- Deploy a Node Express App on Render – Render Docs ↗
“You can deploy a Node.js Express application on Render in just a few clicks.”
Read 2026-09-05 · official docs
What it costs to run there.
- Pricing model
- The Hobby plan does not have a monthly fee, so you only pay for usage.
- When you exceed a cap
- Pipeline minutes: overage is auto-purchased, but with no payment method or once the monthly spend limit is hit, Render stops all pipeline tasks including service builds for the rest of the month (platform-wide, all plans)
- Regions
- Oregon, USA; Ohio, USA; Virginia, USA; Frankfurt, Germany; Singapore
Sources (3) →Sources ↓
- Platform Features by Plan – Render Docs ↗
“The Hobby plan does not have a monthly fee, so you only pay for usage.”
Read 2026-09-05 · official docs
- Build Pipeline – Render Docs ↗
“If you run out of pipeline minutes during a given month, you automatically purchase a supplementary amount of minutes for your current tier, unless you've reached your monthly spend limit, or you haven't added a payment method. In the above cases, Render stops running pipeline tasks (including service builds!) for the remainder of the current month.”
Read 2026-09-05 · official docs
- Regions ↗
“Oregon, USA / Ohio, USA / Virginia, USA / Frankfurt, Germany / Singapore”
Read 2026-09-05 · official docs
Whether it suits you.
Workloads that need real background workers and persistent processes alongside web services, deployed from a repository or a Dockerfile. Managed Postgres and static sites run on the same platform.
Consider something else if…
Free web services spin down after 15 minutes without traffic, which makes the free tier unsuitable for anything that must answer immediately.
Visit Render documentation