Stop Getting Billed Per Execution on the n8n Instance You Already Self-Host

Quick Answer

n8n's free self-hosted Community edition hasn't changed: it's still unlimited on executions and workflows, and you only pay for your own server. What's new is a self-hosted Business tier priced at roughly $800/month billed annually (around $960/month billed monthly) for about 40,000 executions, with overage running roughly $16 per 1,000 extra runs, sold in blocks of 300,000 for $4,800. If you don't need the features Business gates, nothing forces you onto this bill. If you do, you're now choosing between paying a metered price that scales with your traffic, throttling your execution count, or re-architecting your workflows so fewer runs carry more work.

Most agencies and ops teams that self-host n8n do it for one reason: Community edition is free and uncapped. No per-task meter, no execution ceiling, pay for your VPS and that's the whole bill. For a while that covered the entire story. If you wanted governance features on top of a self-hosted instance, SSO, Git-backed environments, role-based access across a team managing multiple client accounts, you either lived without them or went and negotiated an Enterprise contract.

That gap just got a new, metered middle rung. n8n now sells a self-hosted Business license, and it bills by execution the same way n8n Cloud does. If your team has outgrown what Community offers but isn't ready for a custom Enterprise deal, you're now looking at a bill that moves with your traffic instead of a flat license fee. This post covers what actually changed, does the math on what it costs at real volume, and lays out when paying it, throttling your execution count, or re-architecting your workflows is the right call.

What Actually Changed in n8n's Pricing

The free self-hosted Community edition is unchanged. It's still distributed under n8n's Sustainable Use License, still self-hostable on your own infrastructure with unlimited workflows, users, and executions. If you're running Community today for the automation engine itself and never touch SSO, LDAP, Git-based environments, or shared projects, this pricing shift doesn't reach you directly.

What's new is a self-hosted Business license. It sits between Community and Enterprise and unlocks the features agencies and multi-team ops shops actually ask for: SSO and LDAP, Git version control for workflows, multiple environments, and a handful of shared projects (six, as of this writing). n8n positions it at companies under roughly 100 employees.

The catch is how it's priced. Business runs roughly $800/month billed annually, or around $960/month billed monthly, for about 40,000 included executions. Go past that and n8n's published overage is $4,800 per extra block of 300,000 executions, which works out to roughly $16 per 1,000 additional runs if you only partially fill a block. That's a usage meter sitting on top of a self-hosted install you're still fully responsible for running, patching, and backing up yourself.

n8n also offers a startup discount: companies under 20 employees and under €5M raised get roughly 50% off the Business base, bringing the annual rate down to around €333/month (very roughly $350-400 USD depending on exchange rate). Worth checking before you assume the full sticker price applies to you.

Why This Lands Hardest on Agencies and High-Volume Ops Teams

The teams this actually affects share a specific profile: you're already self-hosting Community because the economics made sense, you're running enough workflows across enough clients or departments that "everyone shares one admin login" stopped being acceptable, and you need Git-backed deploys or SSO to pass a client's security review or your own IT policy. That's most agencies running n8n across multiple clients, and most ops teams past a certain headcount.

Before this tier existed, your real options if you needed those features on a self-hosted instance were: live without them, cobble together a workaround (a reverse proxy for auth, a CI pipeline for workflow JSON, separate instances per client to fake isolation), or go negotiate an Enterprise contract. Business gives you a packaged middle option, but it's the first self-hosted n8n tier priced per execution instead of as a flat license.

That distinction matters because agencies and ops teams are exactly the profile most likely to run high execution volume. A single mid-size e-commerce brand syncing orders, inventory, and support tickets can clear 50,000-100,000 executions a month once you count every polling check, every webhook, and every scheduled sync. An agency running that pattern across six or eight clients on one shared instance can clear that in a week.

Doing the Math on the Overage Rate

