n8n Cloud vs Self-Hosted: The Real Cost for a Small Team

For most small teams without a reliable server owner, n8n Cloud is the cheaper operational choice even when self-hosting has the lower monthly invoice. Self-host Community Edition when someone already manages Linux, Docker, backups, monitoring, and recovery, or when data location and infrastructure control justify that work.

The cost at a glance

These are the prices shown on the official n8n pricing page on July 18, 2026. Prices and plan limits can change. Starter includes 2,500 workflow executions, one shared project, and five concurrent executions. Pro includes 10,000 executions, three shared projects, and 20 concurrent executions. Both list unlimited users and workflows.

What n8n Cloud actually buys

The Cloud subscription is not just a place to run the editor. n8n hosts the service, so your team does not need to provision a VPS, expose it safely to the internet, maintain Docker, or schedule application updates. This removes an operational job from a small team.

Cloud also makes collaboration easier. Starter includes one shared project, while Pro includes three and adds admin roles, global variables, workflow history, and execution search. Those features matter when more than one person builds or supports workflows. Community Edition does not include Projects or workflow and credential sharing, so a technically free server can be a poor fit for a team that expects clean access boundaries.

There are still limits. Cloud pricing is based on complete workflow executions, and retained execution data is constrained by plan. The current pricing table lists maximum execution-log retention of seven days on Starter and 30 days on Pro. Cloud also fixes the hosting location for standard hosted plans. n8n currently says hosted data is stored on servers in Frankfurt, Germany.

What self-hosted Community Edition costs

The Community Edition includes almost the complete core feature set, but the official feature list excludes Projects, sharing, environments, SSO, external secrets, external binary storage, log streaming, multi-main mode, and Git version control. Registered Community Edition adds folders, debug-in-editor tools, and custom execution data, but it does not turn the instance into the Business plan.

The first invoice is usually the VPS. DigitalOcean currently lists a basic 1 GB Droplet at $6/month and 2 GB at $12/month. Its weekly backup option costs 20% of the Droplet price, while daily backups cost 30%. That produces a simple infrastructure range like this:

The 2 GB example is a planning starting point, not an n8n sizing guarantee. Workflow concurrency, Code nodes, large payloads, AI tasks, binary data, execution retention, and PostgreSQL all change the requirement. Hetzner and other providers may price similar servers differently by region. Provider prices exclude the value of your time and may exclude tax, IPv4, object storage, or other services.

The hidden self-hosted bill

Updates

n8n publishes minor releases frequently. Its self-hosted update guidance recommends updating at least monthly, reading release notes for breaking changes, and testing before production. Current Docker documentation lists stable version 2.26.8 as of this review. A safe update therefore needs a backup, a maintenance window, a smoke test, and a rollback path.

Backups and credentials

A workflow JSON export is useful, but it is not a complete instance backup. n8n stores workflows, credentials, and execution data in SQLite by default or in PostgreSQL when configured. The persistent .n8n directory also contains important data such as the encryption key. n8n uses that key to encrypt credentials before storing them in the database. The self-hosted n8n backup and restore guide turns those parts into a tested recovery sequence.

A practical recovery plan protects the database, the persistent n8n volume or explicit encryption key, the deployment configuration, and any binary-data location. It also proves that a restore works on a separate instance. A backup that has never been restored is only a hope.

Security and monitoring

Self-hosting means owning operating-system patches, Docker exposure, HTTPS, firewall rules, account access, database health, disk usage, and alerts. n8n's own Docker guide says self-hosting requires server, container, scaling, security, and application knowledge, and recommends Cloud for people without that experience because mistakes can cause data loss, security problems, and downtime.

This is not a reason to avoid self-hosting. It is a reason to price the operator. If maintenance and verification take one hour per month and that person's time is worth $30/hour, the labor assumption adds $360 per year. Two hours per month adds $720. Use your real internal rate rather than treating this time as free.

When self-hosting wins

• You already operate servers. n8n becomes another monitored container instead of a new discipline.
• You need control over data location. You choose the region, database, retention, network, and backup destination.
• You need self-host-only capabilities. Bash execution and custom nodes can justify the infrastructure.
• Your workload is high or unusual. You can size compute and storage around the workflow instead of a standard hosted plan.
• You have a tested recovery owner. One named person can update, restore, and troubleshoot the instance.

My self-hosted n8n deployment case shows what that responsibility looks like in practice: Docker, PostgreSQL, Cloudflare, persistent storage, monitoring, and backups, not just one container command.

When n8n Cloud wins

• No one owns infrastructure. The team needs workflows, not a second job maintaining the workflow server.
• The first automation matters to revenue. A predictable platform bill is easier to defend than an unplanned recovery incident.
• Several people need access. Shared projects and collaboration are part of the requirement, not optional extras.
• The execution allowance fits. Starter or Pro covers the expected runs with room for retries, testing, and growth.
• You want the fastest start. The team can build the workflow without first deploying a public production service.

If you are still deciding whether n8n fits the process at all, start with the plain-English n8n guide for small businesses. If the choice is between automation platforms, the Zapier vs Make vs n8n pricing comparison explains how each one counts usage.

Do not ignore the self-hosted license

Community Edition is source-available under n8n's Sustainable Use License, not a conventional open-source license. The official license FAQ allows internal business use, personal use, and consulting around n8n. It does not allow white-labeling n8n or hosting it and charging customers for access without a separate agreement.

A five-minute decision rule

1. Estimate complete workflow executions for a normal month and a busy month.
2. List how many people need to build, inspect, or support workflows.
3. Decide whether Projects, sharing, SSO, environments, or version control are required.
4. Price the server, backups, storage, domain, and monitoring.
5. Add real operator time for updates, testing, incidents, and restores.
6. Name the recovery owner. If no one accepts the job, choose Cloud.

For a one-person technical operation, Community Edition can be excellent value. For a small team with no infrastructure owner, Cloud Starter is often cheaper than one avoidable incident. Cloud Pro becomes the practical choice when production volume and collaboration outgrow Starter. Self-hosted Business is a different buying decision for companies that need paid governance features while keeping the infrastructure under their control.

Sources checked

• n8n plans and pricing
• n8n Community Edition features
• n8n Docker installation and self-hosting prerequisites
• n8n self-hosted update guidance
• n8n credential encryption key guidance
• n8n Sustainable Use License FAQ
• DigitalOcean Droplet and backup pricing