The quick version
If you want to start fast with no setup and you're running under 2,500 executions per month, n8n Cloud is the right call. If you're running several active workflows, have someone on your team who can handle basic Linux commands, or process client data you'd rather not hand off to a third party, self-hosting is worth the initial setup time and saves real money at scale.
| n8n Cloud | Self-Hosted | |
|---|---|---|
| Starting cost | $20/month (Starter) | ~$6–15/month (VPS) |
| Setup time | Minutes | 1–4 hours |
| Technical skill needed | None | Basic Linux / Docker |
| Executions limit | 2,500/month (Starter) | Unlimited |
| Updates | Automatic | Manual |
| Data stays on your server | No | Yes |
| Support | Included | Community |
n8n Cloud — who it's actually for
n8n Cloud handles everything: hosting, updates, backups, uptime. You log in and build workflows. Nothing to configure on a server, no Docker, no SSH. For a lot of businesses, that's the correct trade — pay a monthly fee and avoid infrastructure entirely.
The plan tiers as of early 2026:
- Starter — $20/month: 2,500 executions/month, 5 active workflows
- Pro — $50/month: 10,000 executions/month, unlimited active workflows
- Enterprise — custom pricing
2,500 executions sounds like a lot until you work through the math. A single workflow polling for new data every 5 minutes runs 12 times per hour, 288 times per day, 8,640 times per month. One active polling workflow eats your entire Starter plan. Run two, and you're already over — before any workflows actually do meaningful work in response to those triggers.
The polling math: 1 workflow polling every 5 min = 8,640 executions/month. At Starter, that leaves you 0 headroom for actual trigger-and-do workflows. The Pro plan's 10,000 limit handles this better, but you're now at $50/month.
n8n Cloud is the right choice if you're just starting out and want to validate whether n8n fits your workflow before committing infrastructure time, or if you have no one on your team who wants to manage a server. The zero-maintenance value is real.
Self-hosted — when it makes sense
"Self-hosted" sounds more intimidating than it is. In practice it means: a VPS running Docker, n8n in a container, Nginx or Caddy as a reverse proxy, and a domain pointed at it. The initial setup takes 1–4 hours depending on your familiarity with the command line. After that, day-to-day operation is no different from using n8n Cloud — you just log into your own URL instead of app.n8n.cloud.
Self-hosting makes sense when:
- You're running 5 or more active workflows (the execution limit math stops working in your favor on Cloud)
- You have a developer, a technically comfortable person on staff, or you're comfortable with a terminal yourself
- You process sensitive client data — medical records, financial data, legal documents — and want it on infrastructure you control
- You're building for a client and want to keep the infrastructure cost low long-term
Realistic hosting options:
- DigitalOcean Basic Droplet — 1GB RAM, 1 vCPU, 25GB SSD. $6/month. Handles n8n fine for most SMB workloads. Step up to $12/month (2GB) if you're running 10+ workflows with heavy data processing.
- Railway $5/month on the Hobby plan. Good developer experience, easy deploys. Slightly less control than a full VPS but easier to get started.
- Render Free tier works for very low volume. Paid plans start at $7/month. The free tier spins down after inactivity, which breaks scheduled workflows — use a paid plan for production.
- Hetzner European-based. Similar pricing to DigitalOcean, often slightly cheaper. Worth considering if your clients' data should stay in the EU.
You'll also need a domain (or subdomain) pointed at the server — something like n8n.yourdomain.com. Caddy makes the TLS certificate automatic. The whole stack, once running, is stable and low-maintenance.
"Self-hosted n8n on a $6/month Droplet is what we run for clients with significant workflow volume. It's stable, fast enough for any SMB use case, and the infrastructure cost is effectively a rounding error."
The cost math at scale
Here's a concrete example. A small service business with 3 active workflows — one polling for new form submissions, one polling the CRM for new contacts, one checking for overdue invoices — each running every 5 minutes:
At 26,400 executions/month, you're on n8n Cloud Pro at $50/month. That's $600/year. Self-hosted on DigitalOcean costs $6/month — $72/year. The $528 annual difference isn't dramatic, but it compounds: over 3 years that's $1,584 in pure platform cost savings, plus you're not subject to n8n raising their Cloud pricing.
The break-even for self-hosting is roughly 3–4 months if you have someone who can handle the setup. If you're paying a developer for an hour or two of setup time, it's still break-even within 6 months.
12-month comparison: n8n Cloud Pro = $600. Self-hosted DigitalOcean = $72. Difference: $528/year — before accounting for any future price changes to n8n's Cloud plans.
What we use at Aplos AI
For clients where workflow volume justifies it, we build on self-hosted n8n. The DigitalOcean setup is reliable, we manage the updates, and clients aren't paying Cloud platform costs month after month on top of our build fee.
For clients who want zero maintenance responsibility — no thinking about servers, no updates, nothing — we build on n8n Cloud. Specifically the Pro plan, because the Starter execution limits cause problems faster than most businesses expect.
The build process is identical either way. A workflow built on n8n Cloud looks exactly the same as one built on a self-hosted instance. Moving between them is an export/import operation.
If you're working with us on an n8n build, we'll recommend the right hosting option based on your expected execution volume and whether you have someone to handle basic server maintenance.
What about Make and Zapier?
Neither Make nor Zapier has a self-hosted option. If you're on Zapier and run into their execution pricing at scale, you're stuck paying it. There's no alternative tier that removes the per-task cost.
n8n's self-hosted option is one of the main reasons it's the right choice for businesses with high automation volume. If cost control at scale matters, it's the only serious workflow tool with this option. We covered the full comparison in our n8n vs Make vs Zapier breakdown.
How to decide
Not sure which setup makes sense for your workflows? We've built on both and can tell you exactly which direction fits your situation — execution volume, team capability, data requirements, all of it. Free audit, 30 minutes.
Get a Free Audit →The bottom line
n8n Cloud is a better starting point. Self-hosting is a better long-term choice once you have enough workflow volume to feel the execution limits. The decision isn't permanent — migrating from Cloud to self-hosted is a 1–2 hour project, not a rebuild.
If you're just starting and have no idea how many executions you'll need, start on Cloud Pro ($50/month) rather than Starter. The Starter limits hit faster than most people expect, and the frustration of throttling active workflows isn't worth the $30/month difference while you're still figuring out your automation stack.