Self-host n8n or use n8n Cloud: how to choose without adding operational burden

When does n8n Cloud provide the clearest value?

n8n Cloud suits teams that want to validate an idea or move lower-risk workflows into production without building another operational platform. The provider handles the underlying infrastructure; your team still owns business logic, credentials, access, output data, and integration failures.

Cloud is especially useful for small teams without on-call coverage, relatively predictable usage, and target systems that can be reached securely over the internet. The subscription buys back deployment, upgrade, and infrastructure-response time. At the time of verification, n8n Cloud pricing is based on monthly workflow executions; practical limits also involve concurrency, execution history, and stored execution data. Pricing and limits can change, so verify the current pricing page before budget approval.

Self-hosting is justified when workflows must connect to databases, ERPs, or services available only on private networks; policies require control over data location; custom nodes, system commands, or specialized runtime settings are needed; or resources must be tuned directly for the workload. n8n also states that self-hosting requires knowledge of servers, containers, resources, security, and scaling, and recommends it for experienced users.

Control does not automatically create reliability. A running container is not a production platform. At minimum, plan for a backed-up PostgreSQL database, a stable credential-encryption key, TLS, restricted editor access, secret management, execution-data retention, tested upgrades, error monitoring, and recovery procedures. For critical workflows, define RTO, RPO, incident ownership, and safe replay before go-live.

A scoring framework before you choose

Score each criterion from zero to three and attach evidence. If data residency, private connectivity, or runtime customization is mandatory, self-hosting may win even at a higher cost. If most points reflect fast delivery, limited operations capacity, and standard needs, prefer Cloud.

1. Data: Do payloads contain PII, trade secrets, or data subject to residency constraints?
2. Connectivity: Must workflows reach private systems that should not expose public endpoints?
3. Capability: Who owns upgrades, backups, restores, CVEs, and after-hours incidents?
4. Load: What execution volume, peak concurrency, payload size, and duration are expected?
5. Governance: What level of SSO, RBAC, audit, Git, environments, or SLA is required?
6. Customization: Do you genuinely need custom nodes, commands, or images?
7. Exit: How quickly can you export workflows, rotate credentials, and move webhooks?

Select two or three representative workflows: one scheduled job, one webhook, and one flow with a private integration. Run them for 30 days and record execution volume, peak concurrency, log storage, failure categories, recovery time, and operational hours. Do not use a financial workflow or a sensitive write path as the first experiment.

For Cloud, inspect quotas, retention, data region, credential controls, and connectivity limits. For self-hosting, rehearse database restore, staged upgrades, version rollback, worker failure, database saturation, and encryption-key rotation. In either model, write workflows need idempotency keys, unique constraints, or upserts so retries do not duplicate records. Choose from observed TCO and risk, not because a server appears inexpensive.

Is self-hosted n8n free?

Community Edition can be self-hosted without a license fee under n8n's license, but infrastructure, operations, and risk still cost money. Review the Sustainable Use License if n8n will form part of a commercial service.

Is n8n Cloud safer than self-hosting?

The deployment model alone does not decide security. Cloud reduces the platform infrastructure you manage; self-hosting increases control while transferring configuration, patching, and monitoring responsibility to your organization.

Where is n8n Cloud data stored?

The official pricing page currently states that hosted-plan data is stored in Frankfurt, Germany. If location is a contractual or legal requirement, confirm it directly before purchase because details can change.

Can we move from Cloud to self-hosting later?

Workflows can be exported and imported, but credentials, webhook URLs, execution history, environment variables, and plan-specific capabilities need a separate migration plan. Test the exit process before many critical workflows accumulate.

Is Kubernetes the default way to self-host n8n?

No. For small workloads, a simpler and well-backed-up design can be easier to operate. Kubernetes makes sense when the organization already has a K8s platform, observability, secrets, backup practices, and accountable operators.