Home / Blog / Business Applications and Automation / How to Choose n8n Hosting in 2026
n8n is a visual workflow-automation platform: you place nodes on a canvas, connect them into a graph, and automate multi-step processes across the tools your business already uses — sending a new lead to the CRM, syncing orders to a spreadsheet, or notifying a channel when a payment fails. It can run as a managed cloud service or on your own server, and the choice between those two shapes everything else: cost, control, maintenance, and what happens when a workflow fails at 2 a.m.
This guide explains the options as they stand in late 2026, so you can choose on evidence rather than on the word “free”.
n8n is fair-code, not open source in the OSI sense. Its own documentation says so plainly: “we do not call ourselves open source.” The self-hosted Community Edition is distributed under the Sustainable Use License, which allows use and modification for your own internal business purposes or for non-commercial or personal use.
In practice, that means:
Code in files or folders marked .ee is covered by a separate Enterprise licence and is not usable without a paid key. Before you build a client-facing service on a self-hosted instance, check the licence with n8n’s licensing team. The free edition’s price is fine; it is the terms that rule that use out. Always confirm the current licence text at n8n’s official documentation before a production deployment — licences and plan boundaries change, and this guide is not legal advice.
n8n’s own hosted service. You sign up, build workflows, and n8n runs the infrastructure, applies updates, and handles availability. You pay per workflow execution, with plans that, as published in 2026, start at around €20 per month billed annually for the Starter tier (2,500 executions) and rise through Pro and Business tiers, with Enterprise quoted on request. Check n8n’s pricing page for the current figures before you budget — prices and execution allowances change, and this article does not set them.
Cloud is the right choice if you want automation without server work, your execution volume is predictable, and you do not need the Community Edition’s unlimited executions enough to justify running a server. Its limit is the execution allowance: when you exceed it, workflows stop until the allowance resets or you upgrade.
You run n8n on your own server — typically a VPS — under the Sustainable Use License. There is no licence fee and no execution quota: the Community Edition has no per-execution charge, so your cost is the server bill plus the time to run it. The catch is that you take on setup, updates, security and backups, and the Community Edition lacks some features that need a paid licence, such as SSO, projects, workflow and credential sharing, Git integration and environments. n8n itself recommends self-hosting only for expert users — take that seriously.
Self-hosting is the right choice if your execution volume is high or unpredictable, your workflows handle sensitive data you want to keep on your own server, or you need the control to integrate deeply with systems on your own network. It is the wrong choice if nobody will own the server.
n8n’s own published self-hosting requirements are modest — the software is not CPU-intensive — but production needs more than the minimum. n8n’s guidance is to prioritise RAM over CPU, and to use PostgreSQL rather than the default SQLite for production.
A sensible starting point for a real production instance, drawn from current self-hosting guides, is:
| Testing / personal | Small production | Busy production | |
|---|---|---|---|
| vCPU | 1–2 | 2 | 4+ |
| RAM | 2 GB | 4–8 GB | 8–16 GB |
| Storage | 20 GB SSD | 40–80 GB NVMe SSD | 100+ GB NVMe SSD |
| Database | SQLite | PostgreSQL 13–17 | PostgreSQL 13–17 |
| Reverse proxy + HTTPS | Optional | Required | Required |
Node.js 20.19 or later is required if you install n8n directly rather than through Docker; the Docker image bundles its dependencies. n8n’s own documentation now recommends Docker Compose for self-hosting, with a three-service layout — PostgreSQL, n8n, and a separate task-runner container — rather than the two-container setup older tutorials show. Confirm the current layout in n8n’s official deployment documentation at the time you deploy, because the recommended setup has changed before and may change again.
Set the encryption key (N8N_ENCRYPTION_KEY) explicitly before the first boot and back it up outside the server. If n8n generates one automatically and you later lose it, a restored database with a different key cannot decrypt any saved credential — every stored credential is effectively lost.
n8n supports a queue execution mode, in which worker processes handle executions and a main instance handles webhooks and triggers, with Redis as the queue broker. That mode is documented by n8n and described in third-party guides, and it is the path to higher throughput — but it adds real operational complexity: PostgreSQL, Redis, and, in current guides, S3-compatible storage for binary data, plus more to monitor and to fail.
[TO BE CONFIRMED: whether Offshore Hosting offers queue/worker configurations for n8n, what those configurations include, and on which plans.] Do not assume a VPS plan includes a managed queue setup unless the provider confirms it. For most small-business workloads — up to tens of thousands of executions a month — the regular single-instance mode is enough, and queue mode is a later step, not a starting point. If you do need it, plan it as a deliberate scaling project with monitoring, not as a checkbox at purchase time.
1. How many executions will you run? Count them, or estimate from the workflows you plan. Low, predictable volume favours Cloud; high or spiky volume favours self-hosting, because the Community Edition has no execution cap.
2. Who will run the server? Self-hosting needs someone who can deploy with Docker Compose, configure a reverse proxy and HTTPS, apply updates, monitor the instance, and restore a backup. If that person does not exist, Cloud is cheaper than the outage that follows an unmaintained server.
3. How sensitive is the data? Workflows that move customer data, credentials, or internal systems benefit from staying on your own server, where you control access, logging and retention. That advantage only holds if the server is actually secured — see How to Deploy n8n Securely on a VPS.
4. Do you need the paid features? SSO, projects, sharing, Git and environments need a paid licence (self-hosted Business or Enterprise). If you need them, compare the paid self-hosted route with Cloud Business rather than assuming the free edition covers them.
5. What does failure cost? A workflow that sends a daily report can fail quietly for a day. A workflow that processes orders or payments cannot. The more a failure costs, the more you should invest in monitoring, backups and a tested restore — whichever hosting option you choose.
| Situation | Usually the better fit |
|---|---|
| A few workflows, low volume, no server skills in-house | n8n Cloud |
| High or unpredictable volume, data must stay on your server | Self-hosted Community Edition on a VPS |
| Need SSO, projects, or Git/environments | Paid n8n plan (Cloud Business or self-hosted Business/Enterprise) — check current pricing |
| Building a client-facing automation service | Commercial agreement with n8n — do not use the Community Edition for this |
| Testing n8n for the first time | Self-hosted test instance or a Cloud trial, with no real credentials |
n8n hosting is a trade, not a trick: Cloud trades money for freedom from maintenance and caps your executions; self-hosting trades maintenance for unlimited executions and full control of your data, under a fair-code licence that allows internal use but not reselling the service. Count your executions, be honest about who will run the server, and check the current licence and pricing on n8n’s official pages before you commit. The cheapest option is the one you can actually keep running.
For a VPS to self-host n8n on, see our VPS hosting plans. [TO BE CONFIRMED: Offshore Hosting VPS specifications for n8n, and whether any managed n8n or queue/worker offering exists.]
Email on your own domain looks professional and stays yours when you change providers. This guide explains what business email hosting involves, how it differs from free webmail, and the DNS and deliverability pieces that make it work.
Latency figures are widely quoted and widely misunderstood. This guide explains what ping measures, which hop actually matters, and the limits of what a VPS can do.
Webhooks, queue mode, and execution retention decide whether n8n stays fast or slowly fills its database. This guide explains each one and the settings that matter.