Self-hosted CI brings control over execution—and more infrastructure to understand. Runnerly connects runner state, job activity, and repository policy in one authenticated operating view.
GitHub sign-in required. Access is currently limited to the authorized operator.
runnerly.
By CaeliCode
Explore the proposed dashboard redesign. The live application remains access-controlled.
RunnerlyInterface preview
Product interface · Illustrative data · Private fleet details are not shown.
An operator needs to connect the runner, the job, the repository, and the execution lane. Those answers can be scattered across GitHub events, inventory, and local knowledge.
The goal was to bring that context together while keeping GitHub in charge of scheduling. The operating view also needed to recover from missed events, respect repository boundaries, and retain records for investigation.
Each choice addresses a specific failure mode, with a deliberate limit to the system’s responsibility.
Signed webhooks update the view quickly. Runner refresh and full reconciliation bring it back into line when events are delayed, missed, or out of date.
GitHub remains the source of truth. Runnerly maintains an operating record; it does not replace the scheduler.
GitHub sign-in and organisation authorisation protect the dashboard. Inside it, policy views distinguish public-repository telemetry from the restricted execution lanes used by private repositories.
Runner-group and repository settings in GitHub enforce execution access. The dashboard makes those boundaries visible.
SQLite brings normalised jobs, events, and audit activity together. JSON and CSV exports support review, while local backup controls preserve copies of the record.
A local store keeps the staging deployment straightforward. High availability, offsite durability, and proven recovery remain separate work.
Observed in an authenticated review of the private staging system on 7 September 2026.
Real organisation-scoped runner records, labels, and state alongside repository and workflow inventory.
GitHub events and policy views in the same signed-in operating surface.
Working JSON/CSV evidence exports, audit views, and local backup controls.
Runnerly is a live CaeliCode engineering project with restricted GitHub authentication. The interface shown here is the proposed redesign, populated with sample data. It is not a customer case study.
The operating review established the views and exports above. It did not establish a complete runner lifecycle or a production recovery objective.
The engineering note documents authentication, state reconciliation, policy, and the remaining hardening work.
Read the Runnerly engineering noteWe can help assess the runner architecture, access boundaries, and visibility your team needs.
Discuss your platform