TL;DR: Self-hosting n8n looks free until you price the ops. The honest crossover: cloud automation platforms ($20–120/month for n8n Cloud, $9–29/month for Make) win for teams under 5 engineers because the on-call cost when the cron node breaks at 2am dwarfs the subscription. Self-hosting wins above roughly 50,000 executions/month, when data residency or SOC 2 forces it, or when you have an engineer whose job already includes infrastructure. The hidden self-host bill: a VPS or Kubernetes cluster, Postgres, backups, monitoring, TLS, security patches, and your weekend when the database fills up. Trade subscription for ops.
Self-hosting an automation platform feels like the engineer move. It's also the move that loses the most teams the most time. Cloud automation platforms are not a tax — they're a service you're buying for a reason, and that reason is "you don't want to be the on-call person when the cron node breaks at 2am."
Here is the honest crossover, by cost and by operational reality.
What "self-host" actually means
Self-hosting an automation platform (n8n, Activepieces, Windmill) means:
- A server somewhere (VPS, Kubernetes cluster, Docker host).
- A database (Postgres or Mongo).
- Backups, monitoring, alerting, logs.
- Updates and security patches.
- TLS, DNS, redundancy.
- A bench when the database fills up at 9pm on a Friday.
You're not getting a free version of the cloud product. You're trading a subscription for ops.
What "cloud" actually means
Cloud (n8n Cloud, Make.com, Zapier, etc.) means:
- The platform runs on their infrastructure.
- Their team handles uptime, backups, scaling.
- You pay per execution, per operation, or per seat.
- Some compliance and data residency caveats apply.
- You don't get root access to the underlying machine.
You're paying for someone else to be on call.
The cost crossover
For n8n specifically (which is the most-self-hosted of the major platforms):
| Workload | n8n self-hosted | n8n Cloud |
|---|---|---|
| 1,000 executions/mo | $5/mo VPS | $20/mo (Starter) |
| 10,000 executions/mo | $5–$10/mo VPS | $20/mo (Starter) |
| 50,000 executions/mo | $20/mo VPS | $50/mo (Pro) |
| 250,000 executions/mo | $50–$100/mo, real Postgres | $120+/mo |
| 1M+ executions/mo | $200+/mo, redundant infrastructure | Custom |
On infrastructure cost alone, self-hosted is always cheaper. That's the easy part.
The harder part is total cost when you include ops time.
Ops time, the part nobody calculates
A self-hosted n8n install has these recurring tasks:
- Quarterly major-version upgrades (1–2 hours, sometimes more).
- Monthly security patches on the OS (30 min).
- Daily backup verification (5 min, usually automated).
- Monitoring setup and alert tuning (one-time 4 hours, then ongoing).
- Postgres maintenance (vacuum, index health, scale-up at growth) (occasional).
- The unplanned 3-hour debugging session twice a year when something breaks.
That's roughly 15–25 hours of engineering time per year for a small install. At a $150/hr blended rate, that's $2,250–$3,750/yr in real cost.
Compare to n8n Cloud at $20–$50/mo, which is $240–$600/yr and zero ops hours.
The crossover where self-hosting pays back is not at small scale. It's at large scale, when the cloud subscription becomes meaningful relative to the ops cost.
When self-hosting actually wins
Three real cases.
1. You'd be on a $200+/mo cloud plan otherwise. At 250k+ executions/mo, the cloud subscription starts to be larger than the ops cost. Self-hosting saves real money.
2. You have ops capacity already. A team running their own Kubernetes cluster, Postgres, observability stack. Adding n8n to that fleet is marginal effort. Standing up all of that for n8n alone is not.
3. Compliance, privacy, or data residency requires it. Healthcare, financial services, EU-only operations. The legal answer is "self-hosted." Done.
Outside these, cloud usually wins on total cost, despite the per-month bill.
When cloud wins
Most cases.
- Small to mid-size teams. Anyone under 5 engineers should be on cloud. The ops cost of self-hosting outweighs the subscription saving by 4–6x.
- Teams without a senior backend engineer. Cloud is the default unless someone on the team is excited to be the n8n DBA.
- Workloads under 250k executions/mo. Below this volume the cloud bill is small enough to not matter. Self-hosting is a hobby, not a saving.
- Workloads that need to scale to zero. Cloud handles bursts cleanly. Self-hosted requires capacity planning.
- Anyone who values evenings and weekends. Self-hosting eats both, irregularly.
The hybrid case
Some teams run cloud for production and self-host a free instance for development, testing, and personal automations. This is fine. The cost of the dev instance is trivial, and you get hands-on familiarity with the platform.
The opposite — self-hosted production with cloud "for testing" — is rare and usually a transitional state.
What we run for clients
A typical Webdimonia automation engagement ships on cloud-hosted n8n unless the client has explicit reasons to self-host. The reasoning:
- Clients aren't engineering teams. We're not standing up infrastructure they then operate.
- Cloud n8n's reliability has been good enough for production workloads since 2024.
- The handoff is cleaner. Client gets a Cloud account, we hand over keys, they're operational on day one.
When a client needs self-hosted (compliance, scale, internal infrastructure team), we ship it on Docker with proper backups and monitoring. The total project cost is 1.5–2x a comparable cloud build because of the infrastructure work.
Cost example: a real lead-routing workflow
Same workflow as before: form fill → Clearbit enrich → ICP score → Slack route → HubSpot write → outbound email. Six steps, ~500 runs/month for a small B2B service business.
| Stack | Year-one cost | Year-one ops time |
|---|---|---|
| n8n Cloud Starter | ~$240 | 0 hours |
| n8n self-hosted on a $5 VPS | $60 + $300 ops = ~$360 | 8–12 hours |
| Coded worker on Vercel | $20 + LLM API + maintenance | 4–6 hours |
At this volume, n8n Cloud is the cleanest answer. Self-hosting saves nothing. A coded worker saves money but adds development cost on the front-end.
Three questions to decide this week
- What's your monthly execution volume? Under 100k: cloud. Over 250k: consider self-hosted seriously.
- Do you have a dedicated ops engineer or platform team? Yes: self-hosted is feasible. No: cloud.
- Are there compliance or data residency requirements? Yes: self-hosted. No: cloud is fine.
If you're trying to decide whether to self-host or stay on cloud as your automations scale, send us the run volume and the workflow shape. We'll tell you within two days where the math lands for your case.