Short answer: Choose n8n Cloud for managed operations and fast setup. Choose self-hosting for direct control of the host, network, and release process.

What does n8n Cloud remove?

A managed service removes much server, upgrade, TLS, and process work. The team can focus on workflows and credentials. It still needs owners for access, data, failures, and cost limits.

Check plan limits and supported integrations first. A managed service still needs retries, idempotency, and alert ownership.

What does self-hosting add?

Self-hosting gives control over the host, network, database, backups, and release timing. It also makes the team responsible for updates, uptime, restore tests, and incident response.

Count operating hours, not only the server bill. A cheap host costs more when nobody owns upgrades or recovery.

How should data location affect the choice?

List the credentials, workflow data, execution records, and files that the automation handles. Confirm where each environment stores them. Confirm who can administer the service.

Document retention and deletion rules. Compare the managed plan with the controls your team can run directly.

What is a sensible decision record?

Record workflow volume, latency needs, integration limits, data rules, owner, and budget. Review the choice after a pilot.

For self-hosted requirements, use the production checklist. For a basic installation path, see the Docker installation guide.