n8n Pricing Guide: Understanding Self-Hosted vs Cloud Costs (2026)

n8n Pricing Guide: Understanding Self-Hosted vs Cloud Costs (2026)

If you are comparing n8n cloud with self-hosted n8n, the short version is simple. Self-hosting starts cheapest because Community Edition is free, but your real cost includes hosting, maintenance, upgrades, monitoring, backups, and time. n8n Cloud costs more upfront, but it removes a lot of operational work.

For most solo builders and small teams, n8n Cloud is the faster path to production. For technical teams with infrastructure experience, compliance needs, or heavy workflow volume, self-hosted can be the better long-term choice.

What does n8n cost in 2026?

As of 10 April 2026, n8n prices usage around workflow executions rather than step counts, and all paid plans include unlimited users and workflows. On the public pricing page, Starter is listed at **£20/month billed annually** for **2.5K workflow executions**, Business is listed at **£581/month billed annually** for **40K executions**, Pro is shown as **£50/month billed annually** with a custom number of workflow executions, and Enterprise is **contact sales** with custom executions.

The important catch is that the cheapest visible number is not always the real operating cost. If you self-host Community Edition, the software license can be free, but the stack around it is not. If you choose cloud, the subscription is explicit, but maintenance is mostly abstracted away.

n8n also introduced a self-hosted Business plan to close the gap between free Community Edition and Enterprise. That matters if you want self-hosting plus features like SSO, LDAP, environments, Git-based version control, and better scaling controls.

Is n8n free or paid?

n8n is both free and paid. The free option is the self-hosted Community Edition, while paid options cover n8n Cloud plans and higher-tier self-hosted business features.

This is where a lot of buyers get confused. When people say “n8n is free,” they usually mean the open-source, self-hosted Community Edition available via GitHub and the docs. That edition lets you run n8n on your own server, Docker host, or VPS without paying a subscription for the core software.

But free does not mean zero-cost in practice. Even a lean self-hosted setup usually includes some combination of VPS fees, database/storage costs, log retention, secrets handling, backups, and engineering time. If your workflows are business-critical, you also need a plan for uptime, patching, observability, and incident response.

The paid side is cleaner to reason about. You pay n8n directly, get hosted infrastructure, and use execution-based limits rather than node-by-node billing. For teams trying to launch quickly, that predictability is often worth the subscription.

Should you choose n8n self-hosted or cloud?

Choose self-hosted if you want maximum control and have the technical ability to run it well. Choose cloud if your priority is shipping workflows quickly with less operational overhead.

Self-hosted n8n makes sense when you care about infrastructure ownership, custom networking, data residency, or integrating n8n into an existing platform stack. It is also attractive if you already run Docker infrastructure and treat automation as another internal service.

Cloud makes more sense when you do not want to own the platform layer. Teams evaluating automation rarely fail because the workflows are conceptually hard. They fail because setup, maintenance, and debugging keep getting delayed behind everything else. Cloud reduces that friction.

There is also a middle layer that buyers miss. You can self-host n8n, keep control of the instance, and still use tooling on top to move faster. That is where Synta fits. Instead of manually wiring every node, Synta builds n8n workflows from plain English, which is especially useful when you want the flexibility of self-hosted n8n without eating the full time cost of hand-building each automation.

What are you really paying for with n8n cloud cost?

You are not only paying for execution capacity. You are paying to avoid platform work: hosting, upgrades, concurrency management, reliability work, and part of the debugging surface.

That matters because “n8n cloud cost” is usually evaluated too narrowly. Buyers compare a visible subscription line item against a cheap VPS and conclude self-hosting wins. Sometimes it does. But the comparison gets distorted if you ignore time.

A realistic n8n cloud cost evaluation should include:

• subscription price

• expected workflow executions

• number of teammates touching the instance

• cost of downtime or broken automations

• cost of maintaining Docker, reverse proxy, TLS, backups, and upgrades

• time spent debugging workflows and failed runs

For a solo developer automating internal tasks, self-hosted may still be dramatically cheaper. For a startup founder or automation lead trying to get five cross-functional workflows live this week, the opportunity cost flips fast.

How does n8n self-hosted pricing work?

At the Community Edition level, self-hosted pricing starts at free software plus your own infrastructure. At the business tier, self-hosted pricing becomes a commercial plan tied to executions and advanced features.

The new pricing model matters here. n8n’s public pricing page says the self-hosted Business plan is **£581/month billed annually** and includes **40K workflow executions with unlimited steps**, plus SSO/SAML/LDAP, environments, scaling options, Git-based version control, 30 days of insights, and six shared projects.

That puts self-hosted into two very different buying motions:

1. **Community Edition** for technical operators who mainly want the engine and can run it themselves.

2. **Business self-hosted** for teams who need governance, collaboration, security, and scale without moving to full Enterprise.

So when someone searches for “n8n self hosted vs cloud,” the answer is not binary. There is free self-hosted, paid self-hosted, and hosted cloud. Each solves a different operational problem.

When does self-hosted n8n make the most sense?

Self-hosted n8n is strongest when control is a requirement, not just a preference. It works best for teams that already know how they will run, secure, and support the platform.

A good self-hosted fit usually looks like this:

• you already run Docker or Kubernetes workloads reliably

• you need private networking or stricter data handling

• you want direct control over updates and deployment windows

• you have internal engineering capacity for maintenance

• you expect workflow volume or complexity that benefits from owning the stack

It is also a good fit if you want to pair n8n with a builder layer that reduces manual work. For example, you can use the Synta MCP installation guide to connect your self-hosted n8n instance to an AI workflow builder, then use the Synta best practices docs to generate and refine workflows faster.

The key is honesty about team capacity. Self-hosting is powerful, but it is not magically cheaper if no one owns the system.

When is n8n Cloud the better buy?

n8n Cloud is usually the better buy when speed, simplicity, and lower maintenance matter more than infrastructure control. It is the default recommendation for teams that want automation outcomes, not another platform to maintain.

Cloud is often the right choice when:

• you want to launch workflows this week, not after infra setup

• your team does not have a dedicated owner for the instance

• reliability matters, but custom hosting does not

• you want predictable plan boundaries tied to executions

• you are still learning where automation will create the most value

There is also less hidden decision load. You do not need to choose deployment topology, backup strategies, update cadence, queue architecture, or hosting vendor before you even know whether the workflows will stick.

For early-stage teams, this simplicity compounds. The first question should be “what workflows should we automate?” not “how should we operate an automation platform?”

What about n8n enterprise pricing?

n8n enterprise pricing is custom, so you should expect a sales process rather than a posted number. It is designed for teams that need strict governance, larger execution volumes, advanced security, and dedicated support.

On the current pricing page, Enterprise is listed as contact sales, available as hosted by n8n or self-hosted, with custom workflow executions. n8n also says Enterprise includes everything in Business plus unlimited shared projects, 200+ concurrent executions, 365 days of insights, external secret store integration, log streaming, extended data retention, dedicated support with SLA, and invoice billing.

If you need an exact price, mark that as **[VERIFY PRICING]** because n8n does not publish a standard Enterprise list price publicly. In practice, buyers usually move to Enterprise when procurement, security review, or internal governance matters more than the plan sticker.

How should developers and founders evaluate n8n free vs paid?

Start with the cost of a working outcome, not the cost of the software line item. “Free vs paid” is useful only if you also count time, risk, and maintenance.

A practical evaluation framework looks like this:

• If you are a developer experimenting alone, start with Community Edition.

• If you are a founder validating automations fast, cloud usually wins.

• If you are an automation lead with internal infra standards, self-hosted can be the right long-term path.

• If compliance, SSO, auditability, or scale are required, evaluate Business or Enterprise.

Then ask a second question: how much of the workflow-building work do you want to do manually? If the answer is “as little as possible,” Synta is the AI layer on top of n8n that cuts build time without locking you out of standard n8n JSON.

Skip the setup - Synta builds n8n workflows from plain English

What is the smartest setup for most teams?

For most teams, the smartest setup is the one that reduces both infrastructure drag and workflow-building drag. That usually means either n8n Cloud alone, or self-hosted n8n paired with a workflow builder layer.

If you want the simplest route, choose n8n Cloud and get live fast. If you want the control of Docker or VPS deployment, self-host n8n and use Synta to reduce manual build complexity. That combination lets you keep ownership while avoiding a lot of repetitive node-level work.

The important thing is not to treat pricing as a pure subscription comparison. n8n pricing is really a tradeoff between cash cost, engineering time, governance requirements, and speed to value.

FAQ

Is n8n Community Edition really free?

Yes, the self-hosted Community Edition is free to run, but your hosting and maintenance costs are still real.

What is the current n8n Starter price?

As of 10 April 2026, the public pricing page shows Starter at **£20/month billed annually** for **2.5K workflow executions**. If you need monthly billing or regional pricing, **[VERIFY PRICING]** against the live page before publishing.

Is n8n Pro or Business better for a growing team?

If you want hosted simplicity, Pro is the natural next step. If you need self-hosting plus SSO, environments, Git version control, and scaling controls, Business is the stronger fit.

Does n8n charge per step like other automation tools?

No. n8n says pricing is based on workflow executions, regardless of workflow complexity, rather than charging per step.

Can I use Synta with both n8n cloud and self-hosted n8n?

Yes. Synta can sit on top of either setup. If you want the setup details, start with the installation docs and then the rules docs.