The choice between n8n self hosted vs cloud is a trade between money and time. n8n Cloud is run for you: no servers, automatic updates, and plans billed by workflow executions with limits on concurrency and run duration. Self-hosted n8n runs on your own server: the community edition has no per-execution fee, you control the data and limits, but you are responsible for security, updates, backups and uptime. For most agencies without a technical person, Cloud is the safer start. For agencies with high volume, strict data requirements or in-house technical skill, self-hosting usually pays off.
I set up both for clients. This guide covers pricing, what self-hosted really costs, the operational differences and a simple way to decide.
n8n Cloud: what you get
n8n Cloud is the hosted version run by n8n. You sign up, log in and build workflows. n8n handles servers, scaling, updates and backups of the platform.
According to n8n's pricing page, checked for this article, cloud plans are priced in euros and differ on:
- Workflow executions per month. One execution is one run of a workflow, regardless of how many nodes it has.
- Concurrent executions. How many workflows can run at the same time.
- Maximum execution duration. How long a single run can last. At the time of writing, the entry Starter plan lists a shorter limit than Pro.
- Log retention. How long execution logs are kept.
- AI assistant credits for n8n's built-in assistant.
At the time of writing, the Starter plan is listed at €20 per month and Pro at €50 per month, billed annually, with execution allowances of 2,500 and 10,000 per month respectively, and Enterprise on custom pricing. These change, so check the pricing page before deciding.
n8n self hosted pricing
Is n8n self hosted free?
The community edition of n8n is available on GitHub and can be self-hosted without paying n8n per execution. It is licensed under n8n's sustainable use license, which is a fair-code license rather than a traditional open-source one. In broad terms, it allows using n8n for your own internal business purposes, but has restrictions on things like offering n8n itself as a hosted service to others. Read the license yourself if your use case is unusual, such as hosting n8n for clients.
Paid self-hosted plans
n8n also offers self-hosted Business and Enterprise plans with features for teams, such as advanced user management and environments. At the time of writing, the pricing page lists the Business plan as self-hosted, at €667 per month billed annually, using a license key that counts production executions. Check the current page for details.
What self-hosting actually costs
Free software is not free to run. The real costs are:
- Server. A VPS sized for your workload. Small setups can run on modest servers, while AI-heavy or high-concurrency workloads need more memory and CPU.
- Database. SQLite by default, Postgres for heavier production use, possibly as a managed service.
- Backups and storage. Off-server storage for database dumps and workflow exports.
- Time. Setup, updates, monitoring and fixing things at awkward hours. This is usually the biggest cost.
As an illustrative example: if a VPS costs you a modest monthly fee and you spend two hours a month on maintenance, the true monthly cost is the server plus two hours of a technical person's time. Compare that to the Cloud plan you would need.
n8n cloud vs self hosted: side by side
- Setup: Cloud is minutes. Self-hosted is an afternoon for someone experienced, following the Docker setup guide.
- Updates: Cloud is automatic. Self-hosted is your job, including reading release notes for breaking changes.
- Executions: Cloud has plan limits. Self-hosted community edition is limited by your server.
- Run duration and concurrency: Cloud has plan limits. Self-hosted is configurable.
- Data location: Cloud runs on n8n's infrastructure. Self-hosted keeps data on your server, in the region you choose.
- Security: Cloud security is managed by n8n. Self-hosted security is your responsibility. See n8n self-hosted security.
- Backups: Cloud platform backups are handled by n8n. Self-hosted backups are yours. See n8n backup and update.
- Support: Cloud plans include n8n support at various levels. Community edition relies on the community forum and your own skills.
- Custom nodes and packages: Self-hosted gives you more freedom to install community nodes and connect to private networks.
When n8n Cloud makes sense
- Nobody on your team wants to manage a server.
- Your volume fits comfortably in a Cloud plan.
- Your workflows are short and do not need long run times.
- You want to start building today and decide on hosting later.
- Your clients do not have strict data residency requirements.
When self-hosting makes sense
- High volume. Thousands of executions a day can make Cloud plans expensive.
- Long or heavy workflows. AI agents, large file processing or big loops that need longer run times or more memory.
- Data control. Clients in regulated industries, or contracts that say data must stay in a specific region or on your infrastructure.
- Private network access. Workflows that need to reach databases or services not exposed to the internet.
- You have the skills. Someone in-house, or a partner on retainer, who will keep it patched and backed up.
Questions to ask before deciding
- How many workflow executions will we run per month in six months, not just today?
- How long do our longest workflows run?
- Who will apply updates and how quickly?
- What happens if the server goes down on a Saturday?
- Do any clients require data to stay on our infrastructure?
- Will we host n8n for clients, and does the license allow our use case?
If you cannot answer questions 3 and 4, start with Cloud.
Moving between them
You can start on Cloud and move to self-hosted later, or the reverse. Workflows can be exported as JSON and imported. Credentials need to be recreated, because they are encrypted with each instance's key. Plan a migration window, recreate credentials, update webhook URLs in every sending app, and test each workflow.
How it compares with Make
If neither option appeals, Make is fully hosted and easier for non-developers, billed per module run in credits. All the production builds I cite on this site, like the client onboarding automation, run in Make. See Make.com vs n8n for that comparison.
A middle option: managed hosting
There is a third path some agencies take: self-hosted n8n on a managed platform or with a partner who handles the server for you. You get the cost and control benefits of self-hosting, while someone else applies updates, watches uptime and runs backups. If you go this way, agree in writing who is responsible for updates, backups and restores, and how quickly they respond when something breaks.
How I build this
I help agencies choose between n8n Cloud and self-hosted, then set it up properly: HTTPS, Postgres, backups, update routines and error alerts, with workflows built on top. See my workflow automation service or AI workflow consulting, and request a free 15-minute Loom teardown if you want a second opinion on your setup.
FAQ
Is n8n self hosted free?
The community edition can be self-hosted without per-execution fees under n8n's sustainable use license. You still pay for the server and the time to maintain it.
Is n8n Cloud or self hosted cheaper?
For low volume, Cloud is often cheaper once you count maintenance time. For high volume or long-running workflows, self-hosting is usually cheaper if you have the skills to run it.
Can I move from n8n Cloud to self hosted?
Yes. Export workflows as JSON and import them, then recreate credentials and update webhook URLs, since credentials are encrypted per instance.
Can I host n8n for my clients?
Possibly, but check n8n's sustainable use license and paid plans first, since the license restricts some ways of offering n8n to others.