A Cloud VPS with instant delivery and n8n already running in Docker about a minute after payment. Unlimited workflows and executions, community nodes, your credentials on a server only you can reach, and root access when you want more. Same sizes and prices as our plain Cloud VPS.
Pick the datacenter, France or Türkiye, then the size. Per month, incl. VAT, billed monthly or annually with two months free. No setup fee, no execution metering, cancel any time.
Annual billingPay yearly, get 2 months free.12 months for the price of 10, on every plan below.
Save 17%
Cloud n8n VPS S
Personal & small-team automations
vCPU
2 vCores
Memory
4 GB
Storage
40 GB NVMe
Port
1 Gbps
IP
1 IPv4 + 1 IPv6
Executions
Unlimited
n8n
Latest stable
Database
SQLite, Postgres optional
Management
Self-managed
Dozens of workflows on schedules and webhooks, a few running at once. Plenty for one person or a small team.
Pick n8n on Debian 13 at checkout and n8n arrives already running in Docker, exactly as in France, from a server in Bursa. More about our Türkiye location
At checkout
Operating system: n8n on Debian 13
Same price as a plain Türkiye VPS of the same size
Same price as a plain Cloud VPS of the same size, in France or Türkiye
30-day money-back guarantee. No minimum term: cancel any time. Refund policy
What is on the server
A production n8n setup, not a one-click experiment
A clean starting point rather than a black box: Docker, the current n8n release and a compose file you can read and extend.
n8n, latest stableThe community edition in Docker, on the current stable release, listening on port 5678 as soon as the server boots. You create the owner account on first login.
SQLite to start, PostgreSQL when you need itn8n ships on its built-in SQLite database. Add a PostgreSQL container to the compose file when execution history grows or you move to queue mode.
Your domain and TLSPoint a subdomain at the server and put a reverse proxy with a certificate in front of n8n; Caddy does it in a few lines. Webhook URLs then use your domain.
Docker Compose you can readOne compose file in /opt/n8n with the environment variables commented. Updates, restarts and changes are one command each.
Debian 13 with DockerA current Debian with Docker Engine and Compose installed, root access, and nothing else running. Add what your automation needs.
Daily snapshotAn automatic backup of the previous 24 hours, restorable from your client area, on top of n8n's own workflow export.
Updating n8n
Two commands over SSH. Take a workflow export first if you are jumping a major version.
cd /opt/n8n
docker compose pull && docker compose up -d
First login
n8n is up as soon as your server boots. Open http://YOUR_IP:5678 and create your owner account right away; until you do, that address is open to anyone who finds it.
Going to production
Put a reverse proxy with TLS in front of n8n and set N8N_SECURE_COOKIE=true in /opt/n8n/docker-compose.yml before real traffic and credentials go through it.
Your side of the deal:
Creating the owner account on first login · Your domain, reverse proxy and TLS · Updating n8n (one command, see above) · OS updates and security patching · Your workflows, credentials and community nodes · Monitoring executions and disk usage · Backups beyond the daily snapshot — or ask about having it managed on a Fully Managed VPS.
Outbound mail
Outbound SMTP is closed by default
Outbound SMTP ports 25, 465 and 587 are blocked by default. This protects the platform's mail reputation. If a workflow needs to send mail over SMTP, open a ticket and tell us what you are sending; we open it for legitimate use, usually within a few hours.
Sending through a provider's HTTP API, such as Postmark, SendGrid or Amazon SES, works without any change.
Why self-host
Flat price, no meter, your data
No execution counting
Hosted n8n plans meter executions and step up in price as you automate more. A server does not care how many times a workflow runs.
Credentials stay with you
API keys, OAuth tokens and customer data live in a database on a machine only you can log in to, in our France or Türkiye datacenter.
Community nodes
Install any community node from the settings screen, or write your own. Nothing is locked to an approved list.
Room next to n8n
Redis for queue mode, a vector database for AI workflows, a small app that consumes the output. It is your server, add what the automation needs.
Built for
What people run on it
AI agents
Chains of LLM calls with memory and tools, triggered by chat, e-mail or webhooks, with the API keys under your control.
Lead & CRM sync
Form submissions routed, enriched and pushed into the CRM, Slack and the mailing list without a per-task fee.
E-commerce operations
Order events from the shop to the warehouse, invoicing and customer messages, running every minute of the day.
Internal reporting
Scheduled pulls from databases and APIs into spreadsheets, dashboards and morning summaries for the team.
Location
n8n hosting in Europe
Your n8n server runs in our France datacenter, inside the EU, or in Türkiye, depending on the plan, with network-level Anti-DDoS, a 1 Gbps port and unlimited traffic. Workflows, credentials and execution history live on that one server, so you know exactly where your data is, and webhooks from European services have a short trip.
A Debian 13 server with Docker and the current n8n community edition already running, reachable at http://YOUR_IP:5678 the moment it boots, plus root SSH access. The first person to open that address creates the owner account, so do it straight away.
Can I host n8n in Türkiye?
Yes. Pick the Türkiye tab in the plans above: the three Bursa sizes take the same n8n on Debian 13 image at checkout, so n8n is running when the server is handed over, exactly as in France. Choose Türkiye when your users, webhooks or data sources are in Türkiye, the Balkans, the Middle East or the Caucasus.
Are workflows or executions limited?
No. Self-hosted n8n has no execution or workflow counters. The only limit is the server's CPU, RAM and disk, which is why the plans are sized by concurrency rather than by execution count.
How is this different from n8n Cloud?
n8n Cloud is a hosted subscription metered by executions and priced per tier. On a Cloud n8n VPS you run the same open-source n8n on your own server: no metering, community nodes allowed, your credentials and data on a machine only you can log in to, at a flat monthly price. You also take on the updates. The full comparison is in n8n Cloud vs self-hosted.
Can I use my own domain?
Yes, and for production you should. Point a subdomain such as n8n.yourcompany.com at the server, put a reverse proxy with TLS in front of n8n (Caddy does this in a few lines), and set N8N_HOST, WEBHOOK_URL and N8N_SECURE_COOKIE=true in /opt/n8n/docker-compose.yml. Webhook URLs then use your domain.
How do I update n8n?
From SSH: change into /opt/n8n, then run docker compose pull followed by docker compose up -d. It takes under a minute. Take a workflow export or wait for the daily snapshot before a major version jump.
Can I install community nodes and other software?
Yes. Community nodes install from the n8n settings screen. For anything else, Redis for queue mode, a vector database, an extra container, you have root and Docker on the server.
Is it licensed for business use?
n8n community edition is published under the Sustainable Use License, which allows you to use it for your own internal business purposes. Features marked Enterprise in n8n need a licence from n8n GmbH. Your server, your instance: nothing is white-labelled or resold.
What if I need help with a workflow?
Support covers the server, console access, restores and reinstalls. Building or debugging workflows is not included, but our developers do it at $35/hour, quoted first, and we can move you to a managed plan if you want the server looked after too.
How is n8n installed on my server?
It is part of the server image. Debian 13 boots with Docker Engine and Compose installed and n8n running from one compose file in /opt/n8n, so there is nothing to install yourself. That file is yours to read and edit, and the same two commands update n8n or restart it.
Where are the servers, and is it GDPR-friendly?
In our France datacenter, inside the EU, or in our Türkiye datacenter, depending on the plan you pick. Your workflows, credentials and execution data are stored on your own server and nowhere else, which keeps data residency simple; choose France if your data must stay in the EU. You remain the data controller for the personal data your workflows handle, so map what you process as you would on any server.
How are backups handled?
Every server gets an automatic daily snapshot of the previous 24 hours, which you can restore from the client area. Export your workflows from n8n as well before major changes, and keep your own off-site copies if you need anything older than a day.
Can I run n8n in queue mode with workers?
Yes. Queue mode is not switched on out of the box, but you have root and Docker, so you add Redis and PostgreSQL containers to the compose file and start as many workers as the plan has room for. The L plan is sized for queue mode with worker processes. Step by step: n8n queue mode explained.
Can I upgrade later?
Yes. Open a ticket and we move your server to the next size. The disk and the IP address stay the same, and the change is a short reboot. Moving down a size works when your data fits the smaller disk.
Already running n8n somewhere else?
Export your workflows and credentials, order the size you need, and import them on the new instance. If you would like a hand with the move, open a support ticket before you order.