How to Self Host n8n Workflow: A Complete Setup Guide for 2026

To self host an n8n workflow, you deploy the n8n automation platform on your own server or VPS using Docker or Node.js, giving you full control over your data, workflows, and costs. This approach eliminates monthly SaaS fees, removes execution limits, and keeps sensitive business data off third-party infrastructure.

Why Self Hosting an n8n Workflow Makes Sense in 2026

n8n’s cloud plan starts at approximately $20 USD per month and caps workflow executions depending on your tier. When you self host n8n workflow deployments, you pay only for the server itself, which can be as low as $6 to $10 per month on a basic VPS. For teams running hundreds of automations daily, that cost difference adds up fast.

Self hosting also gives you:

• No execution limits or workflow caps
• Full ownership of credentials and webhook data
• The ability to install custom nodes not available on the cloud version
• Offline or private network deployment for sensitive environments
• Version control over your n8n instance using Docker Compose

According to n8n’s own documentation, the self-hosted version supports over 400 integrations, identical to the cloud offering. The difference is simply where the software runs and who controls it.

How to Self Host n8n Workflow Step by Step Using Docker

Docker is the most reliable way to self host an n8n workflow in 2026. It handles dependencies cleanly and makes updates straightforward. You will need a Linux VPS with at least 1 GB of RAM, a public IP address, and a domain name pointed to that server.

1. Provision your VPS: Choose a provider that gives you root access and at least 1 vCPU with 1 GB RAM. Ubuntu 22.04 LTS is a solid choice for compatibility. A KVM-based VPS from a provider like Hostinger gives you dedicated resources and stable performance for running persistent automation workflows.
2. Install Docker and Docker Compose: Run sudo apt update followed by sudo apt install docker.io docker-compose -y. Verify installation with docker --version.
3. Create your Docker Compose file: Create a directory called n8n, then inside it create a docker-compose.yml file. Define the n8n service using the official n8nio/n8n image, map port 5678, and set environment variables for your timezone, basic authentication credentials, and webhook URL.
4. Set up a reverse proxy: Install Nginx and configure it to forward traffic from port 80 and 443 to port 5678. Use Certbot with Let’s Encrypt to generate a free SSL certificate. This step ensures your n8n instance is accessible securely over HTTPS.
5. Start the stack: Run docker-compose up -d from your n8n directory. Visit your domain in a browser, log in with the credentials you set, and your self-hosted n8n workflow environment is live.
6. Enable automatic restarts: Add restart: unless-stopped to your Docker Compose file so n8n comes back online automatically after server reboots.

Persistent data storage is handled by mounting a local volume in your Compose file, so your workflows survive container restarts and updates.

Common Mistakes When You Self Host n8n Workflow Deployments

Most setup failures come from a small set of avoidable mistakes. Knowing them in advance saves hours of troubleshooting.

• Skipping the webhook URL variable: If you do not set WEBHOOK_URL in your environment config, external services cannot reach your n8n triggers. This breaks any workflow that relies on inbound webhooks from tools like Stripe, GitHub, or Typeform.
• Using a shared hosting environment: n8n requires persistent processes and port access. Shared hosting plans do not support this. A VPS or dedicated server is required.
• Forgetting to back up the data volume: Your workflows and credentials are stored in the mounted volume directory. Schedule a daily backup of that folder to remote storage such as an S3-compatible bucket.
• Not setting resource limits: Unrestricted workflows can consume all available RAM. Set memory limits in Docker Compose to prevent the host from becoming unresponsive.
• Running without authentication: Leaving n8n exposed without basic auth or OAuth enabled means anyone who finds your IP can access your automation infrastructure.

Taking 30 minutes to address each of these points during initial setup prevents most production issues.

Best Tools for Self Hosting n8n Workflow in 2026

Three tools cover the core needs of a reliable self-hosted n8n setup: a VPS, a reverse proxy manager, and a backup solution.

Hostinger VPS (KVM 2 Plan)

The Hostinger KVM 2 plan provides 2 vCPUs, 8 GB RAM, and 100 GB NVMe storage, which is more than enough to run n8n alongside a database and several concurrent workflows. It includes full root access, a choice of Linux distributions, and a static IP. For the price, it is one of the best value options for self-hosting automation tools in 2026. You can get started directly through this link: Hostinger KVM 2 VPS.

Nginx Proxy Manager

Nginx Proxy Manager is a Docker-based GUI that simplifies reverse proxy configuration and SSL certificate management. Instead of editing Nginx config files manually, you manage everything through a browser interface. It is free, open source, and integrates directly with Let’s Encrypt for automatic certificate renewal.

BorgBackup with Borgbase

BorgBackup is a deduplication backup tool that compresses and encrypts your n8n data volume before sending it offsite. Borgbase offers a free tier with up to 10 GB of storage, which is sufficient for most n8n setups. Automating a nightly backup job takes about 20 minutes to configure and protects you from data loss during server failures or accidental workflow deletion.

Frequently Asked Questions

What are the minimum server requirements to self host n8n workflow?

Self hosting n8n requires a Linux server with at least 1 GB of RAM, 1 vCPU, and 10 GB of disk space for a basic setup. For production environments handling multiple concurrent workflows, 2 GB RAM and 2 vCPUs are recommended. Docker must be supported, which rules out most shared hosting plans. A VPS or dedicated server is the standard choice for reliable performance.

How much does it cost to self host an n8n workflow compared to the cloud plan?

Self hosting n8n on a budget VPS costs roughly $6 to $15 per month depending on your provider and plan. The n8n cloud starter plan costs approximately $20 per month with execution limits. For teams running high volumes of automations, self hosting saves a significant amount annually and removes all execution caps, making it more cost-effective at scale.

Is self hosting n8n workflow secure for business use?

Self hosting n8n is secure for business use when configured correctly. The setup requires HTTPS via SSL, basic authentication or OAuth, and network-level access controls such as a firewall. Because data never leaves your server, self hosting can actually improve security compared to cloud plans, particularly for workflows handling sensitive credentials, financial data, or personal information governed by privacy regulations.

Can self hosted n8n workflows run without interruption on a budget VPS?

Self hosted n8n workflows run continuously on a budget VPS when Docker is configured with the restart: unless-stopped policy. This ensures n8n restarts automatically after server reboots or container crashes. For critical production workflows, choose a VPS provider with a high uptime SLA, ideally 99.9% or better, and monitor the instance using a free tool like UptimeRobot.

Which database should I use when self hosting an n8n workflow at scale?

PostgreSQL is the recommended database for self hosting n8n at scale. By default, n8n uses SQLite, which works for small deployments but becomes a bottleneck under heavy concurrent load. Switching to PostgreSQL is done by setting the DB_TYPE, DB_POSTGRESDB_HOST, and related environment variables in your Docker Compose file. PostgreSQL handles parallel workflow executions more reliably and supports larger execution history storage.

Conclusion

The most important step in learning how to self host an n8n workflow is getting your VPS provisioned and Docker running before anything else. Every other configuration builds on that foundation. Start with a reliable server, follow the Docker setup process, and your first workflow will be live within a couple of hours. Subscribe to FlowWorks Weekly at https://blog.flowworks.tech/subscribe-to-flowworks-weekly/ for practical automation guides delivered regularly.

Disclosure: This article contains affiliate links. We may earn a commission at no extra cost to you.