Why does n8n's hosting model matter?
n8n is a source-available workflow automation tool: a visual builder where you connect triggers, apps, APIs, and logic into automations without writing everything from scratch. What makes it different from most automation tools is that you get a real choice about where it runs. You can let n8n host it for you on n8n Cloud, or you can download the Community Edition and run it yourself on your own infrastructure. The features are largely the same. The difference is who carries the operational weight, and how the cost behaves.
n8n Cloud is the managed software-as-a-service version. n8n runs the servers, applies updates, handles uptime, and gives you support, and you pay a monthly fee tiered by how many workflow executions you use. You log in and build; you never touch infrastructure. Self-hosted n8n is the Community Edition you install on your own server, typically with Docker, under n8n's Sustainable Use License, which is free of license cost for internal business use. There is no per-execution fee, so your only hard cost is the server it runs on. In exchange, you own everything operational: setup, SSL, the database, updates, backups, security, monitoring, and scaling.
This is genuinely a strategic decision, not just a billing preference. It touches your monthly cost as you scale, where your customer data physically lives, how much engineering time you spend on maintenance, and how quickly you can get to working automations. The right answer depends on volume, data sensitivity, and whether anyone on your team wants to own infrastructure.
"n8n Cloud and self-hosted run the same engine. You are not choosing features, you are choosing who carries the operational burden and how the bill behaves as you grow."
Quick comparison: n8n Cloud vs Self-Hosted
| Factor | n8n Cloud | Self-Hosted |
|---|---|---|
| Who hosts it | n8n hosts and operates it for you | You run it on your own server or VPS |
| Pricing model | Tiered monthly fee by executions | Free license; you pay only for infrastructure |
| Execution limits | Capped by plan tier | Limited only by your hardware |
| Maintenance | None; updates and uptime handled for you | You own updates, backups, security, monitoring |
| Data control | Runs through n8n's hosted environment | Stays entirely on your infrastructure |
| Setup effort | Sign up and build immediately | Docker, reverse proxy, SSL, database, backups |
| Scaling | Move up a plan tier | Queue mode with Redis and worker processes |
| Support | Vendor support included | Community forum (Enterprise license adds support) |
| Best for | Teams that want working automations, not infrastructure | High volume, strict data control, in-house technical capacity |
Features and pricing models verified May 2026. Source: n8n
Trying to decide because you are about to build something real on n8n? A free automation audit maps exactly which workflows are worth building and what hosting actually makes sense for your volume and data needs.
Get a free automation audit →Is n8n Cloud the right choice for you?
n8n Cloud is the fully managed version. n8n runs the servers, handles updates and uptime, and provides support, so you focus entirely on building workflows. Its defining trait is execution-based pricing: rather than charging per task or operation the way many automation tools do, n8n counts a complete workflow run as a single execution, no matter how many steps it contains. For multi-step automations, that pricing model is dramatically more economical than per-task tools.
Plans are tiered, commonly a Starter, Pro, and Enterprise structure, with each tier including a monthly execution allowance and a cap on the number of active workflows. Published Starter pricing has been in the roughly $20 to $25 per month range billed annually, with Pro tiers higher and Enterprise priced on request. Confirm current tiers, execution allowances, and active-workflow limits directly with n8n, because these change.
Where n8n Cloud wins:
- Zero maintenance. No servers, no Docker, no SSL certificates, no update cycles, no backups to manage. This is the single biggest reason teams choose it.
- Fast to start. You sign up and build the same day, with no infrastructure project blocking your first workflow.
- Execution-based pricing is cheap for complex automations. A 30-step workflow costs the same one execution as a 3-step one, which punishes per-task tools and rewards n8n.
- Vendor support and managed uptime, so a server problem is n8n's problem, not yours.
- Easy to scale up by moving to a higher tier when you outgrow your execution allowance.
Where n8n Cloud has limitations:
- Execution and active-workflow caps. At high volume, climbing tiers can become more expensive than running your own server, where executions are effectively free.
- Data passes through n8n's hosted environment. For businesses with strict data residency or compliance requirements, that can be a dealbreaker.
- Less control over the environment, custom community nodes, and system-level configuration than you get when you own the box.
- The most advanced governance features (SSO, role-based access, environments) sit on the Enterprise tier.
Pricing note: n8n Cloud's execution-based model is the key to understanding its cost. Because one workflow run is a single execution regardless of how many nodes it touches, a complex automation that would burn dozens of tasks on a per-operation tool counts as just one execution here. That makes Cloud very cost-effective for low-to-moderate volumes of rich workflows, and it is why many teams start on Cloud. The economics flip at high execution volume, where the recurring tier cost can exceed what an equivalent self-hosted server would run, since self-hosted executions are bounded only by your hardware. Always model your real monthly execution count, not a headline price, when comparing Cloud against self-hosting. These figures reflect publicly reported ranges and change over time, so confirm current pricing directly with n8n.
Is self-hosting n8n the right choice for you?
Self-hosted n8n is the Community Edition installed on your own infrastructure, usually via Docker on a cloud server or VPS. Under n8n's Sustainable Use License it is free of license cost for internal business use, so there is no per-execution or per-seat fee. Your only hard cost is the server, which can be as little as a few dollars a month for low volume. In return, you own the entire operational stack, and that ownership is the whole story: it is both the advantage and the cost.
Running it well means putting n8n behind a reverse proxy with an SSL certificate, connecting a proper database, keeping the version updated, taking regular backups, monitoring uptime, and hardening security. For higher throughput you configure queue mode with Redis and separate worker processes so executions scale horizontally. A paid Enterprise self-hosted license is available for organizations that need advanced governance features and vendor support while still keeping data on their own infrastructure.
Where self-hosting wins:
- No execution fees. Once the server is running, you can execute as many workflows as your hardware handles without the bill climbing, which is decisive at scale.
- Full data control. Every payload, credential, and execution stays on infrastructure you own, which is often a hard requirement for healthcare, legal, financial, and compliance-sensitive businesses.
- Complete control over the environment, including custom community nodes, system configuration, and integrations that a managed environment may restrict.
- Lower marginal cost at volume. For heavy automation workloads, self-hosting is usually far cheaper than climbing Cloud tiers.
Where self-hosting has limitations:
- You own all the maintenance: updates, backups, security patches, SSL renewals, uptime monitoring, and incident response. That is ongoing work, not a one-time setup.
- It requires real technical capacity. Standing up and maintaining it is straightforward for a developer but is not a no-code task.
- Support is community-based unless you buy the Enterprise license, so when something breaks at 2am, it is on you.
- Scaling for high throughput (queue mode, workers, database tuning) is your responsibility to design and operate.
"Self-hosting is not really free. The license is free, but you are paying in engineering time and operational risk. Whether that trade is worth it depends entirely on volume and whether someone owns the infrastructure."
The middle ground: managed self-hosting and the SaaS alternatives
The Cloud-versus-self-hosted choice is not strictly binary. Two other options come up constantly when teams are deciding, and understanding them clarifies whether either pure option is right for you.
This is the option most businesses do not realize exists. An agency or partner runs self-hosted n8n on infrastructure you control, handling the setup, updates, backups, security, and scaling for you. You get the data-control and no-execution-fee benefits of self-hosting without putting the DevOps burden on your team. For a business that needs data to stay in its own environment but has no infrastructure person, this is frequently the right answer, and it is how Aplos AI runs n8n for clients who need self-hosting without the operational weight.
Zapier and Make are fully managed SaaS automation tools that compete with n8n Cloud. They are often easier for non-technical users to start with and have large app libraries, but they generally price on tasks or operations, so a single multi-step automation consumes many billable units per run and the cost rises steeply with volume. n8n's execution-based and self-hosted models are usually much cheaper for complex or high-volume workflows. The trade-off is that Zapier and Make ask nothing of you operationally, while n8n rewards a bit more technical investment with far lower marginal cost.
| Factor | n8n Cloud | Self-Hosted | Managed self-hosting | Zapier / Make |
|---|---|---|---|---|
| Maintenance burden | None | High (yours) | None (partner) | None |
| Data control | Vendor-hosted | Full | Full | Vendor-hosted |
| Cost at high volume | Rises by tier | Lowest | Low plus service fee | Highest |
| Technical skill needed | Low | High | Low | Low |
| Best for | Most teams starting out | Technical teams at scale | Data control without DevOps | Simple automations, non-technical users |
If you want managed simplicity and your volume is moderate, n8n Cloud is the obvious starting point. If you have technical capacity and either high volume or strict data needs, self-hosting wins on cost and control. If you need that control but have no one to run the infrastructure, managed self-hosting gives you the benefits without the burden. Zapier and Make make sense only when simplicity matters more than cost and your workflows stay light.
How do you choose between n8n Cloud and self-hosted?
When we set up automation systems for clients, the hosting decision comes down to three questions: how much volume you will run, how sensitive your data is, and who, if anyone, will own the infrastructure. The features barely differ, so the decision is about economics and operations.
We lean toward n8n Cloud when: The team wants working automations without owning infrastructure, volume is low to moderate, and there is no hard data-residency requirement. Cloud gets you live fastest, and execution-based pricing is affordable until volume gets heavy. It is the right default for most businesses that are not running automation at large scale.
We lean toward self-hosting when: Data must stay inside the business's own environment for compliance or privacy reasons, or execution volume is high enough that Cloud tiers cost more than running a server, and there is technical capacity to operate it. At scale, the economics strongly favor self-hosting.
We recommend managed self-hosting when: The business needs self-hosting's control or cost profile but has no one to run infrastructure. An agency operating n8n on infrastructure the client owns delivers the benefits without the maintenance burden landing on a team that cannot sustain it.
Answer these before you commit:
- What is your realistic monthly execution volume? Low to moderate favors Cloud's simplicity; high volume favors self-hosting's flat infrastructure cost.
- Does your data have to stay in your own environment? If compliance or client requirements demand data residency, self-hosting (managed or not) is the safer default.
- Who will own the infrastructure? If no one wants to run servers, choose Cloud or managed self-hosting, not raw self-hosting.
- How fast do you need to be live? Cloud gets you building today; self-hosting adds an infrastructure setup step first.
- Do you need enterprise governance? SSO, role-based access, and environments sit on the Enterprise plan regardless of where you host, so factor that in if you need them.
Enterprise features: what is gated and where
Both hosting models market the same core builder, so it is worth being precise about what is reserved for the paid Enterprise plan, because it is the same list whether you run Cloud or self-hosted.
The free tiers, whether that is a Cloud Starter plan or the self-hosted Community Edition, give you the full workflow builder, the large node library, webhooks, scheduling, and core integrations. For most automation work, that is everything you need.
The Enterprise plan is where governance and team-scale features live: single sign-on (SSO and SAML), role-based access control, multiple environments for separating development and production, git-based version control of workflows, external secret store integration, log streaming, and dedicated support with stronger uptime commitments. Crucially, these are tied to the Enterprise license, not to a particular hosting model, so you can run Enterprise features either in n8n Cloud or on self-hosted infrastructure. If your need for those features is what is driving the decision, the choice is Enterprise-or-not first, and Cloud-or-self-hosted second.
The automation gap: hosting is the easy part
Here is the thing that gets lost in every Cloud-versus-self-hosted debate. Choosing where to run n8n is the easy decision. It is a couple of factors: volume, data sensitivity, and who owns the box. You can resolve it in an afternoon. The hard part, the part that actually determines whether automation delivers any return, is everything that happens after you pick a hosting model.
n8n is an engine. An engine does nothing until someone designs the workflows that run on it, connects them correctly to your CRM, accounting, scheduling, phone, and email systems, handles the edge cases and failures gracefully, and keeps the whole thing working as your tools and processes change. That is where automation projects succeed or quietly fail, and none of it is decided by whether you chose Cloud or self-hosted.
In practice, the real work is:
- Designing the right workflows. Mapping which repetitive processes are actually worth automating, in what order, and what each one needs to connect to. Most wasted automation effort comes from building the wrong thing well.
- Connecting to your real stack. Wiring n8n into the specific CRM, billing, scheduling, and communication tools you already use, with the authentication, data mapping, and error handling that production reliability demands.
- Handling failure gracefully. Real automations break: an API changes, a record is malformed, a service goes down. Production-grade workflows detect, retry, alert, and recover instead of silently dropping work.
- Maintaining it over time. Tools update, APIs deprecate, processes shift. Automations need ongoing care to keep delivering, which is exactly the work most businesses underestimate.
This is the layer Aplos AI builds for service businesses. We design the workflows, build them on n8n, make the hosting decision for you (Cloud, self-hosted, or managed self-hosting on infrastructure you own), connect everything to your real stack, and maintain it so it keeps working. We do not hand you an engine and a hosting bill. We deliver working automations and run the part that is actually hard.
Trying to decide how to run n8n because you have real automations to build? We map your workflow in a free audit, recommend the hosting model that fits your volume and data needs, and show you exactly what is worth building first.
Get a Free Automation Audit →