n8n Self-Hosting: The Real Monthly Cost and Who Maintains It

2. Three infrastructure setups, from simple to scaled

3. Where the money goes

Prices vary by provider and region, so I will not pretend there is one number. The line items are:

• The server. Usually the smallest item for a light workload; it grows with execution volume, memory-hungry workflows, and queue mode workers.
• The database. Free if it runs on the same server, a separate monthly fee if managed.
• Backup storage. Off-server storage for database dumps and the .n8n folder.
• Monitoring and alerting. Often free tiers, sometimes not.
• Paid n8n features, if you need them. SSO, projects, sharing, and Git version control need a paid self-hosted plan. As of October 2026, n8n's pricing page lists Business at €667 a month billed annually for 40,000 executions; check current pricing.
• People's time. Almost always the largest item, covered next.

4. Where the time goes

• Backups that actually restore. A complete backup is the .n8n folder (which holds the credential encryption key) plus the PostgreSQL database if you use one. A CLI workflow export alone is not enough to recover a full instance, and without the encryption key, restored credentials cannot be decrypted (back up and restore). Test a restore before you need one.
• Updates. n8n recommends updating frequently, at least once a month, checking the release notes for breaking changes, and testing first where you can (update n8n). Skipping updates is how you end up jumping several versions at once.
• Monitoring. n8n exposes /healthz, /healthz/readiness (which also checks the database), and /metrics (monitor n8n). Point an uptime checker at them and alert a real person.
• TLS and the reverse proxy. Webhooks need a public HTTPS URL, so certificates and proxy configuration are part of the job (set up SSL).
• Security patching. The operating system, Docker, the database, and Redis all need patches, not just n8n.
• Execution data. Saved executions grow the database; configure execution data pruning so a busy workflow does not fill the disk.

None of this is hard for someone who runs servers. It is easy to neglect when nobody's job description includes it, and that is how self-hosted instances end up three versions behind with backups nobody has tested.

5. n8n Cloud or self-hosted?

n8n's own guide frames it as deciding who manages the infrastructure, then picking a plan (choose how to use n8n). In practice:

• Pick n8n Cloud when nobody on the team wants to run servers, volume fits a Cloud plan comfortably, and there is no rule requiring data to stay on your infrastructure. As of October 2026, Cloud Starter is €20 a month for 2,500 executions and Pro is €50 a month for 10,000, both billed annually (n8n pricing); check current pricing.
• Pick self-hosted when data must stay inside your network or region, execution volume would push you into expensive Cloud tiers, you need custom configuration, or you already run infrastructure and can absorb the maintenance.
• Either way, the instance, the credentials, and the backups should belong to the business, not to whoever built the workflows.

6. How I set it up for clients

When a client chooses self-hosting, I deploy n8n with Docker on their own cloud account, with PostgreSQL, HTTPS, off-server backups that include the encryption key, health checks wired to alerts, and the configuration kept in version control and shipped through a CI/CD pipeline (GitHub Actions or GitLab CI), the same way I deploy any backend service. Then I document the update and restore steps so the client is never dependent on me to keep it running, and offer maintenance for teams that would rather not do it themselves.

Frequently asked questions