n8n Community vs Cloud Starter 2.5K executions: when indies should pay

When indies automate workflows with n8n, two paths show up: run Community Edition yourself, or buy Cloud. The real math is execution count, shared projects, and whether you will maintain the host. This page does not reopen n8n versus Zapier versus Make budgets. It freezes Cloud Starter’s 2.5K workflow executions wall and when to pay for hosting or move to Pro using n8n.io/pricing and Community Edition docs as of 2026-10-01. Euro prices and annual toggles follow the live page.

What the two low-cost paths are

Pricing points to a standard self-hosted Community Edition on GitHub—the path where you trade ops work for not paying a cloud execution SKU. You gain control and potentially lower cash cost; you also own backups, upgrades, monitoring, and incidents. Cloud Starter is the hosted path: on the observation day the annual billing display was about €20/month for 2.5K workflow executions with unlimited steps, one shared project, five concurrent executions, 1,600 Assistant credits/month, forum support, and hosting by n8n. The page stresses paying for full executions rather than per step, unlike some task/step-priced automation products.

Ask first whether you are short on cash or on ops time. If you already run Docker/VPS calmly, Community can win. If automation touches revenue and you refuse midnight disk repairs, Starter fees buy sleep.

How to read Starter’s 2.5K executions

Two point five thousand workflow executions are the core cloud budget. Dense polling, hourly syncs, and per-form workflows jump faster than intuition. Label each production workflow with estimated daily runs and multiply by thirty before you celebrate headroom. Merge triggers when possible; prefer events over overly frequent cron; batch instead of one-execution-per-row. One shared project means production automations need a clear project boundary rather than endless scattered secrets.

Five concurrent executions cover many indie integrations; short bursts of parallelism are when you peek at Pro’s higher concurrency. Assistant credits are a separate pool—do not conflate them with workflow executions.

When to buy Starter, upgrade to Pro, or keep self-hosting

Buy Starter if you want hosted reliability, refuse to babysit database upgrades, and expected volume fits inside 2.5K. Upgrade to Pro—about €50/month on the observation-day annual display—if volume trends toward 10K, you need up to three shared projects, higher concurrency, or longer insights. Keep self-hosting if backups and monitoring are real, volume swings but cash is tight, and you accept owning incidents. You can also burst onto Cloud for a campaign month and reassess Community afterward.

Do not pay because cloud sounds professional, and do not stay free because open source sounds virtuous while ignoring ops hours. Price your own hours once; the slogan debate usually ends.

Budget executions before go-live

List production workflows: trigger, average daily runs, whether retries multiply counts. Inspect execution history for error loops burning quota. Add idempotency and dedupe on webhook flows so client replays do not become execution storms. When separating staging and production, watch Cloud project caps; on self-host, watch environment isolation and secrets. Write an execution budget into the automation README so new cron jobs require arithmetic first.

If you are also evaluating Zapier or Make, finish the internal n8n path math before cross-vendor comparisons. Mixing everything into one emotional “who is cheapest” thread hides self-host ops cost.

Keep this separate from three-way comparisons

Toolvori already publishes n8n versus Zapier versus Make. That answers cross-product choice. This tutorial answers only n8n’s Community versus Cloud execution quotas. Pin 2.5K/10K and project counts in your handbook with a date. When someone says “n8n is free and unlimited,” ask whether they mean self-host or Cloud and whether retries are counted.

Upgrade triggers: two weeks of approaching 2.5K after trigger hygiene, ops time exceeds Starter fees, or Pro’s project/concurrency features map to the blocker. In week one after paying, connect usage review to Friday ops so the subscription does not become shelfware. Re-check euro prices and monthly/annual toggles on the live pricing page before checkout.