Last updated November 11, 2026
Is self-hosted n8n free?
Yes. The Community edition of n8n is free to self-host, with almost the full feature set and no limit on workflows or executions. n8n also offers a free Registered Community edition: register an email and you get folders, debugging in the editor and custom execution data.
n8n is "fair-code" under the Sustainable Use License, not a classic open-source license. In practice:
- Allowed: running your own business on it, building automations for clients on your own instance, charging for setup or consulting, and using it behind the scenes in your product.
- Not allowed: hosting n8n as a service where your clients build their own workflows, letting end users build workflows inside your product, white-labeling it, or selling a fork that competes with n8n.
A few team features are paid even when you self-host: SSO (SAML and LDAP), Git version control, environments, projects, workflow sharing and external secrets. Those come with the Business plan, which n8n sells for self-hosting only.
Self-hosted n8n vs n8n Cloud: what it costs
n8n Cloud has no free plan, only a trial. Its prices are billed annually; a small VPS is billed monthly.
| Option | Per month | Per year | Executions |
|---|---|---|---|
| Self-hosted on a VPS | €6–12 | €72–144 | Unlimited |
| n8n Cloud Starter | €20 | €240 | 2,500 a month |
| n8n Cloud Pro | €50 | €600 | 10,000 a month |
| n8n Business, self-hosted (SSO and Git) | €667 | €8,004 | 40,000 a month |
On a €6 VPS, self-hosting costs about €72 a year, against €600 a year for n8n Cloud Pro, with no execution limit. The same server can run a database or other apps next to n8n.
With SSH Workbench, add $199 once or $9 a month. Even then, the first year on a €6 VPS comes to about €250, less than half of Cloud Pro, and every year after costs only the server.
What you need
- A Linux VPS. n8n does not publish a minimum spec. Its own docker compose guide asks for 4 GB of RAM and 2 vCPUs, but that stack includes an AI sandbox. A single n8n container with a handful of workflows is lighter; start small and watch memory.
- A domain or subdomain, such as
n8n.example.com. Webhook triggers from GitHub, Stripe or forms need a public HTTPS URL to reach n8n. - Docker or Podman on the server.
Self-host n8n in one click with SSH Workbench
- Connect your server in SSH Workbench and open Apps, then Deploy app, and pick n8n.
- Choose On a subdomain with HTTPS and type your domain. SSH Workbench checks that the domain points at your server, sets up the reverse proxy and an HTTPS certificate from Let's Encrypt, and renews it for you.
- Enter your admin email. The admin password and n8n's encryption key are generated for you; save the password from the screen that appears after the deploy.
- Click Deploy and open your domain to sign in.
To back up, use Back up now in the app's menu. It copies n8n's whole data folder, including the SQLite database and the encryption key, and Restore from backup puts it back. n8n pauses for a few seconds while the copy is taken.
Prefer to keep n8n off the internet? Choose Localhost only instead, and SSH Workbench shows you the SSH tunnel command to open it from your own machine.
Self-host n8n with docker compose
If you would rather set it up by hand, this is the essential part of n8n's official compose setup, trimmed to run behind a reverse proxy on the same server. Replace n8n.example.com and the timezone with your own.
services:
n8n:
image: n8nio/n8n
restart: unless-stopped
ports:
- "127.0.0.1:5678:5678"
environment:
- N8N_HOST=n8n.example.com
- N8N_PORT=5678
- N8N_PROTOCOL=https
- NODE_ENV=production
- N8N_WEBHOOK_URL=https://n8n.example.com/
- N8N_PROXY_HOPS=1
- GENERIC_TIMEZONE=Europe/Berlin
- TZ=Europe/Berlin
volumes:
- n8n_data:/home/node/.n8n
volumes:
n8n_data:Binding to 127.0.0.1 keeps port 5678 closed to the internet. Put a reverse proxy in front for HTTPS. With Caddy installed on the server, this Caddyfile is all it takes:
n8n.example.com {
reverse_proxy 127.0.0.1:5678
}Start it with docker compose up -d and open https://n8n.example.com to create the owner account. N8N_WEBHOOK_URL exists from n8n 2.30; older versions use WEBHOOK_URL instead.
Backups and the encryption key
Everything n8n needs lives in /home/node/.n8n inside the container, the n8n_data volume above: the SQLite database with your workflows and credentials, and the encryption key n8n generated on first start.
Back up that whole folder, not just a workflow export. Without the encryption key, a restored database or a credentials export cannot be decrypted, and every saved credential has to be entered again. If you switch to Postgres, the key still lives in .n8n, so keep backing up that folder as well as the database.
Updating self-hosted n8n
With docker compose, pull the new image and recreate the container:
docker compose pull
docker compose down
docker compose up -dn8n recommends updating at least once a month and reading the release notes for breaking changes before you do. Take a backup first, so you can roll back if a workflow breaks.
SQLite or Postgres?
n8n uses SQLite by default, stored in the data folder. n8n's docs call it fine for trying things out, and recommend Postgres (versions 16 to 18) for production setups that run around the clock or serve more than a handful of users. If you start on SQLite and grow, you can move to Postgres later.
Troubleshooting
Webhook URLs show localhost:5678. n8n builds the address from its own port when nobody tells it about the proxy. Set N8N_WEBHOOK_URL to your HTTPS address and N8N_PROXY_HOPS=1, then restart n8n.
"Secure cookie" warning when you open n8n. You are visiting over plain http://, usually by IP and port 5678. Open it through your HTTPS domain instead. For a quick local test only, N8N_SECURE_COOKIE=false turns the check off.
Webhooks from GitHub or Stripe never arrive. The URL has to be reachable from the internet over HTTPS. Check that ports 80 and 443 are open in your firewall, that the domain's DNS points at the server, and that the webhook URL in n8n matches your domain.
Self-hosting n8n: questions
Is self-hosted n8n safe?
It is as safe as the server it runs on. Put n8n behind HTTPS, keep the admin login strong, update it at least monthly and back up the .n8n folder, which holds your encryption key. Avoid exposing port 5678 directly; route traffic through a reverse proxy so only ports 80 and 443 are open.
Can I self host n8n on my laptop?
Yes, for building and testing workflows. Run the Docker image locally and open localhost:5678. Webhook triggers from services like GitHub or Stripe will not reach a laptop without a public URL, and schedules stop when the laptop sleeps, so move anything you depend on to a VPS.
Where should I self host n8n?
A small Linux VPS is the usual choice: Hetzner, DigitalOcean, Vultr or Hostinger all work, as do AWS and Google Cloud. Pick one close to the services your workflows call. Platforms like Railway or Render also run n8n, but a VPS gives you a fixed IP and costs less once you run several apps.
Can I self host n8n without Docker?
Yes. n8n is a Node.js app, so you can install it with npm install n8n -g on a supported Node.js version and run it as a service with systemd or PM2. Docker is still the setup n8n documents first, because it pins the Node.js version for you and makes updates a single pull.
Should I self host n8n or use n8n Cloud?
Self-host if you want unlimited executions for the price of a server, or need your data on your own infrastructure. Pick n8n Cloud if you would rather pay to never think about updates, backups or uptime. Teams that need SSO or Git version control pay for the Business plan either way.
Related guides
n8n is a trademark of n8n GmbH. SSH Workbench is not affiliated with or endorsed by n8n GmbH.
