July 9th, 2024

Runs-on: Self hosted, on-premise, GitHub Action runners

A new self-hosted runner solution, RunsOn, integrates with AWS to offer GitHub Actions users cost-effective and efficient CI/CD processes. Users benefit from faster builds, cost savings up to 80%, and customizable runner specifications.

Read original articleLink Icon
Runs-on: Self hosted, on-premise, GitHub Action runners

A new self-hosted runner solution called RunsOn offers a significant cost reduction for GitHub Actions users, with prices starting at $0.0006 per minute for ARM64 runners. The service, fully integrated with AWS, promises faster builds and unlimited concurrency, making it up to 15 times cheaper than GitHub's official runners. Users report substantial decreases in CI runtime and cost savings of up to 80%. RunsOn provides easy installation through a CloudFormation stack, one-click upgrades, and metrics for monitoring usage. The platform supports various CPU and RAM configurations, including ARM64 architecture, and offers features like SSH access, static IPs, and dynamic instance selection. Users praise RunsOn for its performance, scalability, and compatibility with GitHub runners. The service is recommended for DevOps teams seeking a cost-effective and efficient CI/CD solution, with the flexibility to customize runner specifications based on workflow requirements.

Link Icon 3 comments
By @branon - 5 months
on-premises, not on-premise. but if these are hosted in AWS and aren't actually on-premises, maybe use of the term is not correct at all?
By @gsck - 5 months
On-premise, in the cloud, on someone else's premise. The future is now!
By @bracketfocus - 5 months
If we already have some EKS clusters setup, is there a benefit to this over Actions Runner Controller (ARC)?

https://github.com/actions/actions-runner-controller