n8n self hosted vs cloud for clients: costs, uptime and ownership

You built a client a lead flow in n8n and it works. Now the awkward question: where does it live? On a $10 server you set up, on n8n Cloud, on the client's own machine? Most comparison pages answer this for a company running n8n for itself. That is a different problem from yours.

When you build for clients, the hosting choice decides three things: what the client pays each month, who gets the call when it breaks, and who owns everything when the project ends. Get the last one wrong and you become an unpaid hosting company, or worse, you lock the client out of their own automations.

This guide gives a straight answer, the real numbers as of November 2026, and a handover checklist you can copy.

Should clients be on n8n Cloud or self-hosted?

Default to n8n Cloud, in the client's own account. Choose self-hosting only when the client owns the server and someone is paid to look after it. That covers the large majority of small business clients, who have no IT person and want the automation to just keep running.

Two quick definitions. n8n Cloud is n8n's hosted service: you log in, build, and n8n runs the servers. Self-hosted means you install n8n (usually the free Community edition) with Docker on a server, called a VPS (virtual private server), and you are responsible for keeping it alive.

Here is the short decision table.

The n8n docs make the same split: Cloud for people who "don't have technical expertise" or "don't want to manage infrastructure", self-hosted for those who "have infrastructure and technical resources" (n8n docs).

What does each option cost a client?

n8n Cloud starts at €20 a month billed yearly; self-hosting is free software plus a server plus somebody's time. The time is the cost most freelancers forget to price.

Prices from the n8n pricing page, checked November 3, 2026:

An execution is one full run of a workflow, however many steps it has. A lead flow that fires 50 times a day is about 1,500 executions a month, which fits inside Starter.

A worked example (our illustration)

Say a client's flows run about 2,000 times a month and you charge $60 an hour.

1. Cloud Starter: €20 a month. Your monthly time on hosting: close to zero. Total: about €20.
2. Self-hosted on a small VPS: r/n8n users commonly mention a VPS around $10 a month. Add even one hour of your time for updates, backup checks and the odd restart, and it is $10 plus $60, so $70 a month.

At low volume, Cloud is cheaper for the client once your time is counted. Self-hosting starts to win when volume pushes past Pro's 10,000 executions, or when the client already has an IT team whose time is a sunk cost.

Watch out: "Free" self-hosting is only free if nobody bills for the maintenance. If you do it for free, the cost is still there. It just comes out of your margin.

The free tier has limits too. n8n's compare editions page lists what the Community edition leaves out: workflow and credential sharing, projects, SSO, environments, Git version control, external secrets and log streaming. As one r/n8n reply put it, the moment you want real collaboration "you need the n8n Business license (even when self-hosted)". The free registered version adds folders and debugging tools, nothing more.

Which one is more reliable?

For a client with nobody technical on staff, Cloud is more reliable, because someone is paid to keep it up. Self-hosted n8n can be very stable, but only if you set it up properly and watch it.

The most useful reliability notes come from a r/n8n post titled "What actually breaks when you run n8n self-hosted for 6+ paying clients on one VPS". The replies list what goes wrong in practice:

• Out of memory kills. One reply explained that when a client passes a huge file or JSON array, the container spikes in RAM and Linux kills it. When that happens, "your built-in n8n error workflow will not fire because the container is already dead." You find out when the client asks why their leads stopped.
• One client blocks another. Another builder spent a week chasing dropped webhooks, then found a different client's two minute polling loop was blocking everything, until they switched on queue mode.
• Lost encryption keys. n8n encrypts stored credentials with a key kept in the instance's .n8n folder. The backup docs are blunt: without that key, a restored database's credentials "can't be decrypted". A server rebuilt without it means reconnecting every app by hand.

If you do self-host, the advice from a r/n8n thread on running it for a 100 person company is a good minimum: automate backups of workflows and data, put a firewall on the VPS, manage it with a tool like Coolify or Dokploy, and set usage alerts at 50% and 80% of server resources.

Tip: Use an outside uptime monitor that pings a webhook every few minutes. n8n's own error workflow cannot tell you the server is down, because it runs on that server.

Who owns the server when you hand over?

The client should own it, every time. Put the Cloud account or the VPS in the client's business name, on their card, with their email as the owner. Add yourself as a user.

If the automation runs in your account, three things quietly become your problem:

1. The bill. You pay the subscription and have to chase the client to repay it.
2. The data and logins. Their CRM, email and payment credentials sit on a system you control. That is a liability you probably have not priced or insured.
3. The breakup. If you part ways, the workflows are on your server. Either you keep hosting a former client, or you migrate them, and credentials usually need reconnecting.

The top reply in the shared VPS thread summed up the simplest fix: "I just have the clients setup n8n on cloud and pay for it." That one habit removes most handover pain. For a fuller look at how this works across Zapier and Make too, see our n8n vs Make vs Zapier for client work comparison.

Can you legally host clients on your own n8n?

Usually not, if clients touch it. n8n's Sustainable Use License says you may use the software "only for your own internal business purposes or for non-commercial or personal use". Reselling access, white-labelling n8n or letting clients log into an instance you run falls outside that. In the shared VPS thread, two replies said it plainly: "You are violating the license. Each client needs to be on their own server." Building workflows on a client's own instance, for a fee, is the normal consulting pattern. If your setup is unusual, ask n8n in writing.

How to set up n8n for a client, step by step

Create everything in the client's name, document it, then hand over the keys. This sequence works for both Cloud and self-hosted.

1. Agree hosting in the proposal. State which option, who pays, and what maintenance costs. Pricing that maintenance is covered in the AI Automation pack, alongside the proposal templates.
2. Have the client create the account. For Cloud, they sign up and invite you. For self-hosted, they rent the VPS on their card and give you access.
3. Self-hosted only: set a custom encryption key. Set N8N_ENCRYPTION_KEY before first launch and store it in the client's password manager, not just yours.
4. Self-hosted only: switch on backups and alerts. Back up the .n8n folder and database on a schedule, and add an external uptime check.
5. Build, then add an error workflow. Route failures to the client's email or Slack, so they know before their customers do.
6. Write a one page runbook. What each workflow does, what to check if it stops, and who to call.
7. Hand over. Confirm the client is the owner, transfer anything still in your name, and agree in writing whether you stay on a retainer.

A runbook can be this short:

Workflow: New lead to CRM
Runs when: website form is submitted
If leads stop arriving: check n8n > Executions for red errors
Most common cause: CRM login expired, reconnect it in Credentials
Hosting: n8n Cloud, owner billing@clientco.com
Support: [your name], retainer covers 2 hours/month

What goes wrong most often?

Most failures are ownership and maintenance problems, not technical ones. These come up again and again on r/n8n:

• Hosting every client on your one VPS. Cheap at first, then a licence problem and a single point of failure. One crash is six angry clients.
• Not pricing maintenance. Self-hosting looks free, so builders include it, then spend unpaid hours on updates.
• Losing the encryption key. The server dies, the backup restores, and no credential works.
• Promising features Community does not have. Clients who want several staff editing shared workflows need Cloud Pro or a paid plan, not the free edition.
• Assuming the error workflow covers crashes. It does not if the container itself is dead.
• Ignoring licence changes. When n8n introduced execution-metered Business pricing for self-hosters, a r/n8n thread drew hundreds of upvotes in protest. Community edition stayed free, but check the pricing page before quoting a client a long contract.

If you are still working out what to offer and how to find the first clients, our guide to starting an AI automation agency with no experience covers the first steps.

When is self-hosting the right call?

Self-host when the client owns the server and at least one of these is true: they have strict data rules, they have an IT person, they run very high volume, or they need local AI models or custom nodes. In those cases self-hosting is often the better answer, and you can charge for setup plus a monthly maintenance retainer.

Be honest about what you can support. If you are not confident running Docker, reverse proxies, backups and updates, one r/n8n reply gave advice that applies directly: "You don't sound like you are confident to keep this secure and up." Cloud is not a lesser product; it is a way to sell automation without also selling server administration.

Where to go from here

1. For each current client, write down where their n8n lives and whose name is on it.
2. Move anything hosted on your own server into an account the client owns.
3. Add an outside uptime check and an error workflow for every client.
4. Put hosting, ownership and maintenance into your next proposal in plain words.
5. If you self-host, back up the encryption key today.

The AI Automation pack gives you the parts this article does not: 23 lessons across 6 modules on pricing from hours saved, proposal and scoping templates, and keeping clients after the build. It is $19, or $39 for all 16 Money Printer packs. Results depend on your clients and your work; no pack can promise income.