n8n Self-Hosted vs. Cloud: What Mid-Market Companies Should Choose

Anyone rolling out process automation today will quickly land on n8n. The open-source tool has established itself as a credible alternative to Zapier and Make, especially for companies that want greater control over their data and automation logic. But as soon as evaluation begins, the first strategic question surfaces: self-hosted or cloud?

This is not a configuration question. It is an operating-model decision with lasting consequences for data privacy, IT resources, scalability, and ongoing costs, spanning years. This article lays out the trade-offs plainly, without vendor-brochure prose.

What n8n Is and What It Is Not

n8n is a workflow automation tool with a visual interface and a code escape hatch. It connects APIs, databases, SaaS tools, and internal systems via nodes. Logic can be assembled via drag-and-drop or extended with JavaScript.

Against Zapier and Make, n8n makes three arguments: open source (MIT core), a self-hosting option, and no pay-per-task pricing model.^[1] The last point is particularly relevant for mid-market companies: anyone who needs 50.000 automation runs per month quickly faces four-figure monthly bills with Zapier, with n8n, execution count carries no price tag when self-hosted.

n8n GmbH (Berlin) has also offered a managed cloud variant since 2021. That creates precisely the decision situation this article addresses.

The Two Variants at a Glance

n8n Self-Hosted means: you run the software on your own infrastructure, on-premises, with a German hosting provider (e.g., Hetzner, IONOS), or in a private cloud.^[3] You are responsible for installation, updates, backups, monitoring, and availability.

n8n Cloud means: n8n GmbH operates the instance. You pay monthly per active workflow trigger event (as of Q2 2026: from €24/month for the Starter plan, Pro from €60, Enterprise on request). The vendor handles updates, backups, and infrastructure.

Trade-Off Matrix: The 6 Decisive Dimensions

1. Data Privacy and Data Sovereignty

Self-hosted wins clearly here. Process data, all payloads flowing through workflows, never leave your network.^[2] For industries with regulatory requirements (financial services, medical technology, tax advisory), this is often not a comfort feature but a compliance prerequisite.

n8n Cloud stores execution logs and workflow metadata on n8n GmbH's servers. According to the privacy policy (as of May 2026), data is processed within the EU. For many mid-market companies, that is sufficient, but: you have no influence over the configuration, the subprocessors, or future changes to data storage.

Decision rule: Do your workflows process personal data, financial information, or trade secrets? If so, self-hosted is the safe choice from a GDPR perspective.

2. Operational Overhead (Total Cost of Ownership)

This is where many mid-market companies miscalculate.

Self-hosting sounds cheaper and can be. But comparing license costs against infrastructure costs misses the real picture. The true cost driver is staff time: who installs, who patches, who monitors, who intervenes at 3 a.m. when the queue hangs?

For a company without a dedicated platform team, a self-hosted n8n instance realistically costs 4–8 hours per month in administration, under normal operations. With more complex workflows, on-premises system integrations, and multiple teams, that figure rises.

n8n Cloud eliminates this overhead entirely. For companies whose IT team is already stretched, that is a substantial argument, not just a convenience argument.

Rule of thumb: Self-hosted pays off from around 5–6 active users and >30 productive workflows, where the monthly cloud price exceeds the opportunity cost of administration.

3. Customizability and Technical Depth

Self-hosted wins without qualification. You can:

Develop and deploy custom nodes
Run n8n behind your own reverse proxy (including SSO via LDAP/SAML)
Ship workflow execution logs directly into your own monitoring infrastructure (Prometheus, Grafana)
Build multi-instance setups for different departments or tenants
Customize Docker images and integrate them into existing CI/CD pipelines

n8n Cloud does not offer this depth. Anyone who needs custom nodes or embeds n8n into existing enterprise systems cannot avoid self-hosting.

4. Availability and SLA

n8n Cloud currently advertises a 99.9% uptime SLA for the Pro plan on its service page. Your self-hosted instance delivers the SLA you build yourself, which in practice, for most mid-market companies without a redundancy setup, falls below that figure.

Anyone running n8n for business-critical processes (e.g., automated invoice processing, order intake, customer communications) must answer the high-availability question. Self-hosted HA is feasible (active/passive with PostgreSQL and Kubernetes or Docker Swarm), but not trivial.

Rule of thumb: For non-critical internal processes, self-hosted on a simple VPS is acceptable. For external, customer-facing workflows or real-time integrations, plan for either n8n Cloud or a self-hosted HA architecture.

5. Cost at Scale

n8n Cloud pricing is execution-dependent. The Pro plan allows 10.000 active workflows per month; beyond that it becomes expensive. Self-hosting has no such ceiling.

For mid-market companies with high volume, logistics, e-commerce, manufacturing with MES connectivity, self-hosting is structurally cheaper once monthly execution volume reaches tens of thousands.

Example: A mechanical engineering firm in Baden-Württemberg (approx. 120 employees) automates its ordering process and triggers 80.000 workflow executions per month. Self-hosted on a Hetzner server (CPX31, approx. €18/month) plus administration overhead costs a fraction of the equivalent cloud plan.

6. Time-to-Value and Onboarding Friction

n8n Cloud wins here. A new team is productive in 30 minutes, no infrastructure, no Docker, no network configuration. For evaluations, pilot projects, or teams without a technical background, this is decisive.

Self-hosted requires initial setup time: provision infrastructure, install n8n (Docker Compose is the standard), configure the reverse proxy, set up backups. Realistically: 1–2 days for a solid base installation, 3–5 days for a production-ready setup with monitoring.

Three Mid-Market Scenarios

Scenario A, Tax Advisory Firm, 60 Employees Primary goal: automate client communication (document requests, deadline tracking). Data is sensitive, GDPR requirements are high, IT team: 1 person. → Recommendation: Self-hosted, managed by an n8n consultant. Data sovereignty is non-negotiable. Operational overhead is covered by an external managed service.

Scenario B, SaaS Startup, 35 Employees, Fast Growth Goal: sales and onboarding automation, no sensitive customer data, technically capable team. → Recommendation: n8n Cloud (Starter/Pro). No infrastructure overhead, fast iteration. Switch to self-hosted once execution volume makes cloud costs disproportionate.

Scenario C, Manufacturing Mid-Market, 200 Employees, Existing IT Infrastructure Goal: ERP integration (SAP B1), production data aggregation, custom nodes for internal APIs. → Recommendation: Self-hosted, on-premises or Hetzner Dedicated, integrated into existing monitoring. Custom nodes are not optional here. The cloud variant is ruled out.

The Build-vs.-Buy Question Behind the Question

The real decision is not "self-hosted or cloud", it is: "Do we want to build n8n operations as a core competency, or do we want to buy automation outcomes?"

For most mid-market companies, n8n operations is not a core competency. That points to one of two models:

n8n Cloud, the vendor takes full responsibility for operations.
Self-Hosted Managed, an external n8n consultant handles installation, operations, updates, and monitoring, while you retain control over data and configuration.

Model 2 combines the data sovereignty of self-hosting with the reduced operational overhead of a managed service. It is the model we implement at NextGen IT for the majority of our mid-market clients.

Checklist: When Self-Hosted, When Cloud

Self-hosted when:

Workflows process personal or regulated data
Custom nodes or deep system integration required
Execution volume >20.000/month (cloud becomes uneconomical)
SSO/LDAP integration with existing corporate directories required
Operations secured by an internal admin or external managed service

n8n Cloud when:

Fast evaluation or pilot project without infrastructure overhead
No dedicated IT team available
Data is non-sensitive, no regulatory framework applies
Execution volume moderate (<10.000/month)
Time-to-value is the primary success factor

Conclusion

n8n is a serious platform choice for mid-market companies, both self-hosted and in the cloud. The decision does not hinge on technical preferences but on three questions: How sensitive is the data? Who takes responsibility for operations? What volume is planned?

Those who choose self-hosting without in-house platform expertise should work with an experienced n8n consultant, not to hide the complexity, but to solve it correctly once and master it permanently.

Sources

[1] n8n pricing page (accessed May 2026)

[2] n8n privacy policy (accessed May 2026)

[3] n8n Docs, Self-hosting guide (accessed May 2026)