Skip to content
SelfHostBR, home page
Free tool

What size VPS does my n8n need?

Answer a few questions to see the estimated RAM and CPU, along with the cheapest plans that fit. Prices are in US dollars, checked on October 15, 2026. How the estimate works

Your usage

Sorted by entry price, never by commission. Affiliate links, when there are any, carry an “affiliate” label (details).

This is an estimate. The n8n documentation does not publish an official minimum for RAM or CPU. It says usage depends on the volume of data, the size of binary files, the number of nodes, use of the Code node and simultaneous executions (n8n docs, “Fix memory issues”). The ranges below are a starting point: once n8n is running, watch real usage and adjust.

How the estimate works

1Base

1 GB for the operating system and Docker, plus 1 GB for the main n8n process, with 1 vCPU.

2PostgreSQL on the same VPS

+1 GB. n8n uses SQLite by default and supports PostgreSQL 16, 17 and 18 (docs).

3Queue mode

+0.5 GB for Redis, plus 1 GB and 1 vCPU per worker. The documentation says queue mode with SQLite is not recommended and that queue mode does not support binary data on the filesystem; use S3 instead (docs).

4Volume

An estimate, with no official number in the documentation: above 10,000 executions a day, +1 GB and +1 vCPU; above 50,000, another +2 GB and +1 vCPU. Heavy workflows: +2 GB.

5Margin

The result is rounded up to the next common VPS size (2, 4, 8, 16, 32, 64 GB and so on).

6Official reference

The n8n benchmark ran a single instance with PostgreSQL on a machine with 4 GB of RAM (ECS c5a.large) receiving webhooks (docs, “Measure performance”).

Each plan links to the provider’s pricing page. Prices were checked on the date shown at the top of the page: check the current price before you buy. Entry prices on different billing terms are not directly comparable; the notes below the results explain each one.

Recommendedsee plans ↓