Skip to content
inetGeek

Node.js on Render

Render publishes its own guide for deploying Node.js.

Compare Render with

JavaScript runtime used to run servers and build tooling outside the browser.

01.

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) →
  • 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) →

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) →

The requirement and the reason it matters are ours. Every value beside them was read from Render's own pages — expand a source to see the sentence it came from.

02.

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) →

Node.js features on Render

Capabilities Render documents specifically for Node.js, with the constraint it documents alongside each.

websockets

Supported

Render web services can accept inbound WebSocket connections from the public internet. [...] In your web service code, you usually extend your existing HTTP server framework with WebSocket support. [...] This example uses Express along with the ws module

background_workers

Supported

Background workers are services that run continuously [...] Background workers help to keep your apps responsive by offloading long-running, asynchronous tasks from your services in the critical request path.

ssh_shell_access

Supported

You can initiate a shell session to your Render service from its Shell page in the Render Dashboard [...] You can also SSH into your services from the terminal after completing setup.

Sources (3) →
  • WebSockets on Render – Render Docs ↗

    “Render web services can accept inbound WebSocket connections from the public internet. [...] In your web service code, you usually extend your existing HTTP server framework with WebSocket support. [...] This example uses Express along with the ws module”

    Read 2026-09-13 · official docs

  • Background Workers – Render Docs ↗

    “Background workers are services that run continuously [...] Background workers help to keep your apps responsive by offloading long-running, asynchronous tasks from your services in the critical request path.”

    Read 2026-09-13 · official docs

  • SSH and Shell Access – Render Docs ↗

    “You can initiate a shell session to your Render service from its Shell page in the Render Dashboard [...] You can also SSH into your services from the terminal after completing setup.”

    Read 2026-09-13 · official docs

03.

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 reached Render stops running pipeline tasks, builds included.
Regions
Oregon, USA; Ohio, USA; Virginia, USA; Frankfurt, Germany; Singapore
Sources (3) →
  • 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 ↗

    “Running out of minutes 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.”

    Read 2026-09-14 · official docs

  • Regions — Render Docs ↗

    “You can deploy Render services to any of the following regions to minimize latency for your users: Oregon, USA Ohio, USA Virginia, USA Frankfurt, Germany Singapore”

    Read 2026-09-14 · official docs

04.

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.

Written by Palash Bagchi on 2026-09-05. This is a recommendation, not a sourced fact — it carries no citation because it is an opinion.

Visit Render documentation

When these numbers change, hear about it. Sources are re-checked monthly; a repricing goes out as a short note.

Confirm by email; unsubscribe from any issue. Your address goes to Kit and nowhere else — what we do with it.

Every page here is sourced and dated.