Updated October 2026
n8n is one of the most popular workflow automation tools in the world, but before you build your first workflow you have to answer one question: where will n8n run? The hosting choice decides how much you pay, how many executions you get, who maintains the server, and who controls your data.
This guide compares every realistic way to host n8n in 2026 (n8n Cloud, managed n8n hosting, and self-hosting) with real prices, server sizes and a production checklist, so you can pick the right option in a few minutes.
Quick answer
- Want zero maintenance and are happy with execution limits? Use n8n Cloud (from 20 €/month billed annually for 2,500 executions).
- Want unlimited executions without managing servers? Use managed n8n hosting, for example n8nhost.io from $4.99/month with a 14-day free trial.
- Have DevOps skills and need full control? Self-host n8n with Docker Compose, PostgreSQL and a reverse proxy. Read our n8n self-hosted guide.
What is n8n hosting?
n8n is a workflow automation platform that connects apps, APIs, databases and AI models with a visual editor. “n8n hosting” simply means the server where your n8n instance runs. That server needs to:
- run the n8n application 24/7 so scheduled workflows and webhooks always fire,
- store workflows, credentials and execution history in a database (PostgreSQL for production),
- be reachable over HTTPS so external services can call your webhooks,
- be backed up, monitored and updated regularly.
Who takes care of those four jobs is the real difference between the hosting options below.
The 3 ways to host n8n
1. n8n Cloud (official SaaS)
n8n Cloud is run by n8n GmbH. You sign up, and the n8n team handles servers, updates and backups. It is the simplest option, but every plan is limited by a monthly number of executions (one execution = one full run of a workflow) and by concurrent executions.
2. Managed n8n hosting
A managed provider gives you your own n8n instance and handles the infrastructure for you: server, SSL, updates, backups and monitoring. You still get the self-hosted Community Edition, so there is typically no execution limit, and you can install community nodes. This is the middle ground between convenience and control. n8nhost.io is a managed n8n hosting platform built specifically for this.
3. Self-hosted n8n
You rent a server (VPS, cloud VM or Kubernetes) and install n8n yourself, usually with Docker Compose. The software is free, executions are unlimited and you control everything, but you are also responsible for security, updates, backups, scaling and fixing things at 3 a.m. when a webhook stops responding.
n8n hosting comparison table
| n8n Cloud | Managed n8n hosting | Self-hosted | |
|---|---|---|---|
| Starting price | 20 €/mo (annual) | From $4.99/mo (n8nhost) | Server cost (~5–40 €/mo) + your time |
| Executions | 2,500–40,000/mo by plan | Usually unlimited | Unlimited |
| Setup time | Minutes | Minutes | Hours to days |
| Updates & backups | Included | Included | You do it |
| Security hardening | Included | Included | You do it |
| Community nodes | Limited to verified nodes | Yes | Yes |
| Data location control | n8n’s cloud | Provider’s servers | Full control |
| Best for | Low-volume teams who want official SaaS | Freelancers, agencies, startups, growing teams | Teams with DevOps skills or strict compliance |
How much does n8n hosting cost?
n8n Cloud prices
As of October 2026, n8n’s official pricing page lists these plans (prices billed annually, in euros):
| Plan | Price | Executions / month | Concurrent executions |
|---|---|---|---|
| Starter | 20 €/mo | 2,500 | 5 |
| Pro | 50 €/mo | 10,000 | 20 (up to 50) |
| Business | 667 €/mo | 40,000 | Higher |
| Enterprise | Custom | Custom | 200+ |
Monthly billing costs more than annual billing, and prices change, so always confirm on n8n.io/pricing. For a full cost breakdown with real examples, see our n8n pricing guide.
The execution trap
Execution limits sound generous until you do the math. A workflow that polls an API every 5 minutes uses about 8,640 executions per month on its own. That single workflow already exceeds the Starter plan and uses most of the Pro plan. Webhooks from a busy form, a CRM or a Telegram bot can burn through thousands of executions in days. This is the main reason teams move from n8n Cloud to managed or self-hosted n8n, where executions are not counted.
Self-hosting: the hidden costs
The n8n Community Edition is free, and a capable VPS costs roughly 5–40 € per month. The real cost is time:
- initial setup (Docker, PostgreSQL, reverse proxy, SSL, firewall): several hours,
- updates every few weeks, including testing that nothing broke,
- backups of the database and the encryption key,
- monitoring, disk cleanup and troubleshooting failed executions.
If your time is worth 40 €/hour, just two hours of maintenance per month makes self-hosting more expensive than most managed plans.
Which n8n hosting option should you choose?
| If you are… | Choose | Why |
|---|---|---|
| A beginner testing n8n | Managed hosting trial or n8n Cloud trial | No setup, start building today |
| A freelancer or agency running client automations | Managed n8n hosting | Unlimited executions keep costs predictable as clients grow |
| A startup with a few high-volume workflows | Managed n8n hosting | No execution math, no server work |
| A team with DevOps engineers | Self-hosted | Full control over versions, scaling and networking |
| An enterprise with strict data residency rules | Self-hosted or n8n Enterprise | Data stays in your own infrastructure |
What server size does n8n need?
n8n itself is light. What consumes resources is the number of workflows running at the same time, large data payloads, and Code nodes. Use this as a starting point:
| Workload | vCPU | RAM | Setup |
|---|---|---|---|
| Personal / testing (a few workflows) | 1 | 2 GB | Single container, PostgreSQL |
| Small team (dozens of active workflows) | 2 | 4 GB | PostgreSQL, task runners |
| Busy production (many webhooks, AI workflows) | 4+ | 8 GB+ | Queue mode: Redis + workers |
If executions start queuing up or the editor feels slow, scale out with queue mode instead of only buying a bigger server.
Recommended production architecture
Whether a provider runs it for you or you run it yourself, a reliable n8n setup in 2026 looks like this:
- PostgreSQL instead of SQLite. SQLite is fine for testing, but PostgreSQL handles concurrent executions and large histories far better, and distributed setups require it.
- Queue mode (
EXECUTIONS_MODE=queue) with Redis and one or more workers, so heavy workflows do not slow down the editor or webhooks. - External task runners (the
n8nio/runnersimage) so JavaScript and Python Code nodes run in an isolated sidecar container. The runners image version must match your n8n version. - A reverse proxy with HTTPS (Traefik, Caddy or Nginx) in front of n8n. Never expose port 5678 directly to the internet.
- A correct public URL so webhooks show your real domain:
N8N_WEBHOOK_URLfrom n8n 2.30, orWEBHOOK_URLon older versions. - A safely stored
N8N_ENCRYPTION_KEY. Every credential in n8n is encrypted with it. If you lose it, your saved credentials cannot be decrypted, even with a perfect database backup.
n8n hosting security checklist
- Serve n8n only over HTTPS through a reverse proxy.
- Enable two-factor authentication for every n8n user.
- Keep n8n updated; security fixes ship regularly.
- Block access to environment variables from Code nodes (
N8N_BLOCK_ENV_ACCESS_IN_NODE=true). - Protect production webhooks with header authentication or a secret token.
- Back up the database and the encryption key daily, and test a restore.
- Only install community nodes you trust; they run code inside your instance.
- Restrict SSH and database ports with a firewall.
Performance tips
- Prune old execution data, or your database will grow without limit.
- Avoid saving full execution data for high-volume, successful runs.
- Split very large workflows into sub-workflows and process items in batches.
- Use queue mode and add workers when many workflows run at the same time.
- Keep the server in a region close to the APIs your workflows call most.
Moving between hosting options
You are not locked in. You can move from n8n Cloud or a self-hosted server to managed hosting (or back) by exporting your workflows and credentials. The one rule: credentials can only be decrypted with the same encryption key, so either migrate the key with the database, or export credentials decrypted and re-import them on the new instance.
Why teams choose n8nhost.io
n8nhost.io is managed hosting built only for n8n:
- your own n8n instance, ready in minutes,
- unlimited workflows and executions,
- SSL, CDN and a fast server included,
- Community Edition with free registered enterprise features and community nodes,
- plans from $4.99/month with a 14-day free trial.
See plans and start your free trial →
Frequently asked questions
Can I host n8n for free?
The self-hosted Community Edition is free, but you still pay for a server, and you do all the maintenance yourself. Free cloud tiers on general hosting platforms usually sleep or restart, which breaks schedules and webhooks.
Is n8n Cloud or self-hosted better?
n8n Cloud is better if you want zero maintenance and your execution volume is low. Self-hosted or managed hosting is better when you run many workflows, need community nodes, or want predictable costs without execution limits.
What database should I use for n8n?
PostgreSQL for anything beyond testing. SQLite is the default for quick local setups, but it is not suited to queue mode or high concurrency.
How many executions do I need?
Count each trigger: a workflow that runs every 5 minutes uses about 8,640 executions per month, every 15 minutes about 2,880, and once an hour about 720. Add your expected webhook and form traffic on top.
Do I need queue mode?
Not for small setups. Use queue mode when many workflows run at the same time, when long workflows slow down the editor, or when you need to scale horizontally with multiple workers.
How do I keep n8n updated?
Pin a specific n8n version in Docker, read the release notes, back up, then update n8n and the task runner image together. On managed hosting, updates are handled for you.
Is managed n8n hosting secure?
A good provider isolates each instance, serves it only over HTTPS, keeps n8n patched and backs up your data daily. Ask any provider how they handle backups and encryption keys before you sign up.
Ready to stop managing servers? Start your 14-day free trial on n8nhost.io →
