Why Self-Hosting n8n Changes Everything
If you've been running your automations on the n8n cloud plan, you already know how powerful the tool is. But once your workflows scale, the monthly costs start adding up — and you're limited by execution quotas and data privacy constraints. Self-hosting n8n gives you full control: unlimited executions, your own data, and no vendor lock-in.
The good news? You don't need to be a DevOps engineer to pull this off. With hostinger as your VPS provider, setting up a self-hosted n8n instance is straightforward, affordable, and takes less than 30 minutes.
What You'll Need Before You Start
- A hostinger account with a VPS plan (the KVM 1 plan is enough to start)
- A domain name (optional but recommended for HTTPS access)
- Basic comfort using a terminal or SSH client like PuTTY or iTerm
- About 30 minutes of focused time
That's genuinely it. hostinger takes care of the infrastructure layer, and n8n handles the automation engine. Your job is connecting the two.
Step 1: Set Up Your Hostinger VPS
Log in to your hostinger dashboard and navigate to the VPS section. Choose a plan — the KVM 1 (starting around €3.99/month) is sufficient for most solo automation stacks. Select Ubuntu 22.04 as your operating system. It's stable, well-documented, and works seamlessly with n8n.
Once your server is provisioned by hostinger, you'll receive your server IP, root username, and temporary password. Save these — you'll need them in the next step.
Step 2: Connect to Your Server via SSH
Open your terminal and run:
- Mac/Linux:
ssh root@YOUR_SERVER_IP - Windows: Use PuTTY with your server IP and port 22
Enter your password when prompted. You're now inside your hostinger VPS and ready to install.
Step 3: Install Docker and Docker Compose
The cleanest way to run n8n on hostinger is via Docker. It keeps everything containerised, easy to update, and isolated from other services.
Run the following commands one by one:
apt update && apt upgrade -yapt install docker.io docker-compose -ysystemctl enable docker && systemctl start docker
Once complete, verify Docker is running with docker --version. If you see a version number, you're good to proceed.
Step 4: Create Your n8n Docker Compose File
Create a new directory and configuration file for your n8n instance:
mkdir n8n && cd n8nnano docker-compose.yml
Paste the following configuration into the file:
- image: n8nio/n8n
- ports: 5678:5678
- environment: Set
N8N_BASIC_AUTH_ACTIVE=true, your chosen username, and a strong password - volumes: Map
~/.n8n:/home/node/.n8nto persist your workflows
Save the file with CTRL+X, then Y, then Enter.
Step 5: Launch n8n
Still inside your n8n directory, run:
docker-compose up -d
This pulls the official n8n Docker image and starts the service in the background. Within 60 seconds, your n8n instance will be live and accessible at http://YOUR_SERVER_IP:5678.
Log in with the credentials you set in your docker-compose file. Welcome to your own self-hosted automation hub — running on hostinger infrastructure you control completely.
Step 6: (Optional but Recommended) Add a Domain and HTTPS
Running n8n over plain HTTP is fine for testing, but you'll want HTTPS for production use — especially when connecting to external services and webhooks. Here's how to do it:
- Point your domain's A record to your hostinger VPS IP address
- Install Nginx:
apt install nginx -y - Install Certbot for free SSL:
apt install certbot python3-certbot-nginx -y - Run
certbot --nginx -d yourdomain.comand follow the prompts - Configure Nginx to proxy port 5678 to your domain
Once done, your n8n instance will be securely accessible at https://yourdomain.com — fully encrypted, professional, and ready for production workflows.
How Much Does This Actually Cost?
Here's a realistic cost breakdown for self-hosting n8n on hostinger:
- hostinger KVM 1 VPS: ~€3.99–€5.99/month
- n8n self-hosted: Free (open source, no execution limits)
- SSL certificate via Let's Encrypt: Free
Compare that to n8n's cloud Starter plan at $20/month with execution limits. For power users running dozens of workflows daily, the self-hosted route on hostinger easily pays for itself within a single month.
Common Issues and Quick Fixes
Port 5678 Not Accessible?
Check your hostinger firewall settings. Navigate to your VPS panel and ensure port 5678 is open for inbound traffic. You can also run ufw allow 5678 directly on the server.
n8n Container Keeps Restarting?
Run docker-compose logs to read the error output. Most restarts are caused by missing environment variables or permission issues on the data volume. Double-check your docker-compose.yml configuration.
Workflows Not Persisting After Restart?
Make sure your volume mapping in the n8n Docker config correctly points to a persistent directory. Without this, every container restart wipes your saved workflows.
Final Thoughts
Self-hosting n8n on hostinger is one of the best decisions you can make as an automation builder. You get unlimited executions, complete data ownership, and a cost structure that scales favourably — all without sacrificing the powerful workflow capabilities that make n8n the go-to tool for AI automation in 2024.
Start with the hostinger KVM 1 plan, follow the steps above, and you'll have a production-ready n8n environment running within the hour. Once it's live, the automation possibilities are genuinely limitless.
This post was created with tools we use and recommend: n8n for workflow automation, Turbotic as an AI-native automation alternative, ElevenLabs for AI voiceover, Placid for visual content creation, and Hostinger for reliable VPS hosting. Some links are affiliate links.