- Installing n8n is easy; operating it is a job.
- Classic oversights: encryption key, backups, execution pruning, security updates.
- A stopped n8n triggers nothing, including its own alerts.
- You need an uptime probe and workflow monitoring, outside the server.
Self-hosted n8n appeals for good reasons: controlled cost, data on your side, no execution limit. But between “n8n runs in Docker on my VPS” and “I can run a client's invoicing on it”, there are a dozen settings.
Installation basics
- HTTPS behind a reverse proxy, and the public URL declared correctly, otherwise webhooks do not work.
- PostgreSQL rather than the default database as soon as there is volume.
- A persistent volume for n8n's data.
- The encryption key backed up separately: without it, every stored credential is lost.
Operations
- Daily backups of the database, sent off the server, with a restore test.
- Execution pruning configured: too short and you lose the history; absent and the disk fills up and n8n stops.
- A pinned version of the Docker image, updated deliberately.
- Security patches applied quickly: n8n regularly ships critical fixes, and an instance exposed to the internet is a target.
- Queue mode when a single instance is no longer enough.
Monitoring
- An error workflow on every production workflow. Its limits are detailed here.
- An uptime probe on the instance address. See why it is not enough.
- Workflow monitoring outside the server: a stopped n8n cannot warn you that it is stopped.
The self-monitoring trap
Many instances monitor themselves: an n8n workflow that checks the other n8n workflows. The day the server goes down, the watcher goes down with it. Monitoring has to live somewhere other than what it monitors.
Nokto reads your instance's API every two minutes from the outside, reports an unreachable instance and includes an audit of workflows without error handling. See the guide Monitoring n8n in production.
Frequently asked questions
Is self-hosted n8n free?
The community edition can be used without a paid licence for internal use. You still pay for the server and, above all, for the time to operate it.
Which VPS for n8n?
For a few dozen workflows, a small VPS is enough. Memory becomes the limiting factor with large data volumes and AI agents.