n8n Pricing Explained: Is It Really Free? (2026)
On this page
A student messaged me last month with a screenshot of his Zapier bill. Four hundred and something dollars for the month. He runs a tiny automation side hustle, maybe five clients, and the tasks had crept up on him one Zap at a time until the invoice stopped being funny.
His next line was the reason I'm writing this. "Someone told me n8n is free. Is that actually true or is it one of those free that costs money?"
Good instinct. Because the honest answer is both.
The short version
n8n is free if you self-host it, and paid if you use n8n Cloud.
The core software is open source. You can download it, run it on your own server, and pay n8n nothing. No task limits, no per-step meter counting against you. That version is called the Community edition and it's genuinely free.
n8n Cloud is the hosted option. They run the servers, handle updates, keep it online, and you pay a monthly subscription for that convenience. There's a free trial so you can poke around before you commit.
So when people ask "is n8n free," the real question underneath is "free for who, and at what cost to my time." Self-hosting trades money for effort. Cloud trades effort for money. That's the whole decision, and most of this post is helping you figure out which trade fits your life right now.
The free part: self-hosted Community edition
Here's the thing that trips people up. n8n is source-available software, which means the code is out in the open and you're allowed to run it yourself for free. If you've ever installed WordPress on a server, it's the same mental model. The app costs nothing. You just need somewhere to put it.
That somewhere is the catch, and I'll be honest about it in a minute.
What you get on the self-hosted Community edition:
- The full visual workflow builder
- Hundreds of integrations and nodes
- Unlimited workflows and unlimited executions
- Your data sitting on your own infrastructure, which matters a lot if you handle client data or anything regulated
No task counter ticking in the corner. If you build a workflow that fires ten thousand times a day, that's between you and your server, not you and a billing page. For anyone doing high-volume automation, that single fact is the whole reason n8n exists.
Some of the fancier team features (advanced permissions, certain enterprise controls) live behind a paid license even on self-hosted. But the meat of the tool, the part 95% of people actually need, is free to run forever.
n8n Cloud: what you're paying for
If setting up a server sounds like a Saturday you'd rather not lose, n8n Cloud is the answer. They host it, you log in, you build. It's the closest thing to the Zapier experience while keeping n8n's flexibility.
Cloud runs on paid monthly plans, and this is where the pricing model gets interesting, because it's built differently from almost every competitor.
n8n Cloud bills by workflow executions, not by tasks or steps.
Sit with that for a second, because it's the single most important thing in this article.
On Zapier, every step in a workflow counts. A Zap that grabs a form entry, checks a condition, updates a spreadsheet, and sends a Slack message can burn three or four tasks in one run. Fire it a thousand times and you've spent three or four thousand tasks.
On n8n Cloud, that entire workflow running start to finish counts as one execution. Doesn't matter if it has four nodes or forty. One run, one execution.
For simple two-step automations, this difference barely shows up. For the meaty multi-step workflows that real businesses actually build, it's the difference between a bill that scales gently and one that mugs you. My student's Zapier invoice wasn't high because he had a lot of clients. It was high because each client's automation had a lot of steps.
As for actual dollar figures, n8n's cloud tiers and their names shift around, so I'm not going to quote you a number that's wrong by the time you read this. The structure to expect: a few tiers that step up on the number of executions you're allowed and how many active workflows you can run at once, with the entry plan starting somewhere in the low tens of dollars a month and a free trial before any of it. Check n8n.io for the current numbers, since that's the only place they're guaranteed to be right.
The true cost of self-hosting
I promised honesty, so here it is. Free is not the same as free.
When you self-host n8n, you're not paying n8n. You're paying in three other ways, and pretending otherwise is how people end up frustrated.
A server. n8n has to run somewhere. A small cloud box from a provider like DigitalOcean or Hetzner runs a few dollars a month, and a Raspberry Pi in your closet costs you electricity. Not scary money, but not zero.
Your time to set it up. You need to get it installed, usually with Docker, point a domain at it, and set up HTTPS so it's not sitting there naked on the internet. If you've done this kind of thing before, it's an hour. If you never have, budget an afternoon and some Googling. This is real, and it's the part the "n8n is free!" crowd conveniently skips.
Ongoing maintenance. Updates, backups, the occasional moment where something breaks and it's on you to fix it, not a support team. It's not a heavy load once it's stable, but it never fully drops to zero.
So here's how I'd put it. Self-hosted n8n is better described as unmetered than as free. You stop paying per execution and start paying with a little bit of ownership. For some people that's the best deal in automation. For others it's a headache they'd gladly pay to avoid, and there's no shame in that.
Who should self-host and who should pay
Let me make this concrete, because "it depends" is a useless answer.
Self-host if: you're technical enough to be comfortable in a terminal, you're running high-volume workflows where cloud execution limits would bite, you care about data staying on your own infrastructure, or you're building this into a business where owning the stack is part of the point. If you're an aspiring automation freelancer, learning to self-host is honestly a skill worth having. Clients pay for people who can run the whole thing.
Pay for Cloud if: you want to build automations, not babysit servers. If your time is worth more than the subscription, if you're just starting and want to learn the tool without a DevOps detour, or if the workflows you're running fit comfortably inside a plan's execution limits, Cloud is the sane choice. Paying twenty-ish dollars a month to skip server maintenance is a bargain when you value the hours you'd otherwise sink into it.
Plenty of people start on Cloud to learn, then move to self-hosted once volume makes the math obvious. That's a totally normal path. You don't have to marry your first choice.
n8n vs Zapier and Make on price
Here's where n8n's pricing philosophy really separates from the pack.
Zapier and Make both meter you on the small units of work. Zapier counts tasks, Make counts operations, and either way a busy multi-step workflow eats your allowance fast. The pricing is friendly at low volume and gets aggressive right when your automations start doing serious work. That's not a bug in their model, it's the model.
n8n comes at it from the other side. Self-hosted, you're not metered at all. On Cloud, you're metered by whole-workflow executions, which is a far gentler unit than per-step. The more complex and high-volume your automations, the more that difference compounds in your favor.
The tradeoff, and I won't hide it: Zapier is easier on day one. More polished onboarding, more no-code hand-holding, a bigger app directory. n8n asks a little more of you up front and pays it back in cost and flexibility later. If you want the full head-to-head, I broke it down in n8n vs Zapier, and there's a wider view in Zapier alternatives if you're shopping the whole field.
FAQ
Is n8n free? Yes, if you self-host the Community edition. It's open source, you run it on your own server, and you pay n8n nothing regardless of how many workflows or executions you run. The only cost is the server it lives on and your time to set it up and maintain it. n8n Cloud, the hosted version, is a paid subscription with a free trial.
How much is n8n Cloud? n8n Cloud runs on monthly plans that step up based on how many executions and active workflows you need, with the entry tier generally sitting in the low tens of dollars a month and a free trial before you pay. The exact prices and tier names change, so confirm the current numbers at n8n.io rather than trusting a figure in any blog post, including this one.
Is n8n cheaper than Zapier? For most real workflows, yes, and the gap grows with complexity. Zapier charges per task, so every step in a multi-step automation counts against you. n8n Cloud charges per full-workflow execution, so a forty-node workflow and a two-node workflow both cost one execution when they run. Self-hosted n8n removes the per-execution cost entirely. The more steps and volume you have, the bigger the savings.
What's the difference between n8n Community and Cloud? Community is the free, self-hosted version you run on your own infrastructure. Cloud is the paid, n8n-hosted version where they handle the servers, updates, and uptime for a monthly fee. Same core tool, different amount of work on your end.
Do I need to know how to code to use n8n? No to start. You can build a lot with the visual nodes alone. It leans a bit more technical than Zapier, and you can drop into code when a workflow demands it, but you don't need to be a developer to get going. Our n8n tutorial walks you through your first real workflow, and what is n8n covers the basics if you're brand new.
If your automations are still small, honestly, don't overthink it. Start on the free trial or a cheap self-hosted box and build something real. The pricing question sorts itself out once you can see how many steps and how much volume you're actually running.
The bigger win is learning to build the automations at all, because that's the skill people pay for. If you want to get properly good at this, from the fundamentals to selling it as a service, that's exactly what we teach inside CodingPhase. Come browse the courses and start with the best AI automation tools worth learning first. You've got this, and we're here to help you turn it into something real.
