n8n Cloud vs Self-Hosted (2026): Decision Guide With Real Costs

n8n self-hosted vs cloud comes down to volume and ownership: n8n Cloud is cheaper and simpler while your workflows fit Starter or Pro, and self-hosting the free Community Edition wins once you run well past 10,000 executions a month or need data on your own servers. The license is free either way you self-host; the real costs are the server and the chores that come with it.

Checked October 2026 on the n8n pricing page, n8n's Cloud or self-host guide, edition comparison, license FAQ, backup and update docs, the n8n help article on execution limits, and the DigitalOcean and Hostinger VPS pricing pages. n8n prices in euros, the VPS providers in US dollars.

This page used to be our step-by-step self-hosting tutorial. The setup now lives in the n8n Docker Compose setup guide, with Postgres, a queue worker, HTTPS and a backup job. This page answers the question you should settle first: whether to self-host at all. For what to build once you have decided, start at our n8n hub with workflow templates.

The decision in one picture

n8n's own docs are blunt about the top-right box: "n8n recommends self-hosting for expert users. Mistakes can lead to data loss, security issues, and downtime. If you aren't experienced at managing servers, n8n recommends n8n Cloud." Take that at face value.

n8n Cloud pricing vs self-hosted: total cost of ownership

Cloud prices from the n8n pricing page, with quotas from n8n's help center. VPS ranges are list prices for a renewal-priced Hostinger plan (KVM 1, 2 and 4, backups included) at the low end and a DigitalOcean Basic droplet (2, 4 and 8 GiB) with weekly backups at 20% at the high end. Upkeep hours are illustrative inputs, not measurements. Our self-hosted n8n pricing breakdown has the provider-by-provider sheet, including introductory prices and Railway's usage billing.

The quickest way to place yourself in that table is to count executions. Every schedule run, every webhook call and every chat turn counts; sub-workflows, error workflows and manual test runs do not. Our n8n pricing guide shows the method, and if you are comparing n8n against other tools entirely, n8n vs Zapier prices the same workflow stack on both.

What n8n Cloud gives you

• No server. n8n runs hosting, updates and infrastructure. Data is stored in the EU, in Frankfurt.
• Easy connections. For services such as Microsoft 365, Cloud users click Connect my account; self-hosted users register their own OAuth app.
• Assistant credits. 1,600 a month on Starter and 4,000 or 9,600 on Pro, depending on plan size. Self-hosted, Assistant runs on your own model key.
• A trial that costs nothing. Fourteen days with 1,000 executions, 5 concurrent runs and a 180-second execution timeout, no card required.

The limits are real, though. Each plan has a monthly execution quota and a concurrency cap, and when you hit the quota, new runs fail immediately with "Execution limit reached" rather than queuing. Quotas reset at the start of each calendar month, not on your billing date.

What self-hosting gives you

• No execution cap. The Community Edition has no quota; your server is the limit.
• Queue mode for free. n8n's edition comparison confirms queue mode is included, so you can add workers as volume grows. Multi-main, for high availability, needs a paid license.
• Data where you put it. Any provider, any region, or your own hardware.
• Your own nodes. Custom nodes you build yourself run on your instance; our custom nodes guide covers building them.

What it does not give you: the paid features. The edition comparison lists custom variables, environments, external secrets, external storage for binary data, log streaming, multi-main, projects, SSO, sharing and Git version control as missing from the free edition. Registering your instance by email unlocks folders, debug in editor and custom execution data for free. Anything else means a Business license at €667 a month billed annually, and n8n's pricing FAQ notes that a Business or Enterprise license key pings its license server daily with your production execution count.

Should I self-host n8n? The chores you are signing up for

Cost posts list the server. They rarely list the work. This is the part people underestimate, drawn from n8n's own update and backup docs:

Two of these deserve a note. The n8n 3.0 release, per n8n's breaking-changes page, ends support for installs run with npm or npx n8n, so self-hosted n8n means Docker from now on; our n8n 3.0 upgrade guide groups every change by who it affects. And error alerts are the cheapest insurance you can buy: our n8n error handling guide shows how to wire an error workflow in ten minutes.

For teams: the sharing gap in the free edition

One limit changes the answer for teams more than any price does. In the free Community Edition, n8n's edition comparison says only the instance owner and the user who creates a workflow or credential can access it: there is no workflow sharing, no credential sharing and no projects. That is fine for a solo builder or a single operations lead. It is awkward for three people maintaining the same client workflows, because each person sees only their own work.

So for a team of more than one active builder, the real comparison is usually Cloud Pro (shared projects, admin roles and workflow history included) against self-hosted Business at €667 a month billed annually plus a server, not against free. For a small team that gap is large, and it is why many teams that could self-host technically still pick Cloud.

What a production self-hosted setup has to include

If you do self-host, the bar for "production" is higher than a single container. n8n's docs set three expectations worth knowing before you budget time:

• Postgres, not SQLite. The Docker Compose guide calls SQLite fine for trying things out and recommends Postgres for an instance with more than a handful of users or workflows running around the clock. Switching later starts with an empty database, so choose on day one.
• External task runners. The task runner docs say runners are the only isolation layer between Code node scripts and your credentials, and to use external mode in production. That means an extra runner container next to n8n, and next to each worker if you use queue mode.
• HTTPS through a reverse proxy, with the webhook URL set. Behind a proxy, n8n needs N8N_WEBHOOK_URL and N8N_PROXY_HOPS set or webhook URLs come out wrong.

None of this is exotic, and the Docker Compose guide puts it all in one file. But it is why a production self-hosted instance is a small system to look after, not just an app you installed.

What the license allows on either option

Self-hosted n8n runs under the Sustainable Use License. n8n's license FAQ sums it up: if workflows are only created or modified by you or people in your organization, you can use it for free. You can run your business on it, build automations for clients on your instance as long as they cannot create or edit them, charge for setup and maintenance, and use n8n behind the scenes in your own product. You cannot host n8n as a service where clients build workflows, let end users configure workflows through your product, fork it into your own automation product, or white-label it. n8n Cloud is a paid subscription with its own terms.

When n8n Cloud is genuinely worth it

Many people do both in sequence: start on Cloud, learn what their real execution count is from the Insights dashboard, then move once the numbers justify a server. Moving is an export and import with the same encryption key, described in n8n's backup docs.

Next steps

Decided to self-host? Follow the Docker Compose setup guide, then build something on it: our n8n tutorial for beginners, the database automation and API integration guides cover the common first projects. If you would rather build your own AI product than run n8n for clients, AI SaaS Builder covers building it, deploying it and charging for it.

n8n Cloud vs self-hosted: FAQ