n8n for Small Business: Is the Self-Hosted Route Worth It?

n8n is the one workflow automation tool in this category where «just self-host it, it’s free» gets said constantly online, usually by someone who hasn’t had to keep a self-hosted instance alive through a security patch, a Postgres upgrade, and a broken webhook at the same time. It’s also, genuinely, a real option — n8n’s Community edition is open source, free, and not a crippled trial version. Whether self-hosting is worth it for a specific small business depends on things that don’t fit in a one-line recommendation, so here’s the honest version, run through what it actually costs in money and in time.

What n8n is, quickly

n8n is a node-based workflow automation tool, similar in shape to Make — you connect nodes on a canvas rather than building a strictly linear chain like Zapier. What sets it apart from both is that it’s open source under a fair-code license, it ships full JavaScript and Python code nodes for anything the built-in nodes can’t do, and it bills by execution — one charge per workflow run, regardless of how many steps that run contains. It’s also the only one of the three major players covered on this site that you can run entirely on your own infrastructure.

Pros and cons, straight

Pros
– Community edition is genuinely free and open source, not a time-limited trial.
– Per-execution pricing (even on Cloud) rewards complex, multi-step workflows instead of penalizing them.
– Full code nodes (JavaScript and Python) mean very little is actually impossible to build.
– Self-hosting means your business data stays on infrastructure you control — relevant if you handle sensitive customer data or operate under data-residency requirements.
– Cloud plans bundle a monthly AI credit allowance for built-in AI nodes rather than charging for AI as a fully separate product.

Cons
– Steepest learning curve of the three major tools — non-technical staff will need real training or a dedicated builder.
– Self-hosting trades a subscription fee for hosting and maintenance responsibility, which is a real, ongoing time cost even when the server bill is small.
– Smaller native integration library than Zapier or Make, so less common apps mean building against the generic HTTP Request node and reading API documentation instead of picking a pre-built connector.
– Advanced team features — SSO, environments, Git-based version control — sit behind the paid Business/Enterprise tiers even when self-hosting, so «self-hosted» doesn’t automatically mean «full feature set for free.»
– Cloud plans are billed in euros, which adds a minor currency-conversion wrinkle for businesses budgeting in dollars.

What self-hosting actually costs in money

The server itself is genuinely cheap. A raw virtual private server capable of running n8n comfortably runs somewhere around $5 to $13 a month, depending on region, RAM, and how much storage and backup you want attached. A managed self-hosting service — one that handles the Docker setup and updates for you in exchange for a monthly fee — runs close to $10 a month per instance, which is still far below any of n8n’s own paid Cloud tiers.

On the pure infrastructure line item, self-hosting wins by a wide margin. Community edition itself costs nothing beyond the server, and there’s no execution cap, no task limit, no monthly credit allowance to watch. If your only question is «what’s the cheapest way to run n8n,» self-hosted Community edition on a small VPS is the answer, full stop.

What that number doesn’t include

The server bill is the smallest part of the real cost. Running n8n yourself means owning every piece of what a Cloud plan quietly handles for you: choosing and configuring the database (Postgres for anything beyond hobby use), setting up a reverse proxy and TLS certificates so webhooks work securely, applying software updates on a schedule instead of getting them automatically, managing backups and actually testing that they restore, and monitoring uptime so a crashed container at 2 a.m. doesn’t mean a missed lead-routing workflow going unnoticed until a customer complains.

None of that is exotic technical work if you or someone on your team has done basic server administration before. Initial setup is genuinely a matter of hours, not weeks — figure one to three hours for a first working instance using Docker. The part that catches people off guard isn’t the setup, it’s the maintenance rhythm afterward: security patches that need applying, an occasional broken upgrade that needs debugging, disk space that creeps up over months of logs and needs pruning. A cheap server is not actually cheap the night it costs you three hours of debugging a failed backup right before a workflow that matters needs to run.

If nobody on the team is comfortable with that maintenance rhythm, or comfortable enough to hire a contractor for a few hours a quarter to handle it, the «free» self-hosted option has a real cost — it’s just billed in time instead of dollars, and time is usually the scarcer resource in a small business.

n8n Cloud as the alternative

n8n also sells its own hosted version, which removes all of the maintenance above in exchange for a subscription, priced by monthly executions rather than by task or operation:

A free trial gives Pro-level features up to 1,000 executions with no credit card required, which is enough to genuinely test a real workflow before committing either way.

Self-hosted vs. Cloud, side by side

Who should actually self-host

Self-hosting makes sense when at least one of these is true: someone on the team already manages servers for other reasons and can fold n8n maintenance into that existing work; the business has a genuine data-residency or compliance reason to keep automation data off a third-party cloud; or the automation volume is high enough that Cloud’s execution-based tiers would cost meaningfully more than a cheap VPS plus a few hours of upkeep a month.

It stops making sense the moment «someone on the team» is really «me, in whatever spare time I have,» because that spare time doesn’t exist reliably in a small business, and a broken automation nobody’s watching is worse than no automation at all — it fails silently while everyone assumes it’s still working.

A realistic middle path worth mentioning: a managed self-hosting service. These providers run the Docker container, apply updates, and handle backups for a flat monthly fee close to what a raw VPS costs on its own, while you keep the «no execution limit, no per-task metering» advantage of Community edition. It’s not free in the strictest sense, but it removes most of the maintenance burden that makes pure self-hosting risky for a team without spare technical capacity, and it’s worth pricing out before assuming the choice is only between «fully self-managed» and «full Cloud subscription.»