runs-on/runs-on — Self-hosted GitHub Actions runners made simple.

Description and use

**Brief summary**
Runs‑on (runs‑on/runs‑on) is an open‑source tool that simplifies the deployment of self‑hosted GitHub Actions runners on AWS, delivering up to 10× lower cost, ~40 % faster job execution, and unlimited build‑cache storage. It positions itself as a leaner, faster alternative to the Actions Runner Controller for teams that want to run CI/CD workloads on their own infrastructure.

**Value proposition**

• **Cost & speed** – By leveraging spot instances and native AWS networking, runs‑on reduces the per‑job expense dramatically while cutting latency compared with the default GitHub‑hosted runners.
• **Unlimited caching** – Persistent EBS/EFS volumes give you unbounded cache size, which speeds up dependency installation and artifact reuse across workflows.
• **Simplicity** – A small set of Terraform modules and a CLI handle provisioning, registration, and lifecycle management, so you don’t need to maintain a full Kubernetes‑based controller stack.

**Practical adoption path**

1. **Pilot** – Clone the repo, run the provided Terraform scripts in a sandbox AWS account, and register a runner with a test repository. Verify that jobs complete faster and at lower cost.
2. **Integration** – Add the runner’s ARN to your GitHub organization/repo settings, update your workflow files to target the custom runner label, and optionally enable the shared cache volume.
3. **Scale** – Adjust the Terraform variables (instance type, spot vs. on‑demand, autoscaling thresholds) to match your workload. Use the built‑in health‑check Lambda to automatically replace unhealthy instances.
4. **Governance** – Incorporate the Terraform state into your IaC pipeline, apply IAM least‑privilege policies, and set up CloudWatch alarms for cost and performance monitoring.

**Production readiness**

• **Maturity** – 1,181 ★ and recent activity (last update 2026‑05‑12) indicate a healthy community, but the project is still categorized as “medium” readiness.
• **Risks** – Integration documentation is sparse; you’ll need to manually verify networking (VPC, security groups) and cache persistence. Dependency management (Terraform version, AWS SDK) should be locked down before production rollout.
• **Recommendation** – Suitable for internal tools, prototypes, or teams that can allocate engineering time to validate the setup and monitor costs. With proper testing and a clear maintenance plan, runs‑on can be promoted to production for most CI/CD workloads.

Problem

runs-on/runs-on helps teams persist, query, and move data with less custom plumbing.

Outcome

Medium: useful for prototypes or internal workflows, with dependency and maintenance checks before production.

Workflow

• manage persistence
• speed up data access
• prototype database-backed apps

Evidence

Self-hosted GitHub Actions runners made simple. For AWS. 10x cheaper, 40% faster, and unlimited caching. Best alternative to Actions Runner Controller.

Source