Quick start
Create an account, connect Hetzner Cloud or DigitalOcean and GitLab, start your first runner and run a job on it.
This guide takes you from a new account to a CI/CD job running on your own runner. It takes about 15 minutes, most of it waiting for the server to start. It uses a GitLab runner; for a GitHub Actions runner, choose GitHub under Platform in step 5 and follow GitHub setup instead of step 4.
You need:
- A Hetzner Cloud account or a DigitalOcean account. This guide uses Hetzner; the DigitalOcean differences are noted where they matter.
- A GitLab project on GitLab.com or on your own GitLab instance, where you have the Maintainer or Owner role.
- An authenticator app for two-factor authentication.
1. Create your account
- Open https://app.managerunners.com/register.
- Enter your email address, given name, family name and a password. The password needs at least 8 characters with an uppercase letter, a lowercase letter, a number and a symbol.
- Select Create account.
- Scan the QR code with your authenticator app, enter the 6-digit code and select Verify & Continue.
Two-factor authentication is always on. You enter a code from your authenticator app every time you sign in.
2. Choose a plan
The dashboard opens Billing until your organization has an active plan. Choose a plan and complete the checkout. Every plan includes unlimited runners; schedules and autoscaling need Pro or Enterprise. See Billing and plans and pricing.
3. Create a Hetzner API token
Manage Runners creates and deletes servers in your Hetzner project, so it needs a token with read and write access.
- In the Hetzner Cloud Console, create a project for your runners, for example
gitlab-runners. A separate project keeps runner servers apart from your other infrastructure. - Open the project, go to Security > API tokens and generate a token with Read & Write permission.
- Copy the token. Hetzner shows it only once.
Optional: to log in to the runner servers over SSH, add your public key under Security > SSH keys in the same project. You can select it when you create the runner.
See Hetzner setup for details.
Using DigitalOcean instead? Create a personal access token with the custom scopes listed in DigitalOcean setup; SSH keys come from your account under Settings > Security. In step 5, choose DigitalOcean under Cloud provider.
4. Create a GitLab runner and copy its token
GitLab issues a runner authentication token (it starts with glrt-) when you create a runner in the GitLab UI. Manage Runners uses this token. The older registration tokens are not used.
- In your GitLab project, go to Settings > CI/CD and expand Runners.
- Select New project runner.
- Add the tags your jobs will use, for example
hetzner, or select Run untagged jobs. - Select Create runner and copy the runner authentication token.
You can also create group or instance runners. See GitLab setup.
5. Create the runner
In the dashboard, select Create Runner and fill in the form:
| Field | What to enter |
|---|---|
| Platform | GitLab for this guide. GitHub shows the repository or organization and token fields described in GitHub setup instead of the GitLab fields. |
| Cloud provider | Hetzner or DigitalOcean, shown when both are offered. Changing it clears the product, location, token and SSH keys. |
| Name | Optional. A name with letters, numbers, spaces and dashes, for example build-01. Left blank, the runner gets a name such as swift-falcon. |
| Product | The Hetzner server type or DigitalOcean droplet size. Each option shows the CPU architecture, vCPUs, RAM and disk. |
| Location | The provider’s location. Each option shows the provider’s monthly net list price. |
| Executor | docker for most projects. See executors. |
| Concurrency | How many jobs run at once. Selecting a product sets it to twice the vCPU count. |
| GitLab Host | https://gitlab.com/, or the base URL of your self-managed GitLab instance. |
| GitLab Runner Token | The glrt- token from step 4. |
| Hetzner Auth Token | The token from step 3. The form checks it, loads the project’s SSH keys and saves it to your organization, under the optional Name or after the runner, so later runners can pick it without entering it again. Once your organization has a saved token, the form shows Hetzner API token with it; choose Enter a new token for another one. For DigitalOcean, the field is DigitalOcean API Token. |
| Hetzner SSH Keys | Optional keys for root access to the server; DigitalOcean SSH Keys for a droplet. |
| Labels | Optional labels that are attached to the Hetzner server. DigitalOcean droplets get no labels. |
| Metrics | Optional. Show in dashboard adds CPU, RAM, swap (if the server has swap), running jobs (GitLab runners) and disk charts to the runner card; Send to sends the same metrics to one of your connections. Both need an active plan. See Metrics. |

Select Create. The dashboard shows the runner as Creating while your provider starts the server, then Configuring while it installs GitLab Runner. After a few minutes it changes to Active.

If the runner shows Invalid Gitlab Token instead, GitLab rejected the token. Select Fix on the runner and paste a new one.
6. Run a job
In GitLab, the runner now appears under Settings > CI/CD > Runners as online. Add a job to .gitlab-ci.yml that uses its tag:
hello:
image: alpine:latest
tags:
- hetzner
script:
- echo "Running on my own Hetzner runner"
Commit the file. GitLab assigns the job to your runner. If you selected Run untagged jobs, the tags section is not needed.
7. Pause it when you don’t need it
A runner costs server time at your provider while it is active. Select Pause on the runner card to delete the server, either after the running jobs have finished or at once. The runner keeps its configuration and its IP addresses, so firewall rules and allow lists that mention them keep working. Select Resume to create a fresh server with the same settings.
To pause and resume automatically, for example outside working hours, set up a schedule. Schedules need a Pro or Enterprise plan.
Prefer the command line?
The same steps with the manage-runners CLI, after the account and plan exist:
manage-runners auth login --scope runners:write
manage-runners product list
manage-runners product locations --id hz-cpx31
export HCLOUD_TOKEN GLRT_TOKEN # set them from your secret manager
manage-runners runner create --name build-01 --product-id hz-cpx31 --location fsn1 \
--executor docker --concurrency 8 --gitlab-host https://gitlab.com/ \
--runner-token-env GLRT_TOKEN --hetzner-token-env HCLOUD_TOKEN --wait
See Manage runners with the CLI for every option.
Next steps
- Learn the runner states and which changes recreate the server.
- Invite your team to an organization.
- Create a personal access token for scripts and CI jobs.