n8n VPS & Dedicated Servers Plan & Pricing
Express Linux VPS
- 4GB RAM
- 2 CPU Cores
- 60GB SSD Disk Space
- 100Mbps Unmetered Bandwidth
- Once per 4 Weeks Backup
- 1 Dedicated IP
- Ubuntu/CentOS/Debian&More
- No Setup Fee
Express Plus Linux VPS
- 6GB RAM
- 3 CPU Cores
- 100GB SSD Disk Space
- 100Mbps Unmetered Bandwidth
- Once per 4 Weeks Backup
- 1 Dedicated IP
- Ubuntu/CentOS/Debian&More
- No Setup Fee
Basic Linux VPS
- 8GB RAM
- 4 CPU Cores
- 140GB SSD Disk Space
- 200Mbps Unmetered Bandwidth
- Once per 4 Weeks Backup
- 1 Dedicated IP
- Ubuntu/CentOS/Debian&More
- No Setup Fee
Basic Plus Linux VPS
- 12GB RAM
- 6 CPU Cores
- 180GB SSD Disk Space
- 200Mbps Unmetered Bandwidth
- Once per 4 Weeks Backup
- 1 Dedicated IP
- Ubuntu/CentOS/Debian&More
- No Setup Fee
Professional Linux VPS
- 18GB RAM
- 8 CPU Cores
- 240GB SSD Disk Space
- 300Mbps Unmetered Bandwidth
- Once per 2 Weeks Backup
- 1 Dedicated IP
- Ubuntu/CentOS/Debian&More
- No Setup Fee
Professional Plus Linux VPS
- 24GB RAM
- 8 CPU Cores
- 280GB SSD Disk Space
- 300Mbps Unmetered Bandwidth
- Once per 2 Weeks Backup
- 1 Dedicated IP
- Ubuntu/CentOS/Debian&More
- No Setup Fee
Advanced Linux VPS
- 28GB RAM
- 10 CPU Cores
- 320GB SSD Disk Space
- 500Mbps Unmetered Bandwidth
- Once per 2 Weeks Backup
- 1 Dedicated IP
- Ubuntu/CentOS/Debian&More
- No Setup Fee
Advanced Plus Linux VPS
- 32GB RAM
- 16 CPU Cores
- 400GB SSD Disk Space
- 500Mbps Unmetered Bandwidth
- Once per 2 Weeks Backup
- 1 Dedicated IP
- Ubuntu/CentOS/Debian&More
- No Setup Fee
Recommended n8n Hosting Plans
| Recommended VPS Plan | n8n Task Load / Workflow Volume | Usage Tips / Notes |
|---|---|---|
| Express Linux VPS | Light – <100 tasks/day | Best for testing and small personal automations. Use SQLite or lightweight PostgreSQL. Schedule non-critical workflows during off-peak hours. |
| Express Plus Linux VPS | Low to Moderate – 100–300 tasks/day | Suitable for small teams. Enable basic logging and modularize workflows to avoid execution bottlenecks. |
| Basic Linux VPS | Moderate – 300–800 tasks/day | Switch fully to PostgreSQL. Enable database indexing and begin using webhook-first trigger design. |
| Basic Plus Linux VPS | Growing Business – 800–1,500 tasks/day | Enable queue mode to prevent overload during traffic spikes. Separate critical workflows from non-critical ones. |
| Professional Linux VPS | High – 1,500–3,000 tasks/day | Implement structured logging and monitoring. Optimize API-heavy workflows with caching strategies. |
| Professional Plus Linux VPS | High Volume – 3,000–5,000 tasks/day | Workflow isolation recommended. Tune execution queue workers for higher concurrency. |
| Advanced (Plus) Linux VPS | Enterprise – 5,000–8,000 tasks/day | Deploy reverse proxy and monitoring stack. Prepare scaling plan for database and execution layers. |
| Express Dedicated Server or Higher | Mission-Critical – >8,000 tasks/day | Deploy multiple n8n instances behind reverse proxy. Separate database server recommended. Ideal for large-scale enterprise automation. |
Additional Notes on Plan Sizing & Performance
Select your VPS plan based on workflow volume and concurrent task execution, not just total daily tasks. Smaller plans may struggle under high concurrency. Actual load depends on workflow complexity, triggers, and database operations.
2. Task Spikes
Daily task counts show average load, but sudden spikes can overload smaller plans. Higher-tier VPS or dedicated servers handle surges more reliably.
3. CPU & RAM
CPU cores impact parallel task execution; RAM affects caching, queue processing, and database buffering. Upgrading resources ensures stable performance as workflows grow.
4. Queue & Background Processing
Multiple workflows running simultaneously, heavy API calls, or database-intensive tasks increase load. Enabling queue mode and allocating sufficient PHP/Node workers prevents delays.
5. Multiple Instances & Dedicated Resources
For very high-volume automation, deploying multiple n8n instances behind a reverse proxy and using dedicated databases ensures consistent performance and resource isolation.
6. Performance Tips
Optimize workflows, use PostgreSQL indexing, enable caching with Redis/Memcached, and tune execution queues to maintain stability and efficiency in self hosted n8n environments.
n8n VPS vs Dedicated Server: Choosing the Best Fit for You
| Feature | n8n VPS | Dedicated Server | Note |
|---|---|---|---|
| CPU | Virtual CPU (2–16 cores depending on plan) | Full dedicated CPU (4–24+ cores) | CPU cores affect how many workflows and webhook tasks can run concurrently, especially for API-heavy or computation-heavy automations |
| RAM | 2–16 GB | 16–256 GB | More RAM allows larger workflow caching, smoother concurrency, and better handling of multiple parallel executions |
| Storage | SSD 40–400 GB | SSD/NVMe/SATA 1TB–96TB | Storage affects workflow logs, database size, file attachments, and large payload handling |
| I/O Performance | Moderate | High | Dedicated disk I/O reduces latency for database queries, webhook processing, and serving large files |
| n8n Task Load | 50–8,000 tasks/day (depending on plan) | 8,000+ tasks/day | Determines how many workflows or webhook executions can run simultaneously without delays |
| Caching | Redis / Memcached | Redis / Memcached with larger memory allocation | Improves workflow execution speed, reduces database load, and accelerates API-heavy workflows |
| Uptime & Reliability | 99.9% uptime, shared resources | 99.99% uptime, fully dedicated resources | VPS provides stable access for small/medium automation; dedicated ensures highly reliable, mission-critical workflow execution |
| Scalability | CPU up to 16 cores, RAM up to 16GB, SSD up to 400GB | Full hardware control; can add CPU, RAM, storage | Dedicated servers support multiple n8n instances, clustering, and scaling for growing automation needs |
| Cost | Lower | Higher | VPS is cost-efficient for small-to-medium n8n automation workloads; dedicated servers are more expensive but deliver predictable high performance for enterprise-scale or mission-critical workflows |
n8n Automation Solutions for Every User
Developers / Technical Enthusiasts
SMEs / E-commerce Operators
IT Operations / System Administrators
Enterprise Data Teams / Analysts
Why Choose VPSMart for your n8n VPS?
High-Performance Hardware
99.9% Uptime Guarantee
Seamless Scaling
Step-by-Step Guide to Deploy n8n on VPS
Prerequisites
Ubuntu 22.04 VPS with SSH and full root access, a domain pointing to the VPS IP (required for HTTPS), and minimum 2 vCPU with 2GB RAM (4GB RAM recommended).
Step 1: SSH into VPS
ssh root@your_vps_ipConfirm root access:
whoami
# should output: rootStep 2: Update system
apt update && apt upgrade -yStep 3: Install Docker
apt install docker.io -y
systemctl enable docker
systemctl start docker
docker --versionStep 4: Install Docker Compose
apt install docker-compose -y
docker-compose --versionDocker Compose v2 is recommended (
docker compose) for production environments.
Step 5: Create folder structure
mkdir -p /opt/n8n/{data,postgres-data,nginx/conf.d,nginx/log,certs}
cd /opt/n8ndata→ n8n workflow datapostgres-data→ PostgreSQL database storagenginx/conf.d→ Nginx configurationnginx/log→ Nginx logscerts→ HTTPS certificates
Step 6: Create docker-compose.yml
nano docker-compose.ymlPaste the following:
version: "3.8"
services:
postgres:
image: postgres:15
container_name: n8n_postgres
restart: always
environment:
POSTGRES_USER: n8n
POSTGRES_PASSWORD: StrongDBPass123!
POSTGRES_DB: n8n
volumes:
- /opt/n8n/postgres-data:/var/lib/postgresql/data
n8n:
image: n8nio/n8n
container_name: n8n_app
restart: always
depends_on:
- postgres
ports:
- "5678:5678"
environment:
N8N_BASIC_AUTH_ACTIVE: "true"
N8N_BASIC_AUTH_USER: admin
N8N_BASIC_AUTH_PASSWORD: StrongPass123!
DB_TYPE: postgresdb
DB_POSTGRESDB_HOST: postgres
DB_POSTGRESDB_PORT: 5432
DB_POSTGRESDB_DATABASE: n8n
DB_POSTGRESDB_USER: n8n
DB_POSTGRESDB_PASSWORD: StrongDBPass123!
N8N_HOST: yourdomain.com
N8N_PORT: 5678
WEBHOOK_URL: https://yourdomain.com/
N8N_DESCRIPTION: "Deploy n8n on VPS, the best VPS for n8n with easy n8n server setup"
volumes:
- /opt/n8n/data:/home/node/.n8n
nginx:
image: nginx:latest
container_name: n8n_nginx
restart: always
ports:
- "80:80"
- "443:443"
volumes:
- /opt/n8n/nginx/conf.d:/etc/nginx/conf.d
- /opt/n8n/certs:/etc/letsencrypt
- /opt/n8n/nginx/log:/var/log/nginx
depends_on:
- n8nReplace
StrongPass123!andyourdomain.comwith your own passwords and domain.
Step 7: Create Nginx configuration
nano /opt/n8n/nginx/conf.d/n8n.confPaste:
server {
listen 80;
server_name yourdomain.com;
location /.well-known/acme-challenge/ {
root /var/www/certbot;
}
location / {
return 301 https://$host$request_uri;
}
}
server {
listen 443 ssl;
server_name yourdomain.com;
ssl_certificate /etc/letsencrypt/live/yourdomain.com/fullchain.pem;
ssl_certificate_key /etc/letsencrypt/live/yourdomain.com/privkey.pem;
location / {
proxy_pass http://n8n_app:5678;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
}
}Step 8: Obtain Let's Encrypt certificate
- Install Certbot:
apt install certbot -y- Request certificate (port 80 must be accessible):
certbot certonly --webroot -w /var/www/certbot -d yourdomain.com- Certificates will be stored in
/etc/letsencrypt/live/yourdomain.com/.
Step 9: Start the services
docker-compose up -dCheck containers:
docker ps
docker-compose logs -fStep 10: Access n8n
Open in browser:
https://yourdomain.com- Username:
admin - Password: your chosen password
Step 11: Firewall setup (if using UFW)
ufw allow 80/tcp
ufw allow 443/tcp
ufw reloadStep 12: Production maintenance
- Backup
/opt/n8n/dataand/opt/n8n/postgres-dataregularly - Monitor Docker container status
- Auto-renew Let's Encrypt certificate:
certbot renew --dry-run - Upgrade VPS resources if workflow volume increases
What Can You Integrate with n8n?
FAQ for n8n VPS Hosting
What is self hosted n8n and why should I use it?
Can I integrate self hosted n8n with other internal services?
Is n8n VPS hosting secure?
How can I scale n8n self hosting as my automation grows?
Can I run multiple self hosted n8n instances on the same VPS?
What happens if my VPS reaches resource limits?