n8n's own Docker install docs are fine, but "fine" still means writing a compose file, wiring up a reverse proxy for HTTPS, and remembering to actually back up the workflow database before you lose a year of automations to a bad docker system prune. Here's the version where a template handles the first two and a schedule handles the third.
What you need
- A VPS you can reach over SSH a $5/month box runs n8n comfortably for personal or small-team use.
- The DeployOS desktop app the Free plan includes 5 starter templates, which is enough to try this.
Step 1: Get the server ready
Servers → Add Server, connect over SSH, then run Bootstrap from the server card. That one step installs Docker, sets up the firewall, and starts your reverse proxy (Traefik by default) everything n8n's container is going to need to actually be reachable over HTTPS afterward.
Step 2: Deploy n8n from Templates
Go to Templates, find n8n under the automation category, and pick the server you just bootstrapped. You can optionally set a custom domain right here instead of doing it later. Click deploy.
Behind that one click, DeployOS generates the correct compose configuration for n8n, deploys it, wires it into the server's reverse proxy, and runs the same health check every normal app deploy gets. You don't write or see a compose file unless you go looking for it.
Step 3: Point a domain at it
If you didn't set one during deploy, add an A record for your domain pointing at the server's IP, then set the Custom domain on the app's Config tab and redeploy. DeployOS requests a Let's Encrypt certificate automatically the first time HTTPS traffic reaches it n8n needs HTTPS for webhook nodes and OAuth-based integrations to work correctly, so this step isn't optional the way it might be for an internal tool.
The domain card polls in the background and shows you the moment DNS has propagated and the certificate is live, so you're not stuck refreshing the tab.
Step 4: Back up the workflow database
n8n's actual value your workflows, credentials, and execution history lives in its database, not in the container. From the app's Databases section, turn on scheduled backups; DeployOS supports pushing them offsite to S3-compatible storage if you don't want backups sitting on the same box as the app they're backing up. This is the step that's easy to skip when you're just trying to get n8n running, and the one you'll actually care about the day a workflow gets deleted by accident.
Step 5: Treat it like any other app
Once it's deployed, n8n shows up on your Applications list like anything else you've deployed logs, restart, and monitoring all work the same way. If n8n ever stops responding, the built-in Doctor runs a 9-step check (DNS, ports, proxy, container health, and more) and tells you in plain English what's actually wrong, instead of leaving you to guess between "container crashed" and "certificate expired."
Beyond n8n
The same template flow works for the rest of the automation and admin-tooling shelf DeployOS ships 236 one-click templates in total, and n8n pairs naturally with things like Uptime Kuma for monitoring the webhooks it triggers, or a password manager like Vaultwarden for the credentials n8n's nodes need. All of it runs on the same server, behind the same reverse proxy, backed up on the same schedule.