How to Self-Host n8n for Your Business - A Plain-English Guide

How do you self-host n8n?

You self-host n8n by running it on a server you control - usually a small cloud server you rent for a few dollars a month - instead of using the hosted cloud version. In practice that means renting a basic Linux server, installing n8n on it with Docker, pointing a domain at it, and putting it behind a login and HTTPS. Once it is running, you open it in a browser like any other web app and build workflows exactly as you would on the cloud version, except the whole thing lives on your own machine.

The reason to do it is ownership. On a self-hosted instance, every workflow and every piece of data it touches stays inside your own system rather than passing through a third party, and you are not metered per step, so a workflow that runs thousands of times a month costs the same to run as one that runs a hundred times. That is the whole appeal, and it is why businesses handling sensitive data or high volume choose self-hosting over the convenience of a managed service.

Why self-host n8n instead of using the cloud version?

You self-host when you need to own the data or the cost, and you use the cloud version when you want convenience. Those are the two reasons that decide it. Self-hosting keeps sensitive data - customer records, financial details, anything private - inside your own system, and it removes per-operation pricing, so heavy workflows do not get more expensive as they scale. The cloud version hands you both of those in exchange for a subscription and a data path through someone else's servers.

The honest trade is maintenance. The cloud version handles updates, uptime, and backups for you. Self-hosting puts that work on you, and pretending it is free is the mistake that turns a good decision into a bad one. If the ownership benefits are worth that ongoing work, self-host. If they are not, the cloud version is not a compromise - it is the right tool.

What do you need to self-host n8n?

You need four things, none of which require being a developer: a small cloud server, Docker to run n8n on it, a domain name to reach it, and a login plus HTTPS so it is not open to the internet. That is the whole shopping list. The server is the only recurring cost beyond the domain, and a basic one is enough for most business workflows - you do not need a powerful machine to run a handful of automations.

• A small cloud server. A basic Linux server from any major provider, rented monthly, is plenty for most workflows. Start small - you can resize it later if you outgrow it.
• Docker. It is the standard way to run n8n, because it installs the whole thing as one contained package instead of a dozen separate pieces you have to wire together.
• A domain name. A subdomain of a domain you already own works fine, so you reach n8n at an address you control rather than a raw server number.
• A login and HTTPS. n8n must sit behind authentication and an encrypted connection before it goes live. An open, unencrypted automation server is an invitation, not a setup.

How do you set it up without being a developer?

You set it up by working through it one step at a time with help, not by memorising commands. The install itself is largely a matter of renting the server, running the n8n Docker command on it, and connecting your domain - a short, well-documented path. The part that stops most non-technical owners is not the difficulty of any single step, it is not knowing which step comes next or what an error message means.

This is exactly where Claude Code from the desktop app earns its place. You describe what you are trying to do in plain English - "help me install n8n on this server and put it behind a login" - and it explains each step, gives you the exact command, and tells you what to check before moving on. You are not learning server administration from scratch, you are working through a known path with something that has walked it before. [How to use Claude Code for your business](/blog/how-to-use-claude-code-for-your-business) covers getting started from the desktop app without a terminal setup.

1. Rent a small Linux server from a cloud provider and note its address.
2. Install Docker on it, then run the n8n container - one command, which the docs and Claude Code can hand you directly.
3. Point a subdomain you own at the server so you reach n8n at your own address.
4. Put a login and HTTPS in front of it before it goes live, so it is never open and unencrypted.
5. Open it in a browser, create your account, and build your first workflow read-only to confirm it works before you enable anything that writes or sends.

What is the Own-It Checklist for a self-hosted server?

The Own-It Checklist is our four-point rule for running a self-hosted n8n instance safely, because the install is the easy part and owning it is the real job. Once the server is yours, so is its security, its backups, and its updates - the work the cloud version quietly did for you. Skip these four and a self-hosted instance stops being an asset and becomes a liability that holds your credentials with no one watching it.

1. Lock down access. A strong login, HTTPS, and no open ports beyond what n8n needs. This is the one you cannot skip - the server can act on your systems, so its front door has to be sealed.
2. Back up regularly. Your workflows and credentials live in n8n's database. Back it up on a schedule and store a copy off the server, so a failed disk does not erase months of builds.
3. Keep it updated. Automation tools ship security fixes. Apply updates on a cadence rather than never, because an unpatched server is the one attackers look for first.
4. Monitor it. Set an alert for when a workflow fails or the server goes down, so you find out from a notification rather than from a customer telling you something broke.

None of these are hard once, and all of them are damaging to skip. The reason self-hosting gets a reputation for being risky is not the technology - it is that people run the install, get a working instance, and then never do the four things that keep it safe. Owning the tool means owning that maintenance, and if that is not a commitment you want, the cloud version exists precisely so you do not have to make it.

How much does self-hosting n8n cost?

The direct cost is the server plus a domain - a small monthly figure for a basic cloud server, and a few dollars a year for the domain. There is no per-operation fee, which is the whole financial point: once the server is paid for, running a workflow a thousand times costs no more than running it once. For a high-volume automation, that flat cost is often far cheaper than a metered plan that charges for every step.

The real cost is your time. Setup takes an afternoon the first time, and maintenance - backups, updates, the occasional fix - is an ongoing hour here and there. That time is the true price of ownership, and it is why the honest comparison is not the server bill against a subscription, it is the server bill plus your maintenance time against the subscription. For a business handling sensitive data or high volume, that trade usually favours self-hosting. For a light, non-sensitive workflow, it usually does not.