n8n Self-Hosted vs. Cloud: The April 2026 Calculus

Published April 30, 2026 by Pondero Editorial

TL;DR

The “self-host n8n because it’s free” reflex is wrong more often than it’s right. As of April 2026, the right question isn’t infrastructure cost; it’s whether your team will own the operational tax. For most ops teams under ~10,000 executions/month, n8n Cloud is the cheaper option once you price your time honestly. For teams with data residency requirements, very high volume, or workflows tightly coupled to internal services, self-hosted still wins clearly.

The decision matrix

Dimension	Self-hosted n8n	n8n Cloud
Sticker price	Free (license)	From $20/mo
Real cost	Hosting + ops time + monitoring + upgrades	Subscription + usage tier
Data residency	Wherever you put it	Vendor-managed regions
Time to first workflow	Half-day (Docker) to a week (k8s)	Minutes
Best fit	Engineering-led, infra-fluent teams	Ops-led, automation-first teams
Hidden tax	Upgrade fatigue, on-call surface area	Less control over scaling cliffs
Where it bites	Forgotten upgrades → drift, security holes	Per-execution pricing at high volume

For the broader category context, our best AI automation tools guide places n8n alongside Zapier and Make.

When self-hosted is unambiguously the right call

Data residency or compliance forces it (HIPAA workflows in a private VPC, EU public-sector clients, etc.).
Volume is high enough that Cloud’s execution tiers stop being economical, typically when monthly executions push past tens of thousands and most workflows are simple, frequent triggers.
Workflows reach into internal services that would require punching new holes through your network to expose to a SaaS.
You already have a platform team running container workloads. The marginal cost of adding n8n is small.

When Cloud is the right call (and most teams underestimate this)

Ops-led teams without dedicated platform engineering. Self-hosting n8n is straightforward to start and surprisingly expensive to keep healthy. Upgrades, secrets rotation, backup/restore, and monitoring all cost real time.
Workflows are mostly outbound to SaaS APIs. If n8n is calling Slack, HubSpot, Stripe, and a few HTTP endpoints, the network argument for self-hosting is weak.
You’re in the validation phase. Cloud lets you commit to n8n with hours, not days, of setup. Migrate later if the math shifts.

The honest cost equation

Most “we’ll just self-host” calculations miss three line items:

Upgrade tax. n8n ships frequently; staying current is a recurring half-day-per-quarter cost at minimum, plus regression testing.
Backup and DR. Workflow JSON, credentials, and execution logs need a real backup story. “It’s in Postgres” isn’t one.
On-call surface. A self-hosted automation platform that runs your billing reconciliation is a Tier-1 system. Treat it that way or accept the risk.

If those three line items are unstaffed, Cloud usually wins on total cost even before you factor in vendor support.

The migration question

If you’re already on Cloud and wondering whether to move: the right trigger is usually a specific, named pain, like a residency requirement landing in a contract, a workflow class that needs a private network, or a sustained execution-volume cliff. Don’t migrate on vibes. The portability is real (workflows export cleanly), but the ops surface area is the cost.

Where Cloud’s pricing model bites

n8n Cloud’s tiers scale on executions. The cliff most teams hit is when a single high-frequency trigger (every-minute schedule, busy webhook) blows through the included executions on a mid-tier plan. Audit your workflows for “always-on” triggers before signing up; a single mis-configured cron is the most common surprise on the bill.

Verdict

In April 2026, default to n8n Cloud unless you have a specific, named reason to self-host. The total cost of ownership math has shifted in Cloud’s favor for the median ops team, not because hosting is hard, but because keeping a Tier-1 automation system healthy is a job, and most teams don’t have the slack to take it on.

Try n8n Cloud: the fastest way to validate whether it fits your workflows.