n8n Self-Hosted Limitations, Honestly

What You Give Up, Stated Plainly

Most writing about self-hosting n8n is enthusiastic about the cost saving and quiet about the trade. We self-host for a good share of our client builds, so this isn't a pitch against it. It's the list we go through before recommending it, because a limitation you meet in month one is a bad surprise and a limitation you knew about is a design decision.

Features That Are Not in the Community Edition

The free self-hosted build is genuinely capable, and a few things sit behind the paid tiers.

Multiple users with separate logins and permissions. The community edition is effectively one workspace. If you need three people with their own accounts and different access to different workflows, that's an enterprise feature. For a solo operator or a small team sharing one login, irrelevant. For an agency running client workflows that must stay separated, it's the whole ballgame.

SSO and LDAP. Same category. Fine to skip until you have a compliance reason not to.

Log streaming to external systems. You get execution logs in the interface. Piping them into a central logging stack is a paid feature. You can work around it by having workflows write their own outcomes somewhere, which is what we usually do anyway.

Environments and version control for workflows. Promoting a workflow from staging to production, with git-backed history, is paid. On community you export JSON by hand. Workable, easy to get sloppy about.

Check the current feature comparison before deciding, since where the line sits moves between releases and anything quoted here ages.

The Licence, Which Trips People Up

n8n is fair-code, not strictly open source. Free to self-host and run for your own business, including commercially. What's restricted is offering n8n itself as a hosted service to other people.

For running your own automations, or an agency building workflows that live in a client's own instance, you're fine. If you were planning to resell an n8n-based platform, read the licence properly rather than assuming.

The Operational Limitations Nobody Lists

These matter more day to day than the feature table.

You own uptime. No status page, no support queue. If the server runs out of disk on a Saturday because execution data filled it, your automations stop and nothing tells you. Set up disk alerts before you need them.

Execution data grows. n8n stores the data from each run, and at volume that database gets large quickly. There's a pruning setting and you should configure it deliberately rather than discovering it. Turning execution logging down also matters if you're handling anything sensitive, which is the point we make in HIPAA compliant Zapier alternatives for clinics.

Upgrades are yours. New versions arrive regularly, occasionally with breaking changes to a node you depend on. Skipping upgrades indefinitely leaves you on an old build with unpatched dependencies. Pin a version, read release notes, upgrade deliberately.

Backups are yours. Workflows and credentials live in the database. No backup means rebuilding from memory. We've seen it happen once and it cost a fortnight.

One person understands it. The real risk in a small business. Document how to log in, where it runs, and how to restart it, and make sure a second person can get in.

Performance Ceilings Worth Knowing

A small VPS handles a surprising amount, and there are two places it stops.

Long-running workflows hold memory for their duration. A workflow processing a large file or looping over thousands of records can exhaust a small box, and the symptom is the container restarting rather than a clean error.

Concurrency is bounded by your hardware. Default setup runs a single main process. If twenty webhooks arrive at once, they queue. n8n supports a queue mode with separate workers for exactly this, and it's more infrastructure to run.

Neither is a wall so much as a point where you either size up or split the work. Self-hosted n8n server requirements covers what the box actually needs.

When These Limitations Should Change Your Mind

Go hosted instead if you need multiple users with real permissions today, if nobody on the team is comfortable maintaining a server, if compliance requires audit trails you'd have to build yourself, or if your workflows are few enough that per-run pricing is trivially cheap.

Self-host when run volume makes per-task pricing painful, when data must stay on infrastructure you control, or when you already have someone who runs servers without minding.

We sometimes recommend both: hosted for the customer-facing workflows where downtime costs money, self-hosted for high-volume internal processing where a delay is an inconvenience. When Zapier is still the right choice makes the same argument from the other direction.

The Summary

The community edition's limits are mostly about teams and governance, not capability. The workflow engine is the same one the paid tiers run. If you're one or two people automating your own business, you will likely never hit a feature limit, and the real cost is the hour a month of being your own sysadmin.

If you're an agency or a regulated business with several people needing separate access, the limits are immediate and the paid tier or a hosted alternative is the honest answer.

Open source Zapier alternatives compares n8n against the other self-hostable options, and what Zapier actually costs at scale has the arithmetic if cost is what brought you here.

Book a free 60-minute call and we'll work out whether self-hosting pays at your volume, which limitations you'd actually hit, and what running it would involve for your team.