runs-on
RunsOn is a self-hosted GitHub Actions runner service that runs in your AWS account, offering significant cost savings (7–15x cheaper than GitHub-hosted runners) and faster builds. It replaces the need for third-party runner providers or Kubernetes-based solutions like Actions Runner Controller, giving you full control over your CI infrastructure.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | runs-on/runs-on |
| Owner | runs-on |
| Primary language | Unknown |
| License | MIT — OSI-approved |
| Stars | 1.2k |
| Forks | 46 |
| Open issues | 13 |
| Latest release | v3.1.2 (2026-06-18) |
| Last updated | 2026-07-02 |
| Source | https://github.com/runs-on/runs-on |
What runs-on is
RunsOn deploys ephemeral VMs per job via CloudFormation templates, supporting Linux, Windows, and GPU runners with spot-instance pricing and automatic on-demand fallback. It integrates with GitHub Actions via a private GitHub App, provides S3-backed caching, and includes optional SSH and static IP networking features.
Get the runs-on source
Clone the repository and explore it locally.
git clone https://github.com/runs-on/runs-on.gitcd runs-on# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- Installation via CloudFormation template is documented as ~10 minutes; test in a non-prod environment first and validate GitHub App permissions and AWS IAM role scoping.
- Requires private GitHub App creation per organization; ensure GitHub org admins have permission to create apps and that secret rotation/revocation procedures are in place.
- Job label syntax differs from GitHub-hosted runners (e.g., `runs-on=${{ github.run_id }}/runner=2cpu-linux-x64`); existing workflows must be adapted.
- Spot-instance fallback to on-demand is automatic but adds cost; monitor and tune spot vs. on-demand allocation based on workload SLAs.
- S3 cache backend requires separate S3 bucket configuration and IAM permissions; existing GitHub Actions cache workflows may need migration.
When to avoid it — and what to weigh
- No AWS account or preference for platform-agnostic solutions — RunsOn is AWS-only. Teams using GCP, Azure, or on-premise infrastructure, or those avoiding cloud lock-in, should consider Actions Runner Controller (ARC) on Kubernetes or other multi-cloud alternatives.
- Minimal CI footprint or negligible GitHub Actions spend — Overhead of setting up and managing RunsOn (CloudFormation, networking, AMI maintenance) outweighs savings for teams with very light CI use. GitHub-hosted runners may still be cheaper and simpler.
- Requirement for dedicated support and SLA guarantees — RunsOn is a community/commercial product; production support, SLAs, and guarantees are not clearly available in the open-source repository. Critical workloads may need formal support contracts.
- Teams unfamiliar with AWS or infrastructure-as-code — Deployment requires CloudFormation expertise, AWS account administration, and comfort with VPC, IAM, and EC2 concepts. Non-infrastructure teams may struggle with initial setup and ongoing maintenance.
License & commercial use
The public repository is licensed under MIT (MIT License), which permits commercial use, modification, and distribution with minimal restrictions. However, the README states that commercial licensing, product access, and additional details are on the pricing page (runs-on.com/pricing/), indicating a dual-licensing or commercial support model not fully documented here.
MIT License permits commercial use of the code in this repository. However, RunsOn appears to operate as a commercial product (pricing page referenced, product access mentioned separately from open-source assets). Clarify with the vendor whether commercial deployment requires a separate license, subscription, or support contract beyond the MIT-licensed CloudFormation assets.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Adequate |
| License clarity | Needs review |
| Deployment complexity | Moderate |
| DEV.co fit | Good |
| Assessment confidence | High |
RunsOn runs jobs in your AWS account, reducing risk of unauthorized third-party access to code and secrets compared to external runner providers. However, security posture depends on proper AWS IAM scoping, VPC isolation, GitHub App permission minimization, and AMI hardening. No security audit or vulnerability disclosure policy is mentioned in the data provided. Ephemeral VMs per job reduce persistent attack surface, but misconfigured networking (e.g., overly permissive security groups or static IPs) could expose runners. Review AWS and GitHub security best practices before deployment.
Alternatives to consider
Actions Runner Controller (ARC) on Kubernetes
Multi-cloud (AWS, GCP, Azure, on-premise), Kubernetes-native, open-source, but requires Kubernetes cluster and operator expertise. Slower scaling and higher complexity than RunsOn.
GitHub-hosted runners (ubuntu-latest, windows-latest, etc.)
Zero setup, managed by GitHub, no cost for public repos. Higher per-minute cost (up to 7–15x), less control over hardware, smaller caches. Suitable for small teams or light CI workloads.
Third-party runner services (Buildkite, CircleCI, etc.)
Managed, platform-agnostic, strong support and SLAs. Requires delegating infrastructure to third parties and managing their API/permissions. Often comparable or higher cost than RunsOn.
Build on runs-on with DEV.co software developers
Start with the RunsOn installation guide (10 minutes), or reach out to clarify commercial licensing and support options for your organization.
Talk to DEV.coRelated on DEV.co
Explore the category and the services that help you build with it.
runs-on FAQ
Do I need a separate license to use RunsOn in production?
What happens if spot instances are unavailable?
Can I use RunsOn with private GitHub Enterprise?
Is the primary RunsOn codebase open-source?
Software development & web development with DEV.co
Need help beyond evaluating runs-on? DEV.co is a software development agency offering software development services and web development for teams of every size. Our software developers and web developers build custom software, web applications, APIs, and open-source devops integrations — and maintain them long-term.
Ready to cut CI costs and own your runner infrastructure?
Start with the RunsOn installation guide (10 minutes), or reach out to clarify commercial licensing and support options for your organization.