VM1
Sold out
$ 13,455/ mo
- 1 vCPU
- 1 GB RAM
- 15 GB SSD
- 1 static public IP
- Unmetered transfer (fair use)
- Windows or Linux
- Physical location: Argentina
n8n VPS
n8n VPS: your automations on a server of your own
n8n wires your systems to the usual suspects —email, spreadsheets, databases, APIs— and on your own VPS it runs with no execution caps and without your data passing through anyone else’s cloud. Docker installs it in three commands and it ends up on your domain, over HTTPS.
The short answer
n8n is an open-source automation platform: you build visual flows that connect applications, and every step can be a ready-made node or your own code. Self-hosted on a VPS there are no execution or active-workflow caps, and each service’s credentials stay encrypted on your own server instead of inside someone else’s. At SISArgentina the VPS ships with Ubuntu 24.04 LTS, root SSH access and a static Argentine IP from our Buenos Aires datacenter; with Docker, n8n is up in three commands. We suggest starting on the VM3 plan. Installing and running it is on you: we provide the server, the IP and the operating system.
- n8n
- Docker
- Ubuntu 24.04 LTS
- Caddy
- HTTPS
- PostgreSQL
- Webhooks
- Cron
- SMTP
- API REST
What you get
No execution caps
Your plan is the server, not a price grid per run. A flow that fires a thousand times a day costs the same as one that fires ten times.
Credentials never leave your server
n8n stores the keys of every service you connect, encrypted. On your own VPS that file lives on your disk, not inside an automation vendor’s infrastructure.
Next to your database and your site
If the application you want to automate already runs in our datacenter, the flow reaches it over the internal network instead of going out to the internet and back.
A static Argentine IP for webhooks
One address for the allowlists on the other end, and a stable URL for inbound webhooks, which is the first thing that breaks when the IP moves.
It grows with the project
Start on the SQLite database n8n ships with and, when the flows multiply, move to PostgreSQL and more CPU without changing servers or reinstalling.
n8n VPS plans
These are the usual Cloud VPS plans, and the cart opens with the system already selected. Monthly prices, final price. USD amounts are the official store list; local invoicing is issued in pesos.
VM2
$ 26,910/ mo
- 2 vCPU
- 2 GB RAM
- 30 GB storage
- 1 static public IP
- Unmetered transfer (fair use)
- Windows or Linux
- Physical location: Argentina
Most chosen
VM3
$ 40,365/ mo
- 3 vCPU
- 3 GB RAM
- 45 GB storage
- 1 static public IP
- Unmetered transfer (fair use)
- Windows or Linux
- Physical location: Argentina
VM4
$ 53,820/ mo
- 4 vCPU
- 4 GB RAM
- 60 GB storage
- 1 static public IP
- Unmetered transfer (fair use)
- Windows or Linux
- Physical location: Argentina
n8n running in three steps
-
Install Docker
Log in as root with the IP and password you receive by email and run Docker’s official script, which recognises Ubuntu 24.04 and leaves the service running and enabled.
apt update && apt upgrade -y && curl -fsSL https://get.docker.com -o get-docker.sh && sh get-docker.sh -
Start n8n with its data on a volume
The volume keeps flows, credentials and database outside the container, so updating n8n means pulling the new image and starting it again. Change the domain and keep the port published on 127.0.0.1 only: n8n is reached through the proxy in the next step.
docker volume create n8n_data docker run -d --restart unless-stopped --name n8n \ -p 127.0.0.1:5678:5678 \ -e N8N_HOST=n8n.tudominio.com.ar \ -e WEBHOOK_URL=https://n8n.tudominio.com.ar \ -e GENERIC_TIMEZONE=America/Argentina/Buenos_Aires \ -e TZ=America/Argentina/Buenos_Aires \ -e N8N_ENFORCE_SETTINGS_FILE_PERMISSIONS=true \ -e N8N_RUNNERS_ENABLED=true \ -v n8n_data:/home/node/.n8n \ docker.n8n.io/n8nio/n8n -
Publish it on your domain over HTTPS
Point an A record for the subdomain at the VPS IP and put Caddy in front: it requests the certificate on its own and renews it on its own. Then open https://n8n.tudominio.com.ar and create the instance owner account.
docker run -d --restart unless-stopped --name caddy --network host \ -v caddy_data:/data caddy \ caddy reverse-proxy --from n8n.tudominio.com.ar --to 127.0.0.1:5678
Read on: Primeros pasos al recibir un VPS: la checklist de seguridad · Snapshots y backups en un VPS: la diferencia que salva
Frequently asked questions
How is this different from n8n cloud?
n8n cloud charges by executions and active workflows, and the credentials of everything you connect live on their side. On your own VPS there are no such caps and the credentials file sits on your disk. In exchange, installing, updating and backing up are yours to handle.
Is SQLite enough or do I need PostgreSQL?
To start, yes: n8n ships with SQLite and there is nothing to configure. Once the execution history grows or several flows run at the same time, moving to PostgreSQL pays off; it runs as a second container on the same VPS and you point n8n at it with the DB_TYPE and DB_POSTGRESDB_* variables.
Which plan suits n8n?
The VM3 (3 vCPU, 3 GB, 45 GB) is a comfortable start for an instance on SQLite with flows triggered by webhook or schedule. If you are adding PostgreSQL, processing heavy files or running several flows in parallel, the VM4 gives you room. Moving up a plan needs no migration or reinstall.
How do I update n8n?
Pull the new image, stop the container and create it again with the same command: flows and credentials live on the n8n_data volume, so nothing is lost. It is worth taking a VPS snapshot from the panel first, so you can roll back if a release breaks a flow.
Do inbound webhooks reach it without trouble?
Yes: the VPS has a fixed public IP and the proxy serves port 443, so any external service can call your webhooks. The URL n8n displays comes from WEBHOOK_URL, which is why that value has to be the public domain and not localhost.
Is the server managed?
No. VPS plans and cloud servers are delivered unmanaged: we provide the server with a clean operating system, the static IP and root access, and from there on installing, configuring, updating, securing and backing it up are yours. The commands on this page are the ones in the tool’s official documentation, verified on Ubuntu 24.04, and they are enough to get it running; support for the tool itself is its own documentation and community. If you get stuck with something on the server, write to us and we will lend a hand. And if you would rather not deal with it, our software factory builds custom work on this same infrastructure. Shared hosting with a control panel is a different story: that one we do install and maintain.