n8n self-hosted or cloud: what does it cost and which should you choose?

What do you pay for in n8n Cloud?

Workflow executions, regardless of complexity. One execution is one run of a workflow from trigger to end, whether it has three nodes or sixty. The n8n price list from September 2026, billed annually:

Plan	Monthly price	Executions a month	For whom
Starter	€20	2,500	first automations, one project
Pro	€50	10,000	solo builders and small teams with workflows in production
Business	€667	40,000	companies under 100 people, also on your own server
Enterprise	individual	custom	organisations with compliance requirements

Plans also differ in concurrent executions, shared projects and how long history is kept. Prices and thresholds change; the n8n pricing page is the source of truth.

A planning trap: a workflow that runs every minute is 43,000 executions a month, more than the Business plan holds, even if it does nothing 99% of the time. Frequent schedules and high-traffic webhooks push a company up a plan very quickly.

What does n8n on your own server cost?

The Community Edition has no licence fee and no execution limit. It costs what the server and maintenance time cost.

Server. An instance for a small company runs on a virtual machine for somewhere between ten and a few dozen euros a month, with Postgres alongside. The cost is fixed: the more automations, the lower the unit cost of each. At high volumes you enable queue mode, where the main instance receives triggers and separate worker processes run the workflows; it scales by adding workers, not by changing plans.

AI calls. The only variable cost, and it applies to both options. n8n does not charge for tokens; you pay the model provider for actual calls. A workflow without a model node costs nothing beyond the server. The myth that "n8n charges for tokens" blocks more teams than I would have expected.

Time. Version updates, backups, API key rotation, a security review of webhooks. A few hours a month if someone in the company knows how, or the cost of someone external.

What does the free Community Edition lack?

Almost all of n8n is in the free edition: the editor, every integration, Data Tables, queue mode, folders after email registration. What is missing are features for larger organisations:

• custom variables and environments (dev, staging, production),
• an external secrets store and external storage for binary data,
• log streaming and multi-main mode,
• projects, SSO login through SAML or LDAP,
• sharing workflows and credentials between users: without a licence, only the instance owner and the person who created them have access,
• Git version control.

For a team of a few people working on one instance these gaps rarely hurt. They start to hurt when you need projects with separate permissions or formal environments.

When does data have to stay inside the company?

When documents, personal data, invoices, salaries or customer data flow through workflows. On your own server the data never leaves the company's infrastructure, and the administrator knows exactly where it is.

Two features that help are available in the Community Edition:

• The "do not save" mode for executions. In workflow settings you can disable saving successful, failed and manual executions. Data passes through n8n, the workflow processes it, and after completion it is not in the database. The price: no debugging in that mode, so you switch it on after testing.
• Hosting in the European Union with a provider of your choice, with backups under your control.

n8n Cloud also runs in GDPR-compliant infrastructure, but for many companies the argument "the data is on our server" ends the conversation with legal faster than any processing agreement.

What needs maintaining on your own server?

Installation through Docker Compose is the recommended route and takes less time than reading this guide. Maintenance is four recurring tasks:

1. Updates. n8n releases new versions weekly, usually on Mondays. An update is an image swap and a restart, but read the changelog first, because API contract changes happen.
2. API keys. Updates add new permissions that old keys do not include, even though they look complete in the UI. The symptom is a 403 error for agents building workflows. Issue keys with an expiry and rotate them every 90 days.
3. Backups of the database and credentials, with a restore test, not just a copy.
4. Webhook and form security. A public webhook without authentication is an open door. Basic Auth on forms, a token header on integrations, no tokens hard-coded in nodes. n8n-mcp has an audit that points at such places.

Plus one habit: every production workflow gets an error workflow with a chat alert. Without it a process can keep failing for two weeks with nobody noticing.

What does a minimal installation on your own server look like?

The recommended route is Docker Compose: an n8n container, a Postgres container as the database, and a reverse proxy with an HTTPS certificate in front. In the configuration you set the public address n8n will use to generate webhook URLs, the time zone for schedules, and pin a specific image version instead of "latest", so that updates are a decision rather than an accident. The SQLite database n8n uses by default is fine for testing; in production, have Postgres from day one, because migrating later is painful.

At higher volumes you enable queue mode: the main instance handles triggers and webhooks, and separate worker processes run the workflows through a Redis queue. Scaling means adding workers. One limitation from the docs: in queue mode binary files cannot be kept on the filesystem; an S3-compatible store is required.

Three typical bills

Indicative figures as of September 2026; the server cost depends on the provider and the machine size.

Company	Cloud	Own server
A few workflows, about a thousand executions a month, no personal data	Starter, €20 a month, no maintenance	a server for around ten euros plus time for updates; not worth it if nobody wants to do it
A few dozen workflows, 15,000 executions, schedules every few minutes	Pro is not enough, Business at €667 a month	a server for a few dozen euros plus a few hours of maintenance a month; the annual difference runs into thousands of euros
Invoices, HR documents, customer data in workflows	possible, but the conversation with legal takes time	own server in the EU, "do not save" mode for executions, the decision is usually immediate

The point where your own server starts paying off financially sits around the Pro plan: once volume pushes a company to Business, the annual difference covers external maintenance with room to spare.

The most common self-hosting mistakes

From implementations and from n8n-mcp telemetry, which shows every week where agents working with instances trip up:

• A wrong instance address. 43% of agents' connection checks against the n8n API fail, three quarters of them because of an incorrect address or an unreachable network: an instance behind a proxy with a different path, without public access, or with the webhook address set to localhost.
• API keys with no expiry. After an n8n update an old key lacks the new permissions even though it looks complete; the symptom is a 403 error.
• Public forms and webhooks without authentication and tokens hard-coded in nodes. The n8n-mcp audit points at such places within seconds.
• No error workflow. Only 2% of workflows built by AI agents handle errors; on your own server nobody but you will notice a process has been failing for two weeks.
• Outdated models in workflows. Providers retire older model series; a workflow with a year-old model can stop working overnight. A quarterly review is part of maintenance.

How to choose: a decision tree

1. Do documents, personal data or customer data flow through the workflows? Yes: self-hosted.
2. Is the expected volume above 10,000 executions a month, or do you have workflows on a frequent schedule? Yes: self-hosted, with queue mode when it grows.
3. Can someone in the company spend a few hours a month on the server, or do you have someone external? No: cloud to start, migrate later, because workflows export as JSON.
4. Do you need projects, SSO and environments? Yes: a paid plan, in cloud or on your own server.

In the remaining cases cloud is an honest choice for the first months. Most companies I work with move to their own server the moment the first process with documents appears, or the first bill for executions.

What does an assisted implementation cost?

With me the first stage costs €1,000 to €2,000: self-hosted n8n on your server, backups, team access, error handling and one integration brought to production. Afterwards we both know whether we want to continue, and you have a running instance instead of a proposal covering ten processes.