Self-host n8n on a 6-dollar VPS: the complete setup walkthrough

Self-host n8n vps is a practical setup for a small automation stack if you want control over data, DNS, HTTPS, and update timing without paying for a larger platform. n8n’s own docs say a single Linux server with Docker Compose is the standard path for cloud-provider deployments, and that this is aimed at expert users rather than beginners.¹²

What does a 6-dollar VPS actually buy you?

A 6-dollar VPS is enough for a small self-hosted n8n instance when the workload is modest and the stack stays simple. n8n’s Docker Compose guide is built around a single Linux server with separate containers for n8n, database, and reverse proxy, which is the right shape for a lightweight production setup.¹

For this tutorial, think in terms of a solo operator or small team running a handful of workflows, not a queue-heavy automation engine. If you expect many parallel executions, large files, or heavy community-node use, the same docs point you toward the broader hosting guides for scaling beyond a starter VPS.³

What is the minimum safe stack?

The minimum safe stack is n8n + PostgreSQL + reverse proxy + persistent storage. The official cloud-provider walkthrough explicitly uses Docker Compose to orchestrate those moving parts, sets a DNS A record for a subdomain, and then terminates HTTPS through a proxy such as Traefik, Caddy, or Nginx with Let’s Encrypt.¹

That matters because the cheapest mistake is treating n8n like a throwaway container. The docs warn that self-hosting requires server, container, security, and resource-management skills, and that mistakes can cause data loss, security problems, and downtime.²

How do you set up self host n8n vps step by step?

The standard setup is: provision a Linux VPS, point a subdomain at it, install Docker and Docker Compose, create the n8n project files, start the stack, and confirm HTTPS access on your subdomain.¹²

The official docs also make the workflow unusually explicit: create the project directory, add a .env file, define local-files, and keep critical settings in environment variables so the container can be recreated cleanly later.¹

1) Provision the server and DNS first

Start with a basic Linux VPS from a provider such as Hetzner or DigitalOcean, then create a DNS A record for a subdomain like n8n.example.com pointing to the server IP.¹

That DNS step is not optional window dressing. n8n’s Compose guide assumes the subdomain is in place before the reverse proxy and TLS flow are brought up, because HTTPS certificates need a stable hostname to terminate correctly.¹

2) Install Docker and Docker Compose

Use Docker and Docker Compose rather than a bare-metal install. n8n explicitly recommends Docker for most self-hosting needs because it creates a clean isolated environment and makes updates and rollbacks easier.²

That recommendation is practical, not decorative. The same docs show the Compose-based update flow as a simple pull-down-recreate cycle, which is much easier to reason about than hand-updating packages across the machine.²

3) Create the project files

Inside your server project directory, create the files n8n expects: .env, compose.yaml, and a local-files directory for host-accessible files.¹

The docs are direct about the reason: persistent volumes and host-mounted paths protect workflows, configuration, and execution data when containers are recreated or images change.¹²

4) Configure the environment file

Put your domain, subdomain, database credentials, encryption key, and host settings into .env instead of hardcoding them into the compose file.¹

That setup usually includes values such as DOMAIN_NAME, SUBDOMAIN, N8N_HOST, and database secrets, which n8n then mounts into the container to control URLs, security, and persistence.¹

5) Bring up the stack

Run the Compose stack after the DNS record has propagated and the files are in place.¹

At that point, the reverse proxy should handle TLS and you should be able to reach the instance at https://n8n.example.com once certificates are issued.¹

What should the Compose setup look like?

The Compose setup should separate concerns: one container for n8n, one for PostgreSQL, and one for the reverse proxy, with shared volumes and a common network where needed.¹

That is the key advantage of Docker Compose on a cheap VPS: it keeps the entire deployment readable in one file while still preserving the isolation you want for production-ish use.¹²

Setup choice	Why it matters	Best for
Docker Compose	Simple updates, rollback, isolated services	Most small self-hosted n8n VPS setups
Bare-metal install	More manual dependency handling	Rare, expert-only environments
Single docker run	Fast to start, weak on long-term maintainability	Short tests, not production
Managed platform	Less maintenance, higher recurring cost	Teams that want less ops work

Why use PostgreSQL instead of just files?

Use PostgreSQL because production self-hosting needs a database that survives container recreation and handles growth more predictably than ad hoc local state.¹²

The official docs’ emphasis on volumes and mounts is the real signal here: if the stack is recreated, the data should still exist outside the container boundary.¹

Why does HTTPS matter on day one?

HTTPS is part of the normal deployment path, not a nice-to-have later step.¹

n8n’s guide explicitly expects the instance to be reached through the subdomain you defined in .env, and the reverse proxy handles certificate termination so the public URL is secure from the start.¹

How much does self hosting n8n cost each month?

A small self-hosted n8n VPS usually lands near $6 to $7 per month for the server itself, with the precise number depending on the provider and plan.¹

Hostinger’s current self-hosted n8n page lists a KVM 1 VPS at $6.49/month, which is a useful real-world benchmark for the low end of the market.⁶

A simple cost breakdown

Here is a practical way to think about the bill:

• VPS: about $6 to $7/month for a starter plan⁶
• Domain: typically annual, not monthly, but required for HTTPS and a clean subdomain setup¹
• Backups: either provider snapshots or your own off-server backup target
• Time: initial setup, then update and monitoring time each month

That last line matters more than the VPS price. n8n’s docs are clear that self-hosting is for people who can manage servers, containers, security, and updates without relying on the platform to do the operational work for them.²

How do you keep it reliable after launch?

Reliability comes from persistence, backups, and a disciplined update routine, not from the cheapest host alone.¹²

The docs show persistent volumes and a host-side local-files directory so that workflows and execution data survive container changes, and they describe a simple update process that pulls the new image before recreating the stack.¹²

What backup routine is sane on a small VPS?

A sane backup routine is to back up the database, the n8n config files, and any mounted file directories to a separate location on a schedule.

That is the operational implication of n8n’s persistence guidance: if the data only lives inside the container, an update or failure becomes a recovery exercise instead of a restart.¹²

How do updates work in practice?

The official update flow is straightforward: docker compose pull, then docker compose down, then docker compose up -d.²

That sequence matters because it keeps the same environment variables and volumes in place while replacing the container image, which is the main reason Docker Compose is the recommended path for self-hosting.²

When is a 6-dollar VPS the wrong choice?

A 6-dollar VPS is the wrong choice when you need high concurrency, lots of execution history, large file handling, or a setup that non-technical users must operate alone.

n8n’s own wording is the strongest warning here: self-hosting requires technical knowledge, and mistakes can create data loss, security issues, and downtime.²

What should you upgrade first?

If the instance starts feeling tight, upgrade in this order:

• Storage if executions or file workflows are growing
• RAM if workflows start stalling or the database feels sluggish
• Managed database if you want easier reliability and less local maintenance
• More CPU only when actual load demands it

That matches n8n’s modular hosting docs, which exist specifically to help users move from a basic cloud-provider setup into more advanced hosting patterns when needed.³

What’s the cleanest final architecture for most solopreneurs?

The cleanest architecture is a single Linux VPS with Docker Compose, PostgreSQL, a reverse proxy, HTTPS, persistent volumes, and an off-server backup routine.¹²

That setup is boring in the best way. It is small enough to understand in one sitting, but structured enough to survive updates, certificate renewals, and the occasional workflow mistake without turning into a full-time infrastructure hobby.¹²