n8n on Render
Render publishes its own guide for deploying n8n.
Open-source workflow automation tool deployed from an official Docker image, storing workflows, credentials and execution history that must survive redeploys.
What n8n needs.
Every host claims to run n8n, so the claim on its own decides nothing. These are the things n8n actually requires from the platform underneath it, and what Render publishes about each. Render documents 3 of the 4.
Persistent storage
Supported
Unless it is pointed at an external database, n8n keeps workflows, credentials and execution history on local disk. Without a volume, everything you built disappears on the next deploy.
Sources (1) →Sources ↓
- Persistent Disks – Render Docs ↗
“You can attach a persistent disk to a paid Render web service, private service, or background worker. This enables you to preserve local filesystem changes across deploys and restarts.”
Read 2026-09-05 · official docs
Persistent processes
Supported
Webhook triggers have to be reachable between runs, and a workflow can execute for minutes. Both need a process that stays up rather than one that starts per invocation.
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
Docker deployment
Supported
Every provider guide for n8n starts from the official Docker image. A platform that cannot run a container cannot run n8n.
Sources (1) →Sources ↓
- Docker on Render – Render Docs ↗
“Render fully supports Docker-based deploys.”
Read 2026-09-05 · official docs
Max request duration
Not documented
A workflow calling several slow APIs in sequence is a single HTTP request as far as the platform is concerned, so the request ceiling is what cuts it off mid-run.
What Render documents.
Render publishes its own guide for deploying n8n.
This guide walks through deploying n8n on Render using the official n8n Docker image. [...] Your n8n instance can use one of two methods to store workflow data on Render. The method you choose determines how you configure your deployment
Sources (1) →Sources ↓
- Deploy n8n on Render — Render Docs ↗
“This guide walks through deploying n8n on Render using the official n8n Docker image. [...] Your n8n instance can use one of two methods to store workflow data on Render. The method you choose determines how you configure your deployment”
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