Zum Hauptinhalt springen
Automation

Self-host Rundeck on a VPS

Centralised job scheduling and runbook automation.

Define, schedule and run operational jobs across servers with approvals and audit trails.

Why self-host Rundeck?

Rundeck brings structure and auditing to ops jobs that would otherwise be ad-hoc shell on each box.

How to install Rundeck

  1. 1

    Provision a VPS

    Choose a plan with room for your data as well as the app.

  2. 2

    Install the stack

    Install Java + (Postgres/MySQL).

  3. 3

    Deploy the application

    Follow the project’s official install guide for your distribution.

  4. 4

    Enable HTTPS

    Serve it on your own domain behind a reverse proxy with a certificate.

  5. 5

    Back it up

    Schedule a database dump plus a copy of any uploaded files to an off-box location.

Practical tips

  • Give Rundeck its own database user with rights only on its own schema.
  • Reverse-proxy Rundeck and terminate TLS at the proxy so certificates are managed in one place.
  • Take a VPS snapshot before major upgrades so you can roll back cleanly.
  • Keep Rundeck patched — most self-hosting incidents are unpatched software.

Frequently asked questions

How much RAM does Rundeck need?
Plan on 2–4 GB for typical use; add headroom if you expect many concurrent users.
What stack does Rundeck run on?
Java + (Postgres/MySQL).
Can I run other things on the same VPS?
Yes — size the plan so Rundeck plus your other workloads fit in RAM with room to spare.

Looking for something else? Popular alternatives include Ansible AWX, Windmill, Jenkins — browse all app guides.