When n8n is the right orchestrator
n8n earns its place when a workflow crosses several systems, has to run somewhere you control, and needs to be readable by someone who did not build it. Because it self-hosts, it suits teams with a data-residency requirement or a compliance review that will not clear a US-hosted SaaS orchestrator. The trade is operational: a self-hosted instance is infrastructure you now own, with upgrades, backups and queue capacity to plan. For a team already running containers that cost is marginal; for a team without an ops function it is the main reason to choose a managed platform instead, and we say so during the audit rather than after.
What we build differently
The default way to build in n8n is one long chain of nodes that works until an API returns something unexpected, at which point it stops halfway with half the systems updated. We build the recovery path first: every external call has an explicit failure branch, partial work is either idempotent or reversible, and anything that could not complete lands in an error queue with enough context for a person to finish it by hand. AI steps are bounded to a single decision with a defined output shape, never left to compose an action freely, because a non-deterministic step in the middle of a chain of writes is the hardest kind of failure to unpick.
Compare n8n cloud and self-hosted total cost
As checked on 15 October 2026, n8n lists its Cloud Pro plan at €50 per month when billed annually for 10,000 workflow executions; an execution is one complete workflow run, regardless of how many steps it contains. Self-hosted Community Edition has no n8n subscription fee, but that is not a zero-cost deployment. Compare cloud subscription and any external services with self-hosted infrastructure, storage, backups, monitoring, maintenance hours and incident cover. A useful estimate is: self-hosted monthly cost = infrastructure + backup and monitoring services + maintenance hours × loaded hourly cost + incident cover. Use your measured successful workflow runs and failure/retry volume; do not compare only per-step task counts.
How to measure the pilot
A pilot is accepted against the current process, not an industry promise. Agree the sample, baseline and owner before launch, then review the same measures after the workflow has handled real cases.