Manage Runners
Documentation menu

Manage Runners documentation

Run your own GitLab CI/CD and GitHub Actions runners on Hetzner Cloud or DigitalOcean, managed from a dashboard or the manage-runners CLI.

Manage Runners creates GitLab runners and GitHub Actions self-hosted runners as virtual machines in your own Hetzner Cloud project or DigitalOcean account. You choose the CI platform, the provider, the server type and the location. Manage Runners provisions the server, installs and registers GitLab Runner or the GitHub Actions runner, keeps its packages updated, and lets you pause, resume and schedule the runner, so you only pay your cloud provider for servers while you need them. On the Pro and Enterprise plans, autoscaling adds burst runners while a runner is busy.

How it works

  1. You give Manage Runners a Hetzner Cloud or DigitalOcean API token, and either a GitLab runner authentication token or a GitHub repository or organization with a fine-grained personal access token.
  2. Manage Runners creates a server in your Hetzner project or a droplet in your DigitalOcean account and installs Docker and GitLab Runner or the GitHub Actions runner on it.
  3. The server registers itself with your GitLab instance, GitLab.com or self-managed, or with your repository or organization on GitHub.com. See GitLab setup and GitHub setup.
  4. The runner picks up CI/CD jobs directly from GitLab or GitHub. Job traffic never passes through Manage Runners.

The servers belong to your Hetzner project or DigitalOcean account, and the provider bills you for them directly. Your Manage Runners plan covers the management. See Costs.

Where to start

Components

Component Address
Dashboard https://app.managerunners.com
API, used by the CLI https://api.managerunners.com
MCP server for AI assistants https://api.managerunners.com/mcp
CLI manage-runners, see Install