How to Self-Host Nod by n8n on Your Own Server
Yes — besides the desktop app, you can run Nod on your own server and connect to it from the app. The main reason to bother is availability: on a laptop, Nod stops the moment the laptop sleeps, while a server keeps it working around the clock. Self-hosting also puts the database, files, memory, and saved logins on hardware you control. Below are the requirements, both install paths, and how the self-hosted setup differs from the desktop one — all following n8n's self-hosting documentation.
Who self-hosting is for
The desktop version has one structural weakness, and n8n states it plainly: when your laptop sleeps, shuts down, or you quit the app, everything stops — chats, channels, and scheduled tasks — until the machine wakes and Nod is open again. A morning brief or a price check that runs every few hours is exactly the kind of job that breaks.
n8n's own suggested fixes are to run Nod on an always-on machine such as a Mac mini, or on your own server. A managed hosting option is on n8n's roadmap but has not been released yet, so today, "always on" means self-hosting. It also suits anyone who would rather keep Nod's data on their own infrastructure from the start. If neither applies, the desktop route — Install on Mac or Install on Windows — is simpler.
What you need
Per n8n's self-hosting documentation:
- A Linux server on AMD64 or ARM64, or a Mac with Docker Desktop.
- A recommended starting point of 2 CPU cores, 8 GB of RAM, and 50 GB of disk.
- Docker Engine 25 or later with Compose v2, plus OpenSSL.
- For remote access, either an SSH tunnel or a domain name with inbound ports 80 and 443 open.
The spec is deliberately modest — Nod's server is a single-user application, not a platform you are sizing for a team.
Option 1: the prebuilt bundle
The fastest path is the prebuilt server bundle. Download the nod-server-linux-<architecture>-<commit> package from the GitHub Self-host bundle workflow, verify its sha256 checksum, extract it, and run sh install.sh. One practical warning from the docs: the workflow artifact expires after 14 days, so download it when you are ready to install rather than stockpiling it.
Which route should you take? The bundle is the default for a reason: no build step, no toolchain, and you are running within minutes. The source route earns its extra steps if you want to read or adjust what you deploy, or if no bundle exists for your setup. Both end at the same place — the same Nod, the same token login, the same app connection — so the choice is about how you like to operate a server, not about features.
Option 2: build from source
If you prefer building it yourself, clone the repository, go into deployment/self-host, and run sh setup.sh. That generates a .env file containing your server token, Vault key, and database password. Then bring the stack up with docker compose up -d --build --wait, open http://localhost:4310, and enter the NOD_AUTH_TOKEN from your .env to get in. Keep that .env safe — the token is the key to your Nod.
Connecting, and putting it on the internet
On the desktop app's Welcome screen, choose Connect to a server instead of Get started, and point it at your server — the same app becomes the front end for your self-hosted Nod.
If you want it reachable over HTTPS with a domain: point the domain at the server, open ports 80 and 443, and set NOD_PUBLIC_URL in .env. Bundle installs run sh install.sh --https; source installs use docker compose --profile https up. Certificates are requested and renewed automatically by Caddy. If you already run your own reverse proxy, you can skip that and forward to Nod's local port 4310 instead. And if you'd rather expose nothing at all, an SSH tunnel works fine for remote access.
What lives on your server
Self-hosting moves Nod's whole state onto your hardware: the database, files, memory, and saved logins all sit on the machine running Nod, which is the server you control. Two defaults from the desktop world still apply, and are worth knowing before you start. App connections still route through n8n's hosted connection service and Composio by default — hosting the agent yourself doesn't change how app authorization is brokered. And basic usage-data sharing with n8n is on by default for new users; it can be switched off in Settings → Privacy & data, while conversation traces are only ever sent if you opt in.
The chat channels benefit most from the move. On a laptop, closing the lid silences the Telegram and WhatsApp channels along with everything else; on a server, those conversations — the same conversation you continue in the desktop app — stay reachable, and scheduled jobs fire whether or not any of your own devices are awake.
Self-hosted vs desktop: what actually changes
- Availability. The server runs 24/7. Schedules, chat channels, and background tasks keep going while your laptop is closed or travelling with you.
- The work moves to you. You operate the machine and its Docker stack — updates, uptime, and backups are your job in a way the desktop app never asks of you.
- The limits don't change. A self-hosted install still has exactly one owner. Hosting Nod yourself does not turn it into a team tool; one Nod shared by a team is on n8n's roadmap, not in the product today.
- The product doesn't change. It is the same free, open source Nod, and you still bring your own model — see Connect a model and the pricing breakdown for what that costs. Hosting changes Nod's availability, not its cost structure or its feature set.
If you are still deciding whether Nod is for you at all, What is Nod is the place to start; every guide, including the Tutorial, is collected in the Nod hub.