Testimonials
Easy to setup. 85% cheaper than GitHub Actions.
Our main repository saw an average decrease in CI runtime of 35%. Another repository could fully utilize 16 threads, which dropped its runtime by 75%.
RunsOn helped reduce our monthly CI costs from $1100 to $400 (third-party SaaS), [i.e. 80% cheaper than GitHub]. Also because it is cheaper we increased the instance size, which made it faster and improved our iteration times by 2x.
Previously we used Github hosted runners for all of our build, test and lint jobs. After evaluating other options we settled on RunsOn as it allowed us to host runners within our own cloud, allowing us much greater control than some of the other SaaS hosted providers. With RunsOn, Github workflows run faster whilst still costing us 5-10x less than the Github hosted equivalent.
By leveraging AWS with ECR, RunsOn helped cut our cache restore and image pull times by 80% and 60% respectively. The added bonus of an unrestricted distributed cache via S3 for developer workstations, GPU spot instances via EC2 for our simulations, and retained GitHub Action integration more than justified our infrastructure migration.
I've been testing Kubernetes with ARC: more complex, each runner takes ~25 seconds to boot (on an existing node), far less attractive than the simplicity of RunsOn.
Less than 10 min to test, install and use the product. You can finetune any workflow (CPU, RAM, machine type/size..) depending on your needs. The cache download speed is blazing fast thanks to amazon s3 endpoint. Pricing is transparent, pay only what you use with no overage.
We've been using RunsOn for our organization's hosted GitHub Actions runner service and it has been a game-changer. The platform is reliable, user-friendly, and helps us streamline our workflows efficiently. We highly recommend RunsOn to anyone looking for a seamless CI/CD solution.
With RunsOn, we have increased CI/CD performance and reliability at a fraction of the cost of official or private hosted runners – it's a no-brainer for any DevOps team using GitHub actions at scale.
We've just started using self hosted runners, and we were looking into possible solutions, including running them in Kubernetes, but then we found RunsOn: it's definitely what we needed! The fact that instances are compatible with the github hosted runners made the transition very smooth.
We used the default GHA runners before. The main reason for switching was the need for ARM runners. Overall I'd say we've seen a 2-3x speedup for ~25% of the GHA cost.
CI times are down from ~30 mins to 12 mins, thanks to the larger instances. S3 being faster also helped our one not-very-parallel job.
We've been using RunsOn for the past three months, and the impact on our workflows has been remarkable. Our build times have reduced by 50%, dropping from 20 minutes to just 10 minutes. Moreover, we've seen a drastic reduction in our CI/CD costs, which have decreased from $1,400 per month with GitHub Runners to just $70 per month.
We also tried Action Runner Controller to set up self-hosted runners on EKS, but RunsOn blows that out of the water. When compared with the ease of installation, pre-warmed instances, fast boot times, and minimal admin overhead, RunsOn is clearly the superior solution.
It's a no-brainer for anyone using GitHub Actions but has proven to be an invaluable tool for improving efficiency and reducing costs in our development pipelines.
We did a review of alternative solutions, from Buildjet to Warpbuild, and we ended up with RunsOn. Right now it is the best compromise: runners boot fast, and it's very cost efficient at scale.