# n8n on Render

Canonical: https://inetgeek.com/stacks/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 requires from the platform underneath it, and what Render publishes about each. Render documents 5 of the 6.

| Requirement | Render | Why it matters |
| --- | --- | --- |
| 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. |
| 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. |
| Docker deployment | Supported | Every provider guide for n8n starts from the official Docker image. A platform that cannot run a container cannot run n8n. |
| 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. |
| Managed databases | Supported | n8n runs on SQLite by default and documents Postgres for production. A guide that leaves it on SQLite is not showing a production install, and the host needs to offer the database that replaces it. |
| Scheduled jobs | Supported | Most n8n workflows begin with a schedule trigger rather than a webhook. Those fire from inside the running instance, so a host that idles the process stops the automations it was installed for. |

- Persistent storage source: https://render.com/docs/disks
- Persistent processes source: https://render.com/docs/background-workers
- Docker deployment source: https://render.com/docs/docker
- Managed databases source: https://render.com/docs/postgresql
- Scheduled jobs source: https://render.com/docs/cronjobs

## What Render documents

> 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

Source: https://render.com/docs/deploy-n8n

### n8n features on Render

- **managed_postgres_backend**: Supported — Store workflow data in a PostgreSQL database separate from your n8n instance. [...] A Render Postgres database that stores your n8n workflow data ([source](https://render.com/docs/deploy-n8n))
- **queue_mode**: Supported — You can run multiple n8n instances that share workflow data, such as in queue mode (a persistent disk is accessible by only a single instance). ([source](https://render.com/docs/deploy-n8n))
- **zero_downtime_redeploy**: Limited — You can redeploy your n8n instance with zero downtime (a persistent disk prevents zero-downtime deploys). ([source](https://render.com/docs/deploy-n8n))
- **version_pinning**: Supported — In both setup methods above, you deploy the version of n8n associated with the latest tag. This version changes over time, which might introduce breaking changes to your workflows. [...] You can instead pin your n8n version to a specific version. ([source](https://render.com/docs/deploy-n8n))
- **scheduled_data_backups**: Supported — Render automatically creates a snapshot of your persistent disk once every 24 hours. If your disk experiences critical data loss or corruption, you can completely restore its state to any available snapshot. ([source](https://render.com/docs/disks))

## What it costs to run there

|  | Render |
| --- | --- |
| 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 |

- Pricing model source: https://render.com/docs/new-workspace-plans
- When you exceed a cap source: https://render.com/docs/build-pipeline
- Regions source: https://render.com/docs/regions

## 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.

## Related

- Best hosting for n8n: https://inetgeek.com/stacks/n8n/
- Render: https://inetgeek.com/hosting/render/