Self-hosting removes the limits to amount of workflows and executions.
You can have as many workflows and executions as your hardware and network can handle.
Documentation:
- Prerequisites | n8n Docs
- Scalling n8n | n8n Docs
- Performance and benchmarking | n8n Docs
- Configuring queue mode | n8n Docs
Here are some scenarios:
The bare minimum
I wouldn’t use less than this for any setup.
I’ve used 1 CPU and 1 GB of RAM before and it’s an ok experience, but it’s slow.
Minimal Load: Typically used for testing and low-frequency executions.
- Recommended Specs:
CPU: 1 vCPU
Memory: 2–4 GB RAM
Storage: 1 - 4 GB SSD (sufficient for logs and basic data)
Level 1 – Low Traffic Production
Ideal For: Small teams or low-frequency workflows.
- Specs:
CPU: 2 vCPUs
Memory: 4–8 GB RAM
Storage: 20–40 GB SSD
Provides enough headroom for moderate concurrent workflow executions without overspending.
Level 2 – Moderate Traffic Production
This is my current setup for managing small-to-medium marketing automations.
Ideal For: Growing operations with several concurrent workflows.
- Specs:
CPU: 4 vCPUs
Memory: 8–16 GB RAM
Storage: 40–80 GB SSD (preferably with faster I/O)
More robust resources to handle increased demand and prevent slowdowns during peaks.
Level 3 – High Traffic/Enterprise Production
Ideal For: High-volume, complex workflows with many concurrent executions.
- Specs:
CPU: 8+ vCPUs
Memory: 16+ GB RAM
Storage: 80+ GB SSD, with provisions for scaling storage as needed
Load balancing, separate database server, and redundancy setups. Ideally you should split the installation into MAIN, WORKERs and WEBHOOKs.
This level ensures high reliability, performance, and the ability to handle scaling challenges.
If my reply answers your question, please remember to mark it as a solution.