A founder I worked with last year had read the same thing you probably read: n8n is free if you host it yourself. He runs a six-person agency, he is comfortable with a terminal, and the maths looked unbeatable. A 6-dollar server against a 60-euro monthly subscription. He spun up a droplet on a Saturday, had his first workflow running by lunch, and felt like he had just outsmarted a software company.
Six weeks later he messaged me on a Tuesday night. An n8n update had introduced a breaking change, one of his live workflows had silently stopped firing two days earlier, and a client had noticed before he did. He had no backup of the workflow he had spent an afternoon building. He was, at 11pm, reading a changelog he did not fully understand, trying to work out whether rolling back would lose data. The server was still costing 6 dollars a month. The Tuesday night was costing him something the invoice never showed.
That gap, between the price you see and the cost you pay, is the entire decision. n8n self-hosted versus cloud is not really a question about money, because the sticker prices make self-hosting look like an obvious win. It is a question about whose evenings get spent keeping the thing alive. For most small businesses the honest answer is n8n Cloud, and this article walks through exactly why, where that breaks, and the cases where self-hosting genuinely is the smarter call. If you are still deciding between platforms entirely, our n8n vs Zapier comparison for small business is the better starting point. This one assumes you have chosen n8n and now have to decide how to run it.
The fork in the road
Picking n8n is the easy part, and it is increasingly a popular one. The project crossed 190,000 stars on GitHub by 2026, making it one of the most-starred automation tools in existence, and it carries a fair-code Sustainable Use License with source that is always visible and self-hostable (n8n GitHub repository, 2026). That combination, genuine open availability plus a polished commercial cloud, is exactly what creates the fork you are now standing at. The same product runs two ways, and the wrong choice does not break anything immediately. It just slowly costs you in a column you forgot to budget.
The two paths look almost identical on the surface. The same node-based editor, the same 400-plus integrations, the same workflows. The difference is everything underneath the editor. On Cloud, n8n runs the servers, applies the updates, handles the backups, and patches the security holes while you sleep. Self-hosted, all of that becomes your job, in exchange for a much smaller and more predictable infrastructure bill plus complete control over where your data lives.
The reason this decision trips up smart people is that it is genuinely close on paper and genuinely lopsided in practice. The paper comparison favours self-hosting so heavily that it feels like cloud is a tax on the lazy. The lived comparison, the one that includes the Tuesday nights, swings the other way for almost every small business that does not have a spare technical person whose job already includes babysitting servers. The rest of this article is an attempt to put real numbers on both the paper and the practice, so you can see which side of the line you actually sit on.
What each option actually is
n8n Cloud is the hosted, managed version that n8n itself runs. You sign up, you log in, you build, and you never think about a server. Updates arrive automatically. Backups happen without you. If a security patch ships at 3am, it is applied before you wake up, by people whose entire job is keeping the platform healthy. You are renting both the software and the operational discipline that keeps it running, and the second part is the part most people undervalue until they need it.
Self-hosted n8n is the same software, installed on infrastructure you control, most often a small cloud server you rent from a provider like DigitalOcean, Hetzner, or AWS. Because of the fair-code license, the software itself is free to run this way for your own internal use, which is the headline that draws everyone in. What you take on in exchange is the role of system administrator: you install it, you secure it, you update it, you back it up, you monitor it, and when it breaks at an inconvenient hour, you are the one who fixes it. The software is free. The operations are not.
There is a middle reality worth naming, because the marketing on both sides hides it. Self-hosting n8n in 2026 is genuinely easier than it used to be: a Docker image, a few commands, and a basic instance is live in under an hour. The difficulty was never the first install. It is the hundredth day, when an update has shipped, your backup script has been silently failing, and your live workflows are the thing standing between a client and a missed deadline. Cloud is not selling you the install. It is selling you the hundredth day. To see how this stacks up against the other major platforms, our Make vs n8n vs Zapier breakdown compares all three on exactly these tradeoffs.
The real pricing comparison
Start with the sticker prices, because they are what everyone compares first and they are genuinely informative. n8n Cloud bills on executions, not on the number of steps in a workflow or the volume of data it moves. One execution is a single run of an entire workflow, start to finish, no matter how many nodes it touches (n8n pricing, 2026). The Starter plan runs around 24 euros a month for roughly 2,500 executions, the Pro plan around 60 euros for 10,000, and the Business plan sits at 800 euros for 40,000 executions with the heavier security and version-control features a larger team needs. Every plan includes unlimited active workflows and unlimited users, which is the genuinely generous part of the model.
The execution-based model is worth pausing on because it is the opposite of how Zapier charges, and it changes the economics for a small business completely. A workflow with forty steps that runs a thousand times a month costs the same as a two-step workflow that runs a thousand times. You are billed for runs, not complexity. That rewards building rich, capable automations rather than trivially simple ones, and it is a large part of why technically minded small teams gravitate to n8n in the first place.
Self-hosting moves the cost from a subscription to infrastructure, and on this line it wins clearly. A small cloud server with 1GB of RAM costs around 6 dollars a month, and a more comfortable 2-to-4GB instance that handles a moderate automation load sits in the 12-to-24-dollar range, with a stable production setup running 2 vCPUs and 4GB landing closer to 20-to-40 dollars a month (industry self-hosting cost analyses, 2026). On pure infrastructure, self-hosting can be five to ten times cheaper than the equivalent Cloud plan, and the execution count is effectively unlimited. If you run hundreds of thousands of executions a month, this difference stops being a rounding error and becomes the whole argument. The catch is that the infrastructure bill is not the real bill, which is the next section.
The maintenance burden nobody quotes
Here is the cost that never appears in a pricing table and decides the entire comparison: your time. Honest time-tracking from teams running self-hosted n8n in production lands at 1 to 3 hours a month spent on infrastructure: updates, monitoring, backup verification, and the occasional debugging session (industry self-hosting cost analyses, 2026). That sounds small until you price it. At a modest 30 euros an hour for a founder or technical staffer, three hours a month is 90 euros, which already exceeds the Pro Cloud plan it was supposed to undercut. At a real founder's opportunity cost, the maths gets worse, not better.
The work itself is not glamorous and it does not stop. n8n ships updates frequently, including security patches, and each one means pulling a new image, reading the changelog for breaking changes, restarting the service, and verifying your live workflows still fire. Backups are not automatic: you have to configure them, store them somewhere safe, and, the part everyone skips, actually test that they restore. Monitoring means either paying for a service or building your own alerting, because a workflow that silently stopped two days ago is the failure mode that costs you a client, exactly as it nearly did for the agency founder I opened with.
This is the heart of the honest comparison. The self-hosting decision is not "save 50 euros a month." It is "trade 50 euros a month for a recurring operational responsibility that lands on the most expensive person in the building." For a business with a spare technical hand who genuinely enjoys this work, that trade can be fine, even good. For a four-person Shopify brand or a solo consultant, the founder becoming the part-time sysadmin is precisely the kind of invisible drain that automation was supposed to eliminate. You did not buy n8n to spend Tuesday nights reading changelogs.
Security and data control
This is the one dimension where self-hosting has a real, non-negotiable advantage, and it is worth being precise about. When you self-host, your workflow data and the credentials your automations use never leave infrastructure you control. For a business handling sensitive personal data, operating under strict data-residency rules, or working in a regulated sector where "where exactly does this data live" is a question an auditor will ask, that control is not a preference. It can be a requirement, and no amount of Cloud convenience substitutes for it.
But control and security are not the same thing, and conflating them is how self-hosters get hurt. Self-hosting gives you control over your data and full responsibility for protecting it. The server you control is also the server you must secure: the firewall, the access controls, the encryption, the patch you applied late, the port you left open. n8n Cloud, by contrast, is secured by a team whose full-time job is exactly that, with the security patches applied automatically and the infrastructure hardened to a standard most small businesses cannot match on a 6-dollar droplet. Control moved to you. So did every consequence of getting it wrong.
For most small businesses, the honest reading is that Cloud is the more secure option in practice, because a managed platform patched by professionals beats a self-managed server patched by a busy founder. The exception is the business whose regulatory or contractual position makes data residency mandatory, where self-hosting is the only compliant choice and the security work simply becomes part of the cost of operating legally. Know which of those two you are before you decide, because guessing wrong is expensive in opposite directions.
When each one makes sense
n8n Cloud makes sense for the clear majority of small businesses, and the profile is consistent. You have a handful of people, no dedicated technical operations staff, and an execution volume that fits comfortably inside a Starter or Pro plan. You want to build automations, not maintain servers. Your evenings are worth more than 50 euros a month. If that is you, Cloud is not the lazy choice, it is the correct allocation of your scarcest resource, which is attention. The subscription is the price of never having a Tuesday-night changelog problem.
Self-hosting makes genuine sense in three situations, and they are worth naming precisely so you do not talk yourself into it for the wrong reason. The first is real technical capacity: you have someone whose job already includes running infrastructure, for whom n8n maintenance is a small marginal addition rather than a new responsibility. The second is volume: if you are running hundreds of thousands of executions a month, the Cloud bill scales into territory where the infrastructure savings genuinely dwarf the maintenance time. The third, and the only truly non-negotiable one, is data residency: when regulation or a contract requires your data to stay on infrastructure you control, the decision is made for you.
Notice what is not on that list: "because it is free" and "because I am technical enough." Free is the sticker price, not the real cost, and being technically capable of self-hosting is not the same as it being the best use of your time. The founder from the opening was both technical and right that the software was free. He was wrong about which of his resources was actually scarce. If you are taking your very first steps with automation regardless of platform, our guide to building your first AI automation without code is the gentler on-ramp, and it assumes Cloud for exactly the reasons above.
The honest verdict
For most small businesses, choose n8n Cloud. Start on the Starter or Pro plan, build your automations, and let n8n carry the operational weight you would otherwise carry yourself. The maintenance you avoid is worth more than the subscription you pay, in nearly every case where you do not already employ someone to run servers. This is not a close call once you put your own time on the same line as the infrastructure bill, which is the line the sticker-price comparison conveniently leaves blank.
Choose self-hosting when one of three things is true: you have genuine in-house technical capacity that makes maintenance nearly free, your execution volume is high enough that the infrastructure savings dwarf the time cost, or your data must legally stay on infrastructure you control. In those cases self-hosting is not a compromise, it is the right answer, and the savings or the compliance are real. The mistake is choosing it for the sticker price alone and discovering the real price on a Tuesday night.
The decision underneath the decision is simple once you see it. You are not choosing between cheap and expensive. You are choosing where to spend a fixed amount, in cash or in attention, and for a small team attention is almost always the scarcer of the two. Spend the cash, keep the attention, and point that attention at the work only you can do. That is the version of this decision that founders are happiest with a year later, the one where the automations run quietly and nobody remembers the last time they thought about a server.
The honest summary: n8n is the same capable tool whether you rent it or run it, and the choice between Cloud and self-hosted is really a choice about whose time keeps it alive. The sticker prices say self-hosting wins by a mile. The real prices, once you count the 1 to 3 hours a month of updates and backups and the Tuesday-night fixes, say Cloud wins for almost every small business that does not have a spare technical hand or a regulatory reason to keep data in-house. Pick Cloud and get on with building. Pick self-hosting only when capacity, volume, or compliance genuinely tips the scale, and go in with your eyes open about the evenings it will cost. Either way, the goal is the same: automations that run themselves, so you do not have to.