Self-Hosting n8n: A Practical Guide for Small Businesses

A self-hosted n8n server gives your business unlimited workflow executions, full control over where data lives and the freedom to run custom code, all for the cost of a modest cloud server. The trade-off is responsibility: you own the uptime, updates, backups and security. This guide explains when self-hosting makes sense, what a production-ready setup looks like and the mistakes we see most often.

n8n Cloud vs self-hosted: which should you choose?

Self-hosting is usually the better choice when you run thousands of executions a day, process sensitive customer data, need specific community nodes or want to avoid per-execution fees. Cloud is better when nobody on the team can look after a Linux server.

Licensing: what you are allowed to do

n8n's self-hosted Community Edition is released under the Sustainable Use License. In plain terms, you can use it to automate your own business processes. Offering n8n itself as a paid hosted service to other companies generally requires a commercial agreement with n8n. Some advanced features, such as SSO and certain environment tools, are reserved for paid Business or Enterprise licences. Read the current licence text before you deploy.

What a production-ready setup includes

A quick Docker command will get n8n running, but a business setup needs more than that.

1. A dedicated server or VPS. Start with 2 vCPUs and 4 GB RAM for light to moderate workloads; scale up for AI or heavy data processing.

2. Docker and Docker Compose. These make updates and rollbacks predictable.

3. PostgreSQL instead of SQLite. The default SQLite database is fine for testing but struggles with concurrency and large execution histories.

4. A reverse proxy with HTTPS. Caddy, Nginx or Traefik terminate TLS so webhooks and the editor are encrypted.

5. A stored encryption key. n8n encrypts credentials with a key; if you lose it, every saved credential becomes unusable after a rebuild.

6. Execution data pruning. Set n8n to delete old execution logs automatically so the database does not grow without limit.

7. Automated backups. Back up the database and workflow exports daily to separate storage.

8. Monitoring and alerts. Uptime checks on the webhook URL plus an error workflow that notifies your team.

Scaling with queue mode

By default, one n8n process handles the editor, webhooks and executions. When volume grows, n8n's queue mode separates these roles: a main instance receives triggers, Redis queues the jobs and multiple worker processes execute them in parallel. This keeps webhooks responsive even when a large batch job is running.

Security checklist

• Keep the editor behind authentication and, ideally, restrict access by IP or VPN.

• Use strong, unique credentials and enable two-factor authentication where available.

• Keep the server patched and update n8n regularly after reading release notes.

• Never expose the database port to the internet.

• Validate incoming webhook requests with a secret header or signature.

• Limit who can create credentials and who can run Code nodes.

Mid-article CTA: Want the benefits of self-hosting without the server admin? Ask us about managed n8n hosting during a free audit call.

Common self-hosting mistakes

• Running on SQLite in production, then hitting locking errors as volume grows.

• Losing the encryption key during a server migration.

• Updating without testing, which can break nodes that changed between versions.

• No error workflow, so failed runs go unnoticed for weeks.

• Letting execution logs fill the disk, which eventually stops the server.

What it really costs

The server bill is often small, typically the price of a mid-range VPS each month. The larger cost is time: initial setup, monthly updates, backup checks and troubleshooting. Budget a few hours a month for a stable instance, more if you are actively building new workflows. For many businesses, that is still far cheaper than per-task pricing on other platforms.

Frequently asked questions

Can I run n8n on my own computer? You can for testing, but production workflows need a server that is always online with a public HTTPS address for webhooks.

Does self-hosted n8n include AI features? Yes. The AI Agent, LLM and vector store nodes are available, and you connect them to providers such as Anthropic or OpenAI using your own API keys.

How do I move workflows from n8n Cloud to self-hosted? Export workflows as JSON and import them, then recreate credentials on the new instance, since credentials are encrypted and do not transfer directly.

How often should I update n8n? Review updates monthly, test them on a staging copy if workflows are business-critical, and keep a backup before every upgrade.

Get a reliable n8n server without the headaches

Calari Solutions deploys, secures and monitors self-hosted n8n for businesses that want control without hiring a DevOps engineer. Book a free audit call and we will size the right server and migration plan for your workflows.