Automation is no longer the preserve of corporations. Today, even small teams want data to flow automatically from CRM to spreadsheets, notifications to messaging apps, and routine actions to be performed without human intervention. This is where n8n comes in—an open-source platform for building automated scenarios without having to write code from scratch.
But once it comes to practice, a logical question arises: where and how to deploy n8n so that it's stable, secure, and doesn't eat into your budget? Experience shows that a dedicated VPS is the optimal option, especially for growing projects with integrations and external APIs.
Why does a business need n8n and why is it installed on a VPS?
n8n isn't just a Zapier alternative. It's a tool for those who want control data, architecture, and costs. It is used for marketing automation, application processing, service synchronization, working with banking APIs, CRM, analytics, and even AI models.
«"n8n is a compromise between the flexibility of custom development and the speed of no-code solutions.".
Hosting n8n on a VPS offers a key advantage: independence. You decide where your data is stored, how webhooks are configured, and who has access to the system. This is especially important for companies working with European services.
What server do I need for n8n?
The basic n8n installation doesn't require any extra resources. Experience shows that a VPS running Linux Debian, 2 GB of RAM, and a 20 GB SSD are sufficient to get started.
Installation Architecture: Why Docker and Nginx Proxy Manager
The official n8n documentation suggests using Traefik, but in practice, this solution is overkill for most scenarios. It's much more efficient to use Docker in conjunction with Nginx Proxy Manager. This approach simplifies management, saves resources, and makes the infrastructure visible even to those who don't live in the terminal.
Less magic - more control. This is exactly what the Docker + Nginx Proxy Manager combination provides.
Docker allows you to isolate services, Portainer allows you to manage them via a web interface, and Nginx Proxy Manager allows you to easily work with domains and Let's Encrypt SSL certificates without manual configuration.
Installing n8n on a VPS
After renting a VPS and installing Debian, the n8n deployment process is logical and predictable. First, the server undergoes basic preparation: creating a separate user, setting up access rights, and updating the system. This isn't a formality, but rather a matter of security and discipline—the server is public, after all.
Next, Docker and Docker Compose are installed. These form the foundation of the entire system. Checking containers, adding the user to the Docker group, and running a test run are essential steps that save hours of troubleshooting later.
The next step is Portainer. It transforms container management from a black screen into a user-friendly dashboard. It also deploys the Nginx Proxy Manager, where subdomains, SSL, and traffic routing are configured. As a result, each service—n8n, Portainer, and the proxy itself—gets its own domain and secure connection.
Only then is n8n itself deployed—as a separate container with a domain, HTTPS, environment variables, and a storage volume. This approach ensures resilience and scalability without unnecessary complications.
N8n VPS use cases
In practice, n8n is most often used for sales and support automation: website requests are automatically sent to the CRM, notifications to Telegram or Slack, and documents to cloud storage. In marketing, n8n connects advertising accounts, analytics, and reports. In finance departments, it synchronizes data between accounting systems and banks.
And all this works stably until the infrastructure becomes a bottleneck. This is where a well-located VPS comes into its own.
When should I install n8n?
Installing n8n on a VPS is a smart choice if you want to control your data, scale without limits, and be independent of SaaS pricing.
n8n gives you the freedom to automate. VPS provides the foundation. And a well-chosen architecture eliminates the urge to "do it all over again" in six months.
Guide: How to Install n8n on a Linux VPS (Debian / Ubuntu)
Automation sounds great in theory—arrows, triggers, magic without code. In practice, it all starts with the mundane: a server, SSH access, and a few evenings of careful configuration. The good news is that n8n is one of those tools where the entry barrier is lower than you might think, as long as you don't try to replicate the "reference" design exactly.
We will take the rational route: Docker + Nginx Proxy Manager + n8n, without overloaded proxies and unnecessary services.
Automation is about control. And control starts with infrastructure.
Step 1: Selecting and Preparing a VPS
You don't need a "monster server" to run n8n reliably. But skimping on resources is also a bad idea.
Minimum reasonable configuration (our tariff START will do):
- 2GB RAM (1GB is a compromise that will come back to haunt you later)
- from 20 GB SSD
- 1 vCPU
- Linux Debian 11/12 or Ubuntu 20.04+
If you are planning integration with foreign APIs (OpenAI, Google, Notion, Stripe).
Step 2: Basic Server Setup and Security
We connect via SSH as root and first of all we do what many people put off until later – we create a separate user.
This isn't paranoia. It's basic hygiene, especially if the server is rented and connected to the public internet.
Step 3: Install Docker and Docker Compose
n8n thrives in containers. Moreover, It's weird to deploy it without Docker today..
Update the system and install Docker from the official repository:
Add the Docker key and repository, then:
Let's check:
If the container has started, then the base is ready.
Step 4. Install Portainer to avoid using the terminal
You can control Docker from the CLI, but In real work it is more convenient to see the whole picture.
After this, Portainer will be available at:
We create an administrator, and we get a visual control panel for the entire infrastructure.
Step 5: Setting up your domain and DNS
n8n does not work well without HTTPS, especially when using webhooks.
Create A-records:
This will allow you to neatly separate services and avoid confusion in ports.
Step 6. Installing Nginx Proxy Manager
In Portainer we create a new one Stack and paste the Nginx Proxy Manager configuration.
Once launched it will be available on the port 81.
This is where we:
- setting up a proxy
- We issue Let's Encrypt SSL certificates
- Getting rid of manual fussing with nginx configurations
Step 7. Unfolding n8n
Now comes the main thing.
In Portainer, we create another Stack with the n8n configuration, specifying:
- domain (
N8N_HOST) - HTTPS
- data storage volume
- auto-clearing of execution history
The container does not start instantly - this is normal.
After deployment, n8n will be available at:
We create a user and the system is ready to work.
What's the bottom line?
Do you have:
- n8n with HTTPS
- separate domain
- visual container management
- infrastructure that is easy to scale
n8n isn't just an automation tool. It's a way to stop repeating the same processes manually.
And choosing the right server rental is the foundation upon which such tools cease to be an experiment and become part of the business.
Just contact us and we will help you choose the best solution for you.
