CI Runnerscirunners.org
Glossary

What is ephemeral runner?

Answer in brief

A runner that takes exactly one job and is then destroyed, so every job starts from a clean machine and nothing carries over.

By the CI Runners editors · Updated

Ephemeral runner in CI

An ephemeral runner is registered for a single job. When the job ends, the runner deregisters and its machine, pod or microVM is deleted. The next job gets a new one. This is how hosted runners behave, and GitHub recommends autoscaling self-hosted runners only in this form.

The benefits are security and repeatability: a compromised or careless job cannot leave files, processes or credentials for the next one, and builds do not depend on leftovers. The cost is that local caches vanish with the machine, which is why runner products add remote caches and Docker layer caching.

Sources

  1. docs.github.com/en/actions/reference/runners/self-hosted-runners
  2. docs.github.com/en/actions/reference/security/secure-use

Check before you rely on it. Products change quickly, and this page reflects public documentation as of November 22, 2026. Confirm anything that matters in the provider’s own documentation.

Cite this page

CI Runners. (2026). What is ephemeral runner?. cirunners.org. Last reviewed November 22, 2026. https://cirunners.org/glossary/ephemeral-runner/