n8n Self-Hosted vs Cloud Cost: Full 2025 Breakdown
Quick answer
n8n Cloud starts at $20/month (Starter) and $50/month (Pro), with costs scaling by execution volume. Self-hosted infrastructure runs $5–$40/month, but setup labor, maintenance, and risk exposure add $25–$60/month in true all-in cost for most SMBs. Cloud wins at low volumes; self-hosted becomes cost-effective above roughly 50,000 monthly executions with a technical operator on the team.
What Does n8n Actually Cost? The 30-Second Answer
n8n Cloud starts at $20/month on the Starter plan and rises to $50/month on Pro, with execution limits driving the step-up. Self-hosted on a budget VPS like Hetzner or DigitalOcean costs as little as $5/month in raw infrastructure — but that number is misleading without accounting for setup time, monthly maintenance, and the skill required to run it safely.
The true cost gap only appears when you apply LEVRYO's Total Ownership Cost framework — Infrastructure, Labor, Risk, and Opportunity (ILRO). Raw server pricing is one input. Your team's technical capacity, execution volume, and tolerance for downtime are the others. A solo founder with no DevOps background who chooses self-hosted to save $20/month may spend ten times that in lost hours during the first quarter alone. Conversely, a technical team running 50,000+ workflow executions per month will find Cloud pricing uncompetitive fast. Neither deployment is universally cheaper. The right answer depends on your execution volume, who is on your team, and where your business is headed in the next 12 months. This breakdown gives you the numbers and a decision rubric to reach a defensible answer for your situation. For a broader look at automation strategy, see the LEVRYO automation resource hub.
n8n Cloud Pricing: What You Pay and What You Get
n8n Cloud pricing is structured around two primary self-serve tiers — Starter at $20/month and Pro at $50/month — with an Enterprise tier that is custom-quoted. Each tier sets limits on monthly workflow executions and, in the case of Starter, on the number of active workflows you can run simultaneously.
The Starter plan gives you 2,500 workflow executions per month and a cap of 5 active workflows. For a small team running a handful of automations — a lead capture flow, a CRM sync, a weekly report — that ceiling is workable. Growth changes the math quickly. The Pro plan raises the execution limit to 10,000 per month and removes the active workflow cap, making it the practical choice for teams with more than a few live automations. When you exceed your monthly execution limit, n8n can pause workflows or apply overage charges depending on your plan terms — a surprise that catches growing SMBs off guard if they are not monitoring usage weekly. Enterprise pricing covers SSO, audit logs, dedicated support, and custom execution volumes. According to the n8n official pricing page, these tiers are designed to scale with team size and compliance requirements. Cloud also includes automatic updates, managed infrastructure, and built-in security — value that is easy to overlook when comparing sticker prices alone.
n8n Self-Hosted Pricing: Infrastructure, Setup, and Ongoing Labor
n8n's Community Edition is free software, licensed under the Sustainable Use License. Free to download, free to run. What you pay for is everything around it: the server, the database, backups, SSL, and the human time required to keep it running reliably.
A minimum viable deployment — one virtual CPU, 1 GB RAM — on Hetzner or DigitalOcean costs roughly $4–$6/month. That setup is fine for testing but fragile in production. A production-grade configuration with 2 vCPUs, 4 GB RAM, a managed PostgreSQL database, and automated backups runs closer to $20–$40/month in infrastructure, depending on provider and region. According to the n8n self-hosting documentation, a queue-mode setup with a separate worker process is recommended for reliability at scale, which adds further infrastructure cost. SSL certificates, domain management, and uptime monitoring tools like UptimeRobot add small but real overhead.
Labor is where the hidden cost lives. Initial setup takes 4–10 hours for someone comfortable with Linux and Docker. Ongoing maintenance — updates, log reviews, backup checks, occasional debugging — runs 1–3 hours per month. At a conservative internal rate of $75/hour, a 6-hour setup equals $450 in one-time labor. Amortized over 12 months, that adds approximately $37/month to your true cost — before a single hour of ongoing maintenance. A team logging just 2 maintenance hours per month at that same rate adds another $150/month. The n8n Sustainable Use License on GitHub clarifies what the Community Edition permits, which is worth reviewing before committing to self-hosted at scale.
Head-to-Head Cost Table: Self-Hosted vs Cloud Across 3 Business Sizes
Three SMB profiles illustrate where Cloud and self-hosted economics diverge. The crossover point — where self-hosted total cost of ownership drops below Cloud — does not appear until execution volumes climb well past 10,000 per month and a technically capable operator is already on the team. At low volumes, Cloud wins on total cost. At high volumes, self-hosted wins decisively.
| Business Profile | Monthly Executions | Cloud Plan Cost/mo | Self-Hosted Infra/mo | Self-Hosted Labor/mo | 12-Month Total (Cloud) | 12-Month Total (Self-Hosted) |
|---|---|---|---|---|---|---|
| Solo operator (low volume) | ~1,500 | $20 (Starter) | $6 | $150 (2 hrs @ $75) | $240 | $2,322 (incl. $450 setup) |
| 10-person team (medium volume) | ~8,000 | $50 (Pro) | $25 | $150 (2 hrs @ $75) | $600 | $2,850 (incl. $450 setup) |
| 25-person team (high volume) | ~55,000 | $200+ (Enterprise est.) | $40 | $225 (3 hrs @ $75) | $2,400+ | $3,690 (incl. $450 setup) |
The solo operator profile is the clearest case for Cloud. At 1,500 executions per month, the Starter plan at $20/month covers everything. Self-hosted infrastructure costs only $6/month, but labor flips the equation hard — $150/month in maintenance plus the amortized setup cost produces an annual total that dwarfs the Cloud equivalent. The 10-person team sits in a similar position. Medium execution volume keeps Cloud Pro competitive, and the labor overhead of self-hosting still outweighs the infrastructure savings. The 25-person team at 55,000 executions per month tells a different story. Enterprise Cloud pricing climbs steeply, and a team at this size likely already has someone capable of managing infrastructure. Self-hosted becomes the rational choice — but only because volume justifies the labor investment and technical capacity exists in-house.
The Hidden Cost Factors Most Comparisons Miss
LEVRYO's ILRO framework — Infrastructure, Labor, Risk, Opportunity — surfaces four cost dimensions that raw pricing comparisons ignore. Infrastructure and Labor are the ones most people calculate. Risk and Opportunity are the ones that determine whether the math holds in practice.
Risk cost is concrete. A self-hosted outage during a critical automation — invoice processing, a time-sensitive client notification, a payroll trigger — has a quantifiable business impact. Cloud deployments carry an uptime SLA that transfers that risk to n8n. Self-hosted operators carry it themselves, and without active monitoring and a tested recovery playbook, the exposure is real. Opportunity cost cuts just as deep for lean teams. Every hour spent on server updates, SSL renewals, and log reviews is an hour not spent on product, sales, or customer work. For a solo operator or a 3-person team, that trade-off is rarely worth the infrastructure savings.
Version lock risk is a failure mode that generic comparisons miss entirely. Self-hosted operators who skip n8n updates — often because updates require downtime or testing — accumulate technical debt. Minor version gaps become major migration efforts. A team that falls several versions behind may face breaking changes in node APIs, requiring significant rework to upgrade safely. That hidden migration cost compounds over time and never appears in a month-one infrastructure comparison.
Compliance overhead adds another layer for regulated industries. Healthcare and finance teams may require audit logs, data residency controls, and access management documentation. n8n Cloud Enterprise includes these features. Self-hosted implementations require manual setup and ongoing maintenance of equivalent controls — an underestimated cost that can easily exceed the price difference between Cloud tiers. Vendor dependency risk cuts both ways: Cloud users are exposed to n8n pricing changes; self-hosted users are exposed to their own infrastructure failures and the ongoing cost of keeping pace with the project's development.
Which Option Wins for Your SMB? A 5-Question Decision Rubric
The LEVRYO Deployment Fit Rubric produces a scored recommendation — Cloud or Self-Hosted — based on five questions about your team, your volume, and your operational requirements. Answer each question honestly. The score tells you where the economics and risk profile align for your situation.
- Does your team include someone comfortable with Linux and Docker? A confident yes — someone who has deployed containerized applications before — earns 2 points toward Self-Hosted. A maybe or no earns 0.
- Will you exceed 10,000 workflow executions per month within 6 months? Growth projections matter here. A clear yes based on current trajectory earns 2 points toward Self-Hosted.
- Is uptime SLA critical to daily revenue? If an automation outage would directly block invoicing, order fulfillment, or client-facing processes, score 2 points toward Cloud. Managed infrastructure with a published SLA removes that operational risk from your plate.
- Is your team fewer than 5 people with no dedicated operations role? Small teams without a designated technical operator absorb maintenance cost invisibly — it comes out of founder or developer time. Score 2 points toward Cloud if this describes you.
- Do you need data residency or on-premise compliance? Regulatory requirements that mandate data staying within a specific geography or on your own infrastructure make self-hosted the only viable path. Score 2 points toward Self-Hosted.
Score interpretation: 0–4 points toward Self-Hosted means Cloud is the right starting point. Lower operational risk, predictable pricing, and zero maintenance overhead outweigh the cost savings at this profile. A score of 5–10 points toward Self-Hosted means the investment is justified — your team has the capacity, the volume supports the economics, or compliance requirements remove Cloud as an option. Use this rubric as a starting point, not a final verdict. Revisit it as your execution volume and team composition change.
Frequently Asked Questions: n8n Self-Hosted vs Cloud Cost
Can I start on n8n Cloud and migrate to self-hosted later?
Yes. n8n workflows are portable — you export them as JSON files and import them into any self-hosted instance. The migration process itself takes a few hours of focused work, but credentials and environment variables must be reconfigured manually on the new instance. Most SMBs find it practical to start on Cloud, validate their workflows, and migrate to self-hosted once execution volume makes the economics compelling.
Does n8n Cloud charge per workflow or per execution?
n8n Cloud charges primarily by workflow execution count, not by the number of workflows you build — on Pro and above. The Starter plan adds a cap of 5 active workflows alongside the execution limit. Once you exceed your monthly execution count, n8n may pause workflows or apply overage charges depending on your plan terms. Monitoring your execution usage weekly prevents unexpected downtime or billing surprises.
Is n8n self-hosted really free?
The n8n Community Edition software is free under its Sustainable Use License, but hosting is not free. You will pay for a VPS, a managed database, backups, and SSL management. Add setup labor and ongoing maintenance at a realistic hourly rate, and the true monthly cost for most SMBs lands between $25 and $60 per month all-in — sometimes higher depending on team labor rates and infrastructure choices.
What happens if I exceed my n8n Cloud execution limit?
When execution limits are reached on n8n Cloud, workflows may be paused until the next billing cycle or until you upgrade your plan. n8n does not silently drop executions without notification, but automation downtime carries real business consequences for teams that depend on those workflows for revenue-critical processes. Reviewing your execution usage weekly — especially during growth phases — is strongly recommended.
Can self-hosted n8n connect to the same integrations as n8n Cloud?
Yes. Self-hosted n8n has access to the same 400+ native integrations as the Cloud version, including HubSpot, Google Sheets, Slack, and Stripe. The practical difference is that community-sourced nodes may require manual installation on self-hosted instances, while Cloud handles node availability automatically. For most standard integrations, behavior is identical across both deployment options.