Here's what the published numbers work out to at a few realistic volumes, using n8n's own base price and overage rate. Treat these as estimates, not quotes: overage is sold in fixed blocks, so your actual invoice may round up to the next full block rather than prorate cleanly.

  • 40,000 executions/month: right at the included amount. Roughly $800/mo (annual) or $960/mo (monthly), no overage.
  • 100,000 executions/month: about 60,000 over the included amount. At roughly $16/1,000, that's close to $960 in overage, pushing the bill to somewhere around $1,760-$1,920/mo before any block-rounding.
  • 250,000 executions/month: about 210,000 over. Roughly $3,360 in overage, landing around $4,160-$4,320/mo total.
  • 500,000 executions/month: about 460,000 over. Roughly $7,360 in overage, landing around $8,160-$8,320/mo total.

For comparison, a Community instance running the exact same volume costs whatever your server bill is. A queue-mode deployment built to handle hundreds of thousands of executions a month typically runs somewhere in the $60-150/mo range for infrastructure, based on the deployment shapes most teams actually use. The jump from that to a four- or five-figure monthly license is the whole reason this pricing change is worth stopping and doing math on before you upgrade.

Where Paying for Business Actually Makes Sense

It's easy to read the math above and write Business off as a trap. It isn't, for the right team.

If SSO and Git-backed, audit-ready workflow history are things your compliance team or a client's security review genuinely requires, building an equivalent yourself on Community means engineering time, ongoing maintenance, and a security posture you're personally accountable for instead of a vendor. For a small team, that trade is often worse than the subscription.

If your real execution volume sits right around 30,000-40,000 a month and you need even one of the gated features, paying $800-960/mo is simpler than building and maintaining a workaround that saves you a few hundred dollars. The math only turns ugly once you're meaningfully over the included amount.

And if you qualify for the startup discount, the economics shift again. Roughly €333/month for SSO, Git environments, and shared projects is a reasonable price for a small agency that genuinely needs those features to win and retain clients.

Throttle or Re-Architect: Your Other Two Options

If you don't need the gated features badly enough to justify the bill, or your volume makes the overage math painful, you have two real alternatives short of paying full price.

Throttle your execution count. Widen polling intervals on integrations that don't need real-time updates (every 15 minutes instead of every minute cuts that trigger's volume by 15x). Merge multiple triggers that fire for the same underlying event into one. And audit for zombie workflows: most self-hosted instances we've looked at have a handful of workflows nobody has touched in months that are still running on a schedule, quietly burning executions for no one's benefit.

Re-architect around how n8n actually counts executions. According to n8n's own documentation, sub-workflow calls made through the Execute Workflow node don't count as separate billable runs. Only the top-level production execution is billed. That means restructuring a sprawl of small, single-purpose workflows (each with its own trigger) into fewer parent workflows that branch internally and call sub-workflows for the actual logic can cut your counted execution total significantly without cutting what the automation actually does. Batching records into a single run with an internal loop, instead of triggering once per record, works the same way.

Split your estate by need. Not every workflow needs Business features. A common pattern: keep client-facing or compliance-relevant workflows on a licensed Business instance, and run high-volume internal plumbing, the stuff nobody outside your team ever audits, on a separate free Community install. You pay the metered price only for what genuinely needs it.

A Simple Framework for Deciding

Work through these in order:

  1. Do you actually need SSO, Git-based environments, or RBAC right now, or is it nice-to-have? If it's nice-to-have, stay on Community. Nothing about this pricing change requires you to move.
  2. What's your real monthly execution count across every workflow? Pull it from your instance's execution history before estimating anything. Most teams guess low.
  3. If you need Business features and your volume is near or under 40,000/month, the base price is probably simpler than re-architecting around it.
  4. If you're well over 40,000 and need those features, model the overage cost against the engineering time it would take to consolidate workflows and cut your counted executions. A day or two of consolidation work often pays for itself in avoided overage within the first month.
  5. Check whether you qualify for the startup discount before assuming the full sticker price applies.

There's no universally right answer here, but there is a right answer for your volume, your feature needs, and your tolerance for maintaining workarounds yourself. The math above should get you most of the way to it.

Not Sure What Your n8n Bill Should Actually Look Like?

We audit self-hosted n8n instances, model the real execution math against your workflows, and either harden your Community setup or help you decide if Business is worth it.

Book a Free Pricing Audit Call →

← Back to Blog