Self-hosting n8n is the right call when you've got server skills on the team, real execution volume, or a hard requirement to keep data on your own infrastructure. If you're a capable no-code operator with no spare time for server maintenance, n8n Cloud is the better buy, even at the higher price.
Should you self-host n8n? The short answer
n8n's hosting docs boil it down to two paths: self-host the free Community Edition on a server you control, or use n8n Cloud, where n8n runs and maintains everything for a fee. One thing to get straight before anything else: “free” means no license fee. It does not mean no cost.
Self-host (Community Edition)
Best for server skills, high volume, or specific infrastructure and data needs
- No license fee (n8n docs, September 2026)
- Full control over deployment and configuration
- You own setup, updates, SSL, database and backups
- No backup or disaster-recovery guide published by n8n
- Nobody else on call when it breaks
n8n Cloud
Best for no ops-time budget, modest volume, someone else on call
- Fully managed, no setup or maintenance required
- Backups, updates, uptime and security absorbed by n8n
- Data stored in the EU, Frankfurt, Germany (September 2026)
- Costs from 20 EUR/mo annual, Starter (n8n.io/pricing, September 2026)
- Execution ceiling per tier: 2,500 to 40,000 per month (September 2026)
What self-hosting n8n actually means (and what you become responsible for)
Self-hosting the Community Edition means you own setup, updates, the database and its backups, the reverse proxy (the software that routes traffic to your app, usually handling encryption), and SSL (the certificate that lets your instance load securely instead of throwing a browser warning). In practice, that means Docker (packaging an app so it runs the same way on any machine) running on a VPS, a rented slice of server you fully control. All of it.
n8n's own hosting docs don't dress this up. Self-hosting “requires setup (npm, Docker, or server)” and technical expertise “required for installation and configuration.” Maintenance is “your responsibility”; you “must provide and manage infrastructure.” Cloud, by contrast, is “fully managed, no setup or maintenance required.” One practical note: npm install is deprecated from n8n 3.0, so Docker Compose is now the supported path.
It's a trade. You get control and skip the license fee. In exchange, you become the person on call when something breaks.
The real cost of self-hosting (it is not free)
The license is free. The bill is not. Running the Community Edition yourself means a VPS bill (the amount depends on your setup, and you should distrust any round number from someone who won't name their config) plus your own time: setup, updates, monitoring, backups, recovery. For an operator whose calendar is already full, that's a real cost. It just never shows up on an invoice.
n8n Cloud flips the trade. One flat fee, and n8n absorbs maintenance, updates, uptime, and security. Pricing runs from 20 EUR/mo annual for Starter (2,500 executions/mo), up to roughly 50 EUR/mo for Pro (10,000 executions) and 667 EUR/mo for Business (40,000 executions); month-to-month costs more, per n8n's pricing page, accessed September 2026. That's an executions-based bill, one specific billing model among several automation tools use; how tasks, operations, and credits pricing actually compare is worth knowing before you commit to a tier.
The decision lever is volume, full stop. At low execution counts, Cloud's convenience beats whatever the license-free edition would “save” you, because there's no fee to save, only your time. That calculus shifts once your volume climbs high enough for Cloud's tiers to start biting, though self-hosting doesn't make limits vanish either. It just moves them somewhere you have to watch yourself.
When self-hosting silently breaks (the reliability and security reality)
For a moderately used app we very quickly burned through their ‘executions’ that were allotted by our license... even their highest enterprise license was cutting it close, and if you ‘run out’ of these executions, the service just stops working.
That's a Hacker News commenter from October 2025, describing a team that self-hosted n8n as a full backend, still hit an execution ceiling, and ended up owning the entire infrastructure stack anyway: load balancers, a key-value store, the database, failovers, backups. It's the clearest evidence for the whole point of this article. The free version has a salary attached. And paying that salary doesn't even guarantee you dodge the limits Cloud users complain about too.
Here's what quietly breaks, in plain terms. n8n's docs publish zero backup or disaster-recovery guide anywhere in their documentation index, so recovery is entirely on you. The default database is SQLite, and n8n's own docs say running queue mode (a separate worker process pulling jobs off a queue instead of one process handling everything) with SQLite “isn't recommended.” Queue mode needs a Redis broker alongside your database, usually Postgres at scale, and n8n warns that low worker concurrency “can exhaust your database's connection pool, leading to processing delays and failures.”
Real self-hosters back this up. On the n8n community forum, one operator without in-house server capacity named the worry precisely: “uptime and maintenance,” not setup. Another said they run their instance on a Digital Ocean VPS and “have cloudflare take care of the security,” which is itself one more service you have to configure correctly. A Stack Overflow thread shows what “breaks” often looks like in practice: a container couldn't reach the host, fixed with ordinary Docker networking knowledge, not an n8n bug.
To be fair, a well-configured self-host is reliable. The catch is that “well-configured and maintained” isn't a one-time task, it's an ongoing job description. And when it silently stops, there's no one else on call at 2am. The guide on fixing AI agent automations that keep breaking covers the reliability side in more depth. (Honest breakdowns like this one land in the newslettertoo, if that's useful.)
When self-hosting is the right call
Self-hosting genuinely wins in a few documented situations, and it's worth being just as straight about that. n8n's docs put it plainly: if you “need full control over deployment” or “have customized use cases,” you get “full control over deployment and configuration.” If you already “have infrastructure and technical resources,” you can “manage your own deployment” without paying a Cloud premium for it.
One nuance worth flagging against the reflexive “self-host for data control” argument: n8n Cloud data is stored within the EU, in Frankfurt, Germany. If your compliance need is simply “keep data in the EU,” Cloud already covers that. Self-hosting only becomes necessary if you need a specific facility, or need to stay fully outside n8n's infrastructure altogether.
Real self-hosters back the case, too. Hacker News users describe stable, multi-year setups with “a gazillion integrations.” On the n8n community forum, one operator put it honestly: go self-hosted “if the knowledge and time is there,” and “certainly if security at scale is a top priority.”
There's also a middle path. Managed n8n hosts like Northflank, Railway, and Hostinger run the infrastructure for you, priced somewhere between Cloud and full DIY. Treat their specific cost claims as vendor marketing, they would say that, but as a category it's a genuinely real option.
When you should skip self-hosting
This is the section the SERP can't write. Every top result is a self-host tutorial, an n8n doc, or a managed-hosting funnel with an incentive to say yes. None of them can tell you to just pay for Cloud. So here's the honest rule: skip self-hosting and pay for Cloud if you don't have, and don't want to build, server-admin time; if you have no plan for backups (n8n doesn't publish one for you, remember); if your data isn't specially sensitive; and if your volume is modest. Tick those boxes, and whatever the Community Edition “saves” on license cost gets eaten by your own time and the risk of a failure you can't recover from.
There's an even harder truth n8n's own content can't say: if your task is fully predictable and rule-based, you may not need n8n at all. A plain Zapier or Make automation can be cheaper and lower-maintenance than any n8n hosting choice, self-hosted or Cloud. Not sure n8n is even the right platform for what you're doing? The comparison against Make covers that fork directly.
Self-host vs n8n Cloud: the decision grid
| Dimension | Self-host (Community Edition) | n8n Cloud |
|---|---|---|
| License cost | Free, “almost the complete feature set” (n8n docs, Sept 2026) | From 20 EUR/mo annual, Starter, 2,500 executions/mo; month-to-month costs more (n8n.io/pricing, Sept 2026) |
| Real all-in monthly cost | VPS bill (not published, varies) plus your time: setup, updates, backups, recovery | Flat fee only; n8n absorbs hosting, updates, scaling |
| Setup & maintenance | Docker Compose setup; ongoing updates and infra are your responsibility | No setup; n8n handles maintenance |
| Backups & recovery | Entirely on you; n8n publishes no backup or recovery guide | Handled by n8n |
| Scaling | You run and tune Redis for queue mode; low concurrency can exhaust the DB connection pool | Managed; ceilings by plan tier |
| Execution limits | Not published; don't assume unlimited | Starter 2,500/mo, Pro 10,000/mo, Business 40,000/mo (Sept 2026) |
| Data control / residency | Full control; data lives wherever you host it | Stored in the EU, Frankfurt, Germany (Sept 2026) |
| Best-fit reader | Server skills, high volume, or specific infra/data needs | No ops-time budget, modest volume, someone else on call |
Every price above is sourced to n8n's own pricing and docs pages, accessed September 2026.
How to decide for your situation
Self-host if:you or a teammate already manage servers; your volume makes Cloud's tiered pricing expensive; your data must live on specific infrastructure; or you need environment control Cloud doesn't expose.
Use n8n Cloud if:you have no dedicated ops time; your volume is modest; you want someone else answering the 2am page; or you have no backup plan and aren't building one this quarter.
There's one legitimate “it depends” here, and it's a real pattern, not a hedge: a team with an ops person already managing other servers, where self-hosting adds almost no new burden and the savings are genuine. Outside that specific case, default to whichever side matches your actual available time. Not your aspirational one.
Frequently asked questions
Is self-hosting n8n a good idea? It depends on whether you have server-admin time and a backup plan, not on whether you could technically handle the setup. Have both, and self-hosting is legitimate at no license cost. Missing either one, n8n Cloud is the safer choice once you count your own time.
What is the best way to host n8n? For non-sysadmin operators, n8n Cloud. Fully managed, no setup required. For teams with server skills, Docker Compose is the recommended self-host method (npm install was deprecated from n8n 3.0).
Is it hard to self-host n8n?Initial setup isn't hard if you're comfortable with a terminal. What's hard is everything after: keeping the database, backups, SSL, and queue mode running correctly for months, with no backup guide from n8n to lean on.
Is self-hosting n8n actually free?No. The license is free, but you carry the VPS bill and your own time. Paid self-hosted tiers add another tether too: a license key that must ping n8n's server daily, with telemetry on by default unless you disable it.
n8n self-hosted vs cloud: which should you pick? Self-host for server skills, real volume, or specific data needs. Pick Cloud for a flat fee and someone else on call (see the grid above).
What are the requirements to self-host n8n?n8n doesn't publish a RAM or CPU minimum. You need a server you control, Docker or Node, a database (SQLite by default, Postgres at scale), and Redis for queue mode.
How much does self-hosting n8n save vs n8n Cloud?No verified figure exists. Treat any “70% savings” claim you see elsewhere as unattributed marketing math. The honest framing: a flat Cloud fee with a hard ceiling, versus a VPS bill plus your own time, which only wins once volume and skills actually justify it.
When should you skip self-hosting and just use n8n Cloud (or a plain Zap)? When you have no server-admin time, no backup plan, no sensitive data, and modest volume. And if the task is fully predictable, a plain Zapier or Make automation can beat any n8n setup on cost anyway.
Still deciding whether n8n is even the right platform for you? The guide on choosing an AI agent tool covers platform fit. Our newsletter covers one honest verdict like this a week. No pitch.