Is self-hosting n8n worth it for a small business?

n8n has a reputation as the automation tool you can run for free. The Community edition is open to download, you install it on a server you control, and there is no per-task or per-execution bill. For a firm watching its Zapier or Make invoice climb, that sounds like an easy win.

The direct answer: self-hosting n8n is worth it when you have high automation volume, a clear reason to keep data on your own infrastructure, and a named person (in-house or contracted) who will look after the server every month. Without that person, the money you save on subscriptions usually comes back as downtime, silent failures and an unpatched server holding client data. For most 10 to 50 person firms with modest volume, n8n Cloud or a mainstream hosted tool is the better starting point.

What "free" actually covers

Without a license key, a self-hosted install runs as the free Community edition. It is a capable product: the workflow editor, the built-in integrations, code steps and the HTTP Request node for anything with an API. What it leaves out matters more for a firm than for a hobbyist. n8n's list of Community edition limits includes:

• No sharing of workflows and credentials, and no projects. In practice, one person's account owns everything.
• No SSO (SAML or LDAP), so staff accounts are not tied to your Microsoft or Google sign-in.
• No environments or Git version control, so there is no clean way to test a change before it goes live.
• No log streaming or external secrets, which are the features that make monitoring and credential handling easier to audit.

Registering the Community edition with an email unlocks a few extras (folders, debugging in the editor, custom execution data), but not the team features above. Those sit in the paid Business and Enterprise licenses, which n8n lists on its pricing page as of October 2026. The Business license is self-hosted only and priced for teams running serious volume, so it changes the "free" math considerably.

There is also the license itself. n8n is distributed under its own Sustainable Use License, which says you may use or modify the software "only for your own internal business purposes or for non-commercial or personal use". Running your firm's own automations fits that description. If you plan to offer automations to your own clients as a service, read the license and check with your lawyer first.

What you take on when you self-host

n8n's own comparison of Cloud and self-hosted is blunt: with self-hosting you provide and manage the infrastructure, technical expertise is required for installation and configuration, and maintenance is your responsibility. For a professional services firm, that list breaks down into real recurring tasks:

1. The server. A cloud virtual machine or a container platform, sized for your workload, with a domain and an HTTPS certificate.
2. The database. n8n stores every execution, including the data that passed through it. The docs warn that this database can grow and run out of storage unless pruning is configured; by default, finished executions are pruned after 14 days or once there are more than 10,000 of them.
3. Updates. n8n releases frequently. Someone has to read the release notes, update, and check that nothing broke.
4. Backups and restores. A backup you have never restored is a hope, not a backup. Test it at least once.
5. Security. Patching the operating system, restricting who can reach the editor, protecting the stored credentials for every connected app, and reviewing access when staff leave.
6. Monitoring. If the server stops at 2am, nothing emails you unless you set that up. With a hosted tool, the vendor carries this.

None of these is difficult for someone who runs servers for a living. All of them are easy to forget for a busy operations manager who installed n8n from a tutorial one weekend.

The real cost comparison

The subscription saving is visible; the operating cost is not. A fair comparison looks at four lines, not one:

For a sense of the hosted side, Zapier's Team plan is listed from $69 a month billed annually for 2,000 tasks, as shown on Zapier's pricing page in October 2026. If your hosted bill is in that range, a few hours a month of competent server maintenance will usually cost more than you save. If your automations process tens of thousands of records a month and your hosted bill has grown with them, the balance can tip the other way.

A useful test: price one hour a month of maintenance at the rate you would pay an IT provider, add the server, and compare that with your current or projected subscription. Then ask who covers the month that person is on vacation.

When self-hosting does make sense

• High volume, simple logic. Workflows that run thousands of times a day, such as syncing records or processing inbound documents, are where per-task pricing hurts most.
• Data location requirements. Some firms want automation data to stay on infrastructure they choose, for client or regulatory reasons. Self-hosting gives you that control, but it also makes you responsible for securing it. For health data, read our article on whether Zapier or Make can carry patient data, which covers what self-hosting does and does not solve, and check with your compliance lead.
• You already run servers. If your IT provider manages other Linux servers for you and will add n8n to their maintenance contract in writing, most of the hidden cost is already covered.
• You need custom code or internal systems. n8n handles code steps and private network access well, which hosted tools can make awkward.

When it usually does not

• Nobody owns it. If the honest answer to "who updates it?" is "whoever set it up", stop here.
• Low volume across many apps. Ten automations running a few hundred times a month are cheap on hosted plans, and hosted tools have larger ready-made app catalogs.
• Several people need to build and share. The Community edition's lack of sharing and SSO makes it awkward for a team, as covered in our comparison of n8n and Zapier for firms without a developer.
• The goal is only to save a subscription. A cheaper tool does not fix a messy process. Many automation bills are high because the same work runs twice or a workflow loops, not because the tool is expensive.

A middle route: n8n Cloud

If you like n8n's editor and its pricing model but do not want a server, n8n Cloud runs the same software for you. Its plans are priced per workflow execution rather than per step, as shown on n8n's pricing page in October 2026, which can be favorable for long, multi-step workflows. You can start on Cloud and move to self-hosting later if volume justifies it; exporting workflows is straightforward, though credentials have to be set up again.

How to decide in one meeting

1. List the automations you run or want, with rough monthly volume for each.
2. Price them on one hosted plan, using the vendor's own calculator.
3. Name the person who would maintain a self-hosted server, and get their time and rate in writing.
4. Write down any data location requirement, and confirm it with your compliance lead.
5. If the saving is small, there is no named owner, or no data requirement, choose hosted.

How Flow Mesh helps

Whether a tool should be self-hosted, moved to a hosted plan or retired is exactly the kind of call our stack audit makes: a verdict on every tool (keep, configure, consolidate or replace) and a written scope for what is worth building. If you go ahead, any integration work is quoted in writing after the audit and done inside your own accounts and infrastructure.

Key takeaways

• Self-hosted n8n Community has no license fee, but it lacks sharing, SSO, environments and Git version control.
• You take on the server, database growth, updates, backups, security and monitoring.
• It pays off with high volume, a real data location need and a named, contracted maintainer.
• For modest volume and no in-house IT, n8n Cloud or another hosted tool is usually cheaper in total.
• Price the maintenance time, not just the subscription you would cancel.