n8n on your VPS, production-ready in one click

Here's what it looks like in the panel

Everything a serious n8n setup needs, already built

The panel installs and maintains the full stack. You focus on the workflows.

• Full stack in one click: Main process for the editor and the webhooks, N queue-mode workers, PostgreSQL 18 and Redis 7 inside the same Docker Compose stack. No separate database or Redis to install.
• A check before you install: The panel shows you whether Docker is ready, how much RAM is actually free, how many workers fit and how much memory each option asks for, with one recommended.
• Workers your way: From 1 to 8 workers (4 by default) and the concurrency per worker (5 by default). Ask for more than fit in RAM and they get trimmed, with a notice.
• Scale without downtime: Adding workers interrupts nothing. When you remove them, there's a grace period so running executions can finish.
• Your domain with HTTPS: nginx is set up as a reverse proxy, and the editor and webhook URLs update themselves. You can change the domain as many times as you want.
• Safe updates: Pick the version and it updates in the background. The database is backed up first, and if the new version won't start, it rolls back on its own.
• Environment variables without fear: Edit several at once and they apply in a single restart. Secrets are shown masked, and the critical variables (encryption key, database credentials) are protected.
• Backups and maintenance: Daily database dump with 7-day retention, log rotation for every container, and execution history pruned after 14 days so the disk doesn't fill up.
• Isolated Code node: Each n8n process has its own task runner (the external mode n8n recommends for production): code that escapes the sandbox can't see the encryption key or the credentials.
• No execution limit: No quota per plan or per workflow: the ceiling is the VPS's RAM and CPU, and you see it before installing.
• Your data stays on your VPS: The n8n database, the credentials and the execution history live on your server, with your root access and your backups.

From zero to n8n on your own domain

1. Pick a VPS with enough RAM: n8n needs at least 4 GB of RAM actually free. The plan table tells you which ones run it comfortably.
2. Review and pick workers: The panel works out how many workers fit and recommends a configuration.
3. Install in one click: The full stack comes up with Postgres and Redis. You follow the progress from the panel.
4. Add your domain: You assign a domain with HTTPS and the webhooks point to it automatically.
5. Scale when you need to: Adding workers doesn't interrupt the service. When you remove them there's a grace period so running executions can finish.

How it works underneath, and what to keep in mind

• It's the deployment n8n itself recommends for production: queue mode with Redis in between, the main process separate from the workers and PostgreSQL as the database, all inside the same Docker Compose stack.
• The main process serves the editor and the webhooks; the workers execute. That's why a heavy execution doesn't leave the interface hanging, which is the typical problem with n8n installed on SQLite as a single process.
• You need at least 4 GB of RAM actually free, and it's the available memory that gets measured, not the plan's. Roughly: 4 to 5.9 GB fits 2 workers, 6 to 7.9 GB fits 3, and from 8 GB up it's 4 or more, capped at 8.
• Each process has its own task runner in external mode, which is what n8n recommends for production: Code node code runs isolated and, if it escapes the sandbox, it can't see the encryption key or the credentials.
• Docker has to be enabled. If it isn't yet, enabling it reboots the VPS, and the panel asks you to confirm first.
• It needs Node 20 or later, which in turn requires glibc 2.28. That's why it doesn't run on Ubuntu 16.04 (glibc 2.23) or 18.04 (glibc 2.27). It's verified in production on 22.04 and compatible with 20.04, 24.04 and 26.04.
• To assign a domain, that domain has to have HTTPS set up first. After that the editor and webhook URLs update themselves every time you change it.
• n8n's schema migrations can't be undone. The automatic rollback covers the new version failing to start; to go back a version you restore the pre-update backup, which is always taken before updating.
• Maintenance runs on its own: daily database dump with 7-day retention, log rotation for every container, and execution history pruned after 14 days so it doesn't fill your disk.
• Installing, updating, scaling workers and editing environment variables are for Company administrators. Members can see the status and the logs.
• Real root over SSH: the panel is a shortcut, not a cage. Anything it does with a button, you can also do by hand.

Or just ask Claude, ChatGPT or Cursor

Everything you see in the panel, your AI agent can do through the ArduMaker MCP server: with your authorization, within the scope you grant, and with every action audited. See what the MCP does

Frequently asked questions

Services that go well together

• Docker: Enable Docker in one click and manage images, containers, logs, volumes and networks from the panel.
• PostgreSQL: Install PostgreSQL and manage databases, users and permissions without the command line.
• Domains and SSL: A free subdomain or your own domain with Let's Encrypt, an nginx proxy with rollback, and port forwarding.