Local n8n vs n8n Cloud: What You Need to Operate Yourself

A local experiment and a production automation service require different operating decisions. Compare responsibilities before choosing where to run n8n, rather than assuming that a workflow working on a laptop is ready to run unattended.

Use a local trial to answer a small question

Start with dummy inputs and a workflow whose external actions cannot affect real users. Check how the workflow handles an invalid item, a duplicate event and a stopped process. These are proposed tests; this article does not report having run them.

A powered-off laptop cannot receive and process requests as a continuously available service. If availability matters, define who monitors the system and what happens when it is unavailable.

Give production self-hosting an operating owner

n8n’s Docker Compose guide is a setup reference. Review which components are intended for local development and which recommendations apply to production. The presence of a configuration example does not prove that it meets your recovery, access or availability requirements.

Responsibility	Question to answer
Availability	Who notices outages and restores service?
Recovery	Which database, files, configuration and secrets are required?
Credentials	Who has access, and how are credentials changed?
Retention	What evidence is saved, for how long, and at what volume?
Updates	Who tests changes and keeps a recovery path?
External actions	How are duplicates and uncertain outcomes reconciled?

The encryption-key documentation explains how credentials are encrypted before database storage. Include the key in an appropriately protected recovery plan. Workflow exports alone do not establish that you can restore the full service.

Execution data can grow with saved runs and their content. Decide what evidence you need and review storage settings and pruning. Do not select retention based only on a small initial trial.

Review the intended licensing use

The official FAQ and license describe conditions for personal, learning and internal business use, and some work for clients. The FAQ identifies external users creating or changing their own workflows as an important boundary for services built with n8n, including through a custom interface. Connecting credentials owned by another party is not, by itself, the whole test.

Describe the actual service and confirm uncertain cases with n8n. This article does not decide whether an individual arrangement is license-compliant. n8n Cloud is offered under its own terms.

Cloud still leaves workflow decisions with you

Using Cloud changes the hosting responsibilities, but you still choose the workflow logic, external permissions, retention needs and response to failed or duplicated actions. n8n’s Cloud update documentation also describes owner choices around versions and maintenance.

Choose the option whose responsibilities you can support. This comparison makes no claim about measured speed, uptime, total cost or revenue for either option.