n8n Cloud or Self-Hosted? A Developer’s Decision Checklist

Short answer: start with n8n Cloud when automation is the product you want to build. Self-host when infrastructure control is itself a requirement, and only after you have priced the operational work.

Commercial note: links through loke.dev/go are measured as outbound clicks. This comparison currently uses a direct n8n link and earns no commission. If that changes, the relationship label and disclosure will change.

If you want to test the managed route first, open n8n Cloud. Keep reading before paying if local network access, custom nodes, or strict infrastructure control are central to the project.

The choice is really managed service versus an operations job

Both options run the same kind of visual workflows. The difference is who owns everything around them. With Cloud, n8n operates the service. With a self-hosted instance, you own deployment, upgrades, TLS, backups, monitoring, database health, incident response, and recovery testing.

That makes the cheapest server price a poor comparison. A small virtual machine may cost less than a Cloud subscription, while still being more expensive after one failed upgrade or a few hours of monthly maintenance.

Use total cost, not server cost

Use this simple monthly model:

Self-hosted total = server + database + backups + monitoring + maintenance hours × the value of your time

An illustrative example: an €8 server plus 30 minutes of work valued at €50 per hour is already €33 per month before backups or monitoring. Change those numbers to match your situation. The point is to count the work instead of pretending it is free.

As checked on 24 July 2026, n8n’s pricing page lists Cloud Starter at €20 per month billed annually for 2,500 workflow executions, and Pro at €50 per month billed annually for 10,000. n8n bills a complete workflow run as one execution regardless of its number of steps. Prices and limits change, so verify the live page before deciding.

Community Edition is available as a standard self-hosted version. Do not confuse it with the paid self-hosted Business plan. The current Business plan adds features such as different environments, Git-based version control, and scaling options, and is priced very differently from a small Cloud plan.

Choose n8n Cloud when these statements are true

• You want to build workflows today and do not want to maintain another production service.
• Your usage fits a predictable execution allowance.
• Managed upgrades, availability, and backups are worth more than infrastructure control.
• A hosted service in the EU meets your data-location and procurement needs.
• You are testing a product idea and want the fastest reversible start.

For a solo developer, consultant, or small Swedish company, Cloud is usually the sensible default. It gives you a known monthly cost and removes several ways to lose a weekend.

Choose self-hosting when these statements are true

• Workflows must reach systems on a private network without exposing them publicly.
• You need custom nodes, command execution, or host-level integrations that the managed product does not provide.
• You have a specific infrastructure, compliance, or data-location requirement that Cloud cannot meet.
• Execution volume makes the managed plan expensive and you can operate the service reliably.
• You already have monitored container infrastructure, tested backups, and someone accountable for incidents.

Self-hosting is strongest when it solves a concrete constraint. “I can run Docker” is not enough on its own. Production ownership also means knowing whether a backup restores, whether webhooks work after an upgrade, and whether someone notices a stopped worker.

A Sweden and EU data checklist

The current n8n pricing FAQ says hosted-plan data is stored in the EU on servers in Frankfurt. n8n’s sub-processor list identifies Microsoft Azure as the cloud provider and lists EU processing locations including Germany and Sweden. Check both pages during procurement because providers and terms can change.

Self-hosting gives you control over where the n8n instance and its database run. It does not automatically keep all workflow data in Sweden or the EU. A workflow that sends customer data to an AI model, CRM, email provider, or analytics API still transfers data to that service.

For any workflow that handles personal data, record at least:

• which systems receive the data and for what purpose
• where execution history and binary files are stored
• how long successful and failed execution data is retained
• who can read credentials and execution logs
• which data processing agreements and sub-processors apply

This is an engineering checklist, not legal advice. For material personal-data processing, confirm the setup with the person responsible for privacy and compliance.

The self-hosting minimum

n8n provides an official Docker installation guide. A production deployment needs more than starting the container. At minimum, plan for the following:

1. A pinned n8n version and a tested update procedure.
2. Persistent database storage and encrypted, off-machine backups.
3. A stable encryption key stored separately from the database backup.
4. TLS, a correctly configured public webhook URL, and restricted admin access.
5. Monitoring for availability, failed workflows, disk space, and database health.
6. A restore drill that proves workflows and credentials work after recovery.
7. A schedule for security updates and an owner for incidents.

Run the built-in n8n security audit as part of that routine. It checks for issues including risky or custom nodes, unprotected webhooks, missing security settings, and an outdated instance.

Do a reversible Cloud trial before migrating

If you are unsure, spend the first two weeks proving the workflows instead of designing infrastructure. Build two or three real automations, measure execution volume, and list every missing capability.

Then make the decision from evidence:

1. Estimate monthly executions from schedules, webhooks, and chat messages.
2. Record whether workflows require local network access or unsupported custom code.
3. Price the appropriate Cloud plan from the current pricing page.
4. Price self-hosting with time, backups, monitoring, and recovery included.
5. Choose Cloud unless the self-hosted option wins on a named requirement, not only on the server invoice.

Starting on Cloud is reversible, but migration is still work. Export and test workflows, recreate or transfer credentials safely, reproduce environment variables, compare webhook URLs, and run old and new environments in a controlled cutover. Do not cancel the source environment until scheduled and webhook-triggered workflows have completed successfully on the destination.

My default recommendation

Use n8n Cloud for the first production workflows. Move to self-hosting only when the workflows prove their value and expose a clear reason to own the infrastructure. That order keeps your first investment in automation logic, which survives either hosting choice.

Start an n8n Cloud trial if managed hosting fits the checklist. If you choose self-hosting, begin with the official Docker guide and write the backup and upgrade procedure before the instance becomes business-critical.