Wiki· Updated 19 Oct 2026
Automations
How RunStack automations work: one-command service install, management, upgrades, removal.
A RunStack automation installs a ready service on your server with one command: Docker, HTTPS with Let's Encrypt, backups, IP allow-list. You answer a few questions — the installer does the rest.
Available now:
- HashiCorp Vault — a secrets store.
- Vaultwarden — a password manager compatible with the Bitwarden apps.
- n8n — workflow automation with PostgreSQL.
- Open WebUI + Ollama — your own AI chat on local models.
- Uptime Kuma — uptime monitoring with alerts.
- Outline — team wiki and knowledge base.
- Immich — your own Google Photos.
Also — server scripts: what is on the server, why it is slow, security check, Docker cleanup.
How it works:
- After you sign in, the service page shows an install command with your personal token (valid for 12 hours).
- The command downloads the installer, verifies its checksum and asks for the settings.
- The installer checks the server (OS, memory, disk, ports, the domain's DNS), installs Docker and starts the service.
- From then on the
rscommand on the server manages it.
More:
In this section
- Install: what you need and how it goesServer requirements, installer questions, unattended install from variables or a file.
- The rs command: managing a serviceStatus, logs, backups, upgrades, IP access, stopping and removing RunStack services.
- When the install failsCommon RunStack automation install errors and what to do about them.
