n8n Cloud vs self-hosted: the real cost for a small business

Two different kinds of bill

With n8n Cloud, you pay n8n a subscription and they run everything: the servers, updates, uptime and the database behind your workflows. With self-hosting, the software costs nothing to run as the free Community edition, but you rent a server and someone on your side becomes the system administrator.

So the real comparison isn’t “subscription vs free.” It’s “subscription vs server plus staff time plus risk.” For a small business, staff time is usually the biggest number in that sum, and it’s the one people forget to price.

How n8n Cloud pricing works

I checked the n8n pricing page on October 18, 2026. Prices change and are shown in different currencies by region, so check the page for current numbers. The model itself is what matters for planning:

• You pay for executions, not steps. Plans are tiered by how many workflow executions you get each month. An execution is one full run of a workflow, no matter how many nodes it has or how much data it moves. A ten-step workflow that runs once counts the same as a two-step one.
• Users and workflows aren’t the limit. The page says all plans include unlimited users and workflows. What changes between tiers is the execution allowance, how many runs can happen at the same time, and features like shared projects.
• Going over doesn’t stop your workflows. According to the page, workflows keep running if you exceed your quota, but overage charges may apply if you don’t move up a tier.
• Annual billing costs less. The page offers a discount for paying yearly instead of monthly.

The practical takeaway: Cloud costs scale with how often your workflows run, not how complex they are. That rewards good design. One workflow that processes fifty records in a single run is one execution. A trigger that fires once per record is fifty.

What self-hosting actually costs

Here’s every line I’d put in a self-hosting budget. The server prices come from DigitalOcean’s public Droplet pricing page, which I checked on October 18, 2026, as one example of a typical VPS provider. Other providers price differently.

The first two rows are small. The last three are where self-hosting gets expensive, because they never end. n8n’s own hosting docs list several ways to run it, including Docker Compose for production and guides for providers like AWS, Google Cloud, DigitalOcean and Hetzner. Every one of them assumes someone is comfortable running a server.

Work out your own number in five steps

You don’t need a spreadsheet model. A rough pass with these steps is enough to decide.

1. Count your executions. List each workflow and how often it runs. A form-to-CRM workflow runs once per submission. A schedule that checks for new orders every five minutes runs about 8,600 times a month, even when there’s nothing new. Add them up.
2. Find your Cloud tier. Match that monthly total to a tier on the pricing page, with headroom for growth. That’s your Cloud cost.
3. Price the server. Pick a VPS size and add backups. For a handful of light workflows, a small server is usually enough. Heavy AI or file processing needs more memory.
4. Price the time. Estimate the hours per month someone will spend on updates, checks and fixes, and multiply by what that person’s hour costs the business. Be honest. Even if it’s you, your time has a price.
5. Add the risk. Ask what one day of your workflows being down would cost: missed leads, late invoices, angry customers. If it’s significant, weigh that against who’s on call for each option.

Compare step 2 against steps 3, 4 and 5 combined. For a small business with a few workflows, the Cloud number usually wins once staff time is in the sum. The server alone is almost never the deciding factor.

When self-hosting pays off

Self-hosting makes sense when one or more of these is true:

• Very high volume. When your workflows run tens of thousands of times a month, execution-based pricing grows with you, while a server’s cost stays fairly flat. That’s where self-hosting saves real money.
• Data has to stay in your environment. If customer, health or financial data can’t leave your own infrastructure, self-hosting may be a requirement rather than a choice.
• You already run servers. If someone on staff already manages Linux servers and backups, adding n8n is a small extra task rather than a new job.
• You need custom setup. Self-hosting lets you control environment variables, custom nodes and how n8n connects to internal systems behind your firewall.

And it usually doesn’t pay off when you have a few workflows, no in-house IT and a team that would rather spend its time on the business. That describes most small companies starting out with automation.

You can change your mind later

This decision isn’t permanent. Workflows export as JSON and can be imported into another n8n instance, so starting on Cloud and moving to self-hosted later is a normal path. Credentials need to be set up again on the new instance, so plan an afternoon of testing for the move.

My usual advice is to start on Cloud, get a few workflows earning their keep, and then look at your actual execution count after a few months. Real numbers beat guesses. If you want to try n8n before paying for anything, the n8n beginner course walks you through building your first workflows step by step, and it teaches you to think in executions from the start.