OpenRunnersSign in

Invite onlyBuilt for GitHub Actions

Clean runners.Clear proof.

OpenRunners creates a fresh GitHub Actions runner for every job, removes it after execution, and keeps a verified record of what happened.

See how it worksSign in if invited
Illustrative runVerified
workflow / jobbuild / linux
01J8F2
  1. 01Observed
  2. 02Admitted
  3. 03Running
  4. 04Recorded
  5. 05Removed
Execution completeRunner removed. Evidence retained.runs-on: openrunners-8vcpu-ubuntu-2404
Runner
Fresh for this job
Idle compute
None
Cleanup
Confirmed
Record
Retained

01 — Switch

Keep GitHub Actions. Change one line.

Keep your workflows, checks, logs, and artifact flow. Select an approved repository and use an OpenRunners label.

Explore the platform
Beforeruns-on: ubuntu-latest
Afterruns-on: openrunners-8vcpu-ubuntu-2404

02 — Lifecycle

From job request to runner removal.

Each handoff has a named state. You can see where a run is, what failed, and whether cleanup finished.

  1. 01Observed

    GitHub sends the job request.

  2. 02Admitted

    Policy accepts the workload.

  3. 03Running

    A fresh runner connects.

  4. 04Recorded

    The result becomes durable.

  5. 05Removed

    The runner is destroyed.

03 — Evidence

The machine goes away. The proof stays.

Guest output stays separate from authoritative platform state, so the record tells you what is verified and what is not.

Run record01J8F2
Cleanup verified
Lifecycle
Ordered platform events
Failure class
Workflow or infrastructure
Cleanup
Confirmed or explicitly uncertain
Access
Dashboard, API, CLI, and MCP
Read the security model

Limited access

Limited access. Real workloads.

Public registration is closed while approved teams validate the isolation, reliability, and operating model.

View pricingSign in if invited