Self-hosting n8n for small business

Why small firms look at n8n

n8n is a workflow automation tool with a visual builder, similar in purpose to Zapier and Make. It can be used as a hosted cloud service or installed on your own server. The self-hosted route attracts small businesses for two reasons. The first is cost: automation platforms that charge by task or operation can grow expensive as volume rises, while a self-hosted instance costs the same whether it runs a hundred workflows or ten thousand. The second is control: data passes through a server you manage rather than a third party's.

Those are real benefits. But they come with responsibilities that are easy to underestimate, especially in a firm without in-house technical staff.

What the license allows

n8n's documentation says all self-hosted installations use the same core product, and that without a license key n8n runs as the free Community edition. Adding a Business or Enterprise license key enables paid editions with extra features.

n8n uses its own Sustainable Use License, which it describes as fair-code rather than open source. According to n8n, the license permits use for your own internal business purposes, such as syncing data you control from a CRM to an internal database, and permits consultants to build and maintain workflows for you. It does not permit things like hosting n8n and charging others to access it, or white-labeling it for your customers. For a service business automating its own operations, that is usually fine, but read the license yourself and ask n8n if you are unsure.

There is a middle path as well. n8n offers its own hosted cloud service, which keeps the same workflow builder without the server work. Some firms start there and move to self-hosting later if volumes grow or data requirements change.

What self-hosting actually involves

n8n's documentation lists several installation routes, including Docker Compose for production deployments and guides for cloud providers such as AWS, Azure, Google Cloud, DigitalOcean and Hetzner. Installing it is the easy part. Running it well is ongoing work.

• Hosting: a server or cloud instance sized for your workload, with a production database.
• Updates: applying new versions regularly, testing that workflows still run afterward.
• Security: HTTPS, strong admin authentication, firewall rules, and limiting who can reach the editor.
• Credentials: n8n stores API keys and passwords for every app it connects to, so the server becomes a high-value target.
• Backups: regular, tested backups of the database and workflow definitions.
• Monitoring: alerts when workflows fail or the server goes down, and someone who responds.
• Documentation: a record of what runs, who owns it and how to recover it.

The real cost comparison

Self-hosting is free in license terms, not in total cost. The server itself may cost little each month, but the time to maintain it is the larger expense. Someone has to apply updates, check backups, investigate failures and keep security current. If that person is an outside IT provider or developer, budget for their hours. If it is an employee, count the time they are not spending on their actual job.

A fair comparison puts three numbers side by side: the cloud subscription at your expected volume for Zapier, Make or n8n Cloud; the server cost plus maintenance hours for self-hosting; and the cost of an outage, meaning what happens if leads stop flowing into the CRM for a day. For a firm running a few dozen automations at modest volume, managed cloud often wins once maintenance is counted. For a firm processing thousands of documents or records a day, self-hosting can save meaningful money.

Remember that outages have a business cost as well as a technical one. If an intake workflow stops for a weekend and nobody notices, enquiries may sit unanswered until Monday. Hosted services carry this risk too, but with self-hosting, detecting and fixing the problem is entirely your responsibility.

Security and compliance considerations

Data control is a common reason to self-host, but it only helps if the server is actually well secured. A poorly maintained n8n instance exposed to the internet, holding credentials for your email, CRM and accounting system, is a bigger risk than a reputable cloud service. If you self-host, keep the editor behind a VPN or single sign-on, restrict admin access, turn on multi-factor authentication where possible, and apply security updates promptly.

For regulated firms, self-hosting can simplify some questions, since client data stays on infrastructure you control, but it does not remove your obligations. A health practice still needs to meet HIPAA security requirements on that server. A tax or accounting firm should include it in its written information security plan under the FTC Safeguards Rule and IRS Publication 4557. Ask your adviser how these apply.

Also decide who can build and edit workflows. Every editor can potentially reach the credentials stored in n8n, so keep that group small and review it whenever staff or contractors change.

When self-hosting makes sense

If most of those are not true, start with a hosted option, either n8n Cloud or another platform. You can move to self-hosting later once you know your volumes and have the support in place.

• You run high volumes of automation, where per-task pricing would be expensive.
• You have a strong reason to keep data on your own infrastructure.
• You have an IT provider or staff member who already manages servers and will own this one.
• Your workflows need custom code or connections that hosted tools handle poorly.
• You are prepared to treat the server as a production system, with monitoring and backups.

A sensible way to start

If you decide to self-host, start small. Pick one or two workflows with clear value, such as moving intake form data into your practice management system, and build them on a properly configured server with backups and alerts from day one. Document every workflow and credential. Agree in writing who handles updates and failures, and test a restore from backup before you rely on the system.

Review after 90 days: how many hours went into maintenance, how many failures occurred and how quickly they were fixed, and what the hosted alternative would have cost. Then decide whether to expand, stay as you are or move to a managed service. InTheory would usually run this comparison before recommending either path.