OPERATING MODEL
n8n Cloud vs self-host: who owns the pager?
Self-hosting changes control, security work and recovery responsibility. It does not merely remove a subscription line.
Choose n8n Cloud when managed operation meets the requirement. Self-host only when deployment control is a Must and a named person can operate it.
START WITH RESPONSIBILITY
Control and maintenance arrive together
Cloudn8n operates the hosted service; your team owns workflows, credentials and process failures.
Self-hostYour team also owns deployment, upgrades, backups, availability, security and recovery.
KeepUse the current method when neither route has an operating owner.
CHOOSE CLOUD IF
Managed operation is a feature
- The team wants n8n without maintaining infrastructure.
- Published cloud plan conditions meet data and governance needs.
- Fast setup matters more than deployment control.
CHOOSE SELF-HOST IF
Control solves a requirement
- Network placement or deployment control is a Must.
- The team already operates backups, monitoring and upgrades.
- License and edition limits have been reviewed for the intended use.
CURRENT OFFICIAL MODEL
Community, Business and Enterprise are not the same promise
| Community Edition | A standard self-hosted edition is available; compare missing paid features before treating it as equivalent. |
|---|---|
| Cloud plans | Current pricing is based on monthly workflow executions, regardless of step count. |
| Paid self-hosted | Business and Enterprise add collaboration, governance or support conditions; confirm current pricing and licensing. |
Infrastructure cost, staff time and incident recovery remain outside the software price.
Self-hosting is premature when…
- No one owns patching and restore tests.
- The requirement is “more control” with no control named.
- A laptop under a desk is being described as high availability.
- The process itself is still changing weekly.
SIMPLER ROUTE