Runnerly is a control room for the runner layer GitHub does not manage for you: fleet readiness, repository policy, tokenized enrollment, and CI audit trails.
Runnerly sits beside GitHub Actions and turns self-hosted runners into an observable, governed fleet instead of a set of machines people hope are still alive.
Heartbeats, labels, architecture, status, runner scope, and recent checks from managed agents and GitHub events.
# GET /api/runners
{
"name": "caelicode-runner-01",
"labels": ["self-hosted", "linux", "arm64"],
"status": "online",
"heartbeat": "18s ago",
"checks": { "actions_runner": "ok" }
}Allowed repositories, required labels, and online runner coverage checked before the workflow gets stranded.
Short-lived registration tokens minted through a GitHub App, scoped to a repository and issued only when needed.
sudo GITHUB_OWNER=caelicode \
GITHUB_REPO=runnerly \
RUNNER_LABELS=linux,arm64 \
bash install-github-runner.shEvery workflow job links back to its repository, runner labels, webhook delivery, and operator events.
The control plane receives workflow events, keeps a system of record, coordinates runner agents through authenticated API calls, and gives operators a private dashboard for readiness and audit trails.
Runnerly is an operations product running against real runner fleets. It makes runner ownership clearer while the broader product surface expands.
Pick a repository, register a runner with the required labels, watch a workflow job land, then decide whether the operating model deserves a wider rollout.
Scope it to the repositories Runnerly is allowed to observe and manage.
Declare required labels and confirm that the fleet can satisfy them.
Use a short-lived registration token and the generated install command.
Watch queue, pickup, runner identity, and audit evidence in the dashboard.
$ curl /api/onboarding
[ok] repository policy loaded
[ok] matching runner found
$ bash install-github-runner.sh
[ok] runner registered
[ok] heartbeat received
$ gh workflow run onboarding.yml
[ok] workflow_job queued
[ok] runner matched
[ok] audit event recordedNo. GitHub still schedules the work. Runnerly sits beside Actions and owns runner readiness, policy, enrollment, and evidence.
No. Runnerly is live for real runner operations, with access still controlled while the broader product surface matures.
No. Your runners stay in your environment. Runnerly talks to them through authenticated API calls and GitHub events.
Runner registration tokens are minted through a GitHub App, scoped to the target repository, and short-lived by design.
In the Runnerly deployment you operate. The dashboard and API expose runner, repository, job, webhook, and operator events.
Start with one repository and one self-hosted runner. Prove the operating model, then decide how far Runnerly should go.