What engineers say

ParadeDB needed a tool to run benchmarks in a perfectly reproducible environment. RunsOn enabled us to run on bare metal instances with the convenience and familiarity of GitHub Actions at a fraction of the cost. Everything has worked smoothly from day one. We've switched our entire benchmarking infrastructure to be powered by RunsOn.

After benchmarking a lot of tools, it's the best. We run thousands of jobs per day. Costs divided by 4.

Your product is amazing and I can choose machines 4x the size we had before. It made our entire suite 12 minutes instead of 23+. I did not expect an increase in speed or resources so that was a very pleasant surprise.

Monumental improvements with our work pipelines though. Everything is more consistent. The ephemeral nature of the runners that we gain along with the power and cost-effectiveness of using short-term aws machines is just a no-brainer. I honestly can’t think of any downsides. Just an overall improvement everywhere.

Cyril responds to emails even from trial customers super quickly. And some of the "magic features" are so nice - especially that the whole team's SSH keys are imported from github and you can just SSH into any box without setup 🪄

We have been using RunsOn for more than half a year and are delighted by cost, speed benefit and easy maintenance. Cyril is super responsive on requests and always moving the product forward. I have been promoting it to other friends, who adopted it for their companies. My favourite product this year!

Reduced GitHub Actions costs by 70%, CI runtime improved by up to 80%. A clear win with virtually no downside.

We've been using RunsOn for a short while and have already seen massive savings compared to using GH actions with larger runners. The ease of setup is also amazing, where it says on the website that it will take 10 minutes to setup I think that's understating how simple and quick it is to get going.

Saved around 75% our costs, tests now run 5x faster with gigantic spot instances.

Very easy to set up, very stable. Documentation is really good and the support is reactive. RunsOn allowed us to provide any kind of runner, while being confident that the pricing would be okay. Way more comfortable than homemade self-hosted, I strongly recommend it !

We started adopting runs-on.com on aptos-core a few months ago and it's been great! We were able to both reduce cost and decrease duration of our jobs, running hundreds/thousands of jobs on very large machines daily. This replaced our previous usage of the k8s-based github actions-runner-controller.

Some noteworthy additional callouts:

1. RunsOn's built-in S3-powered caching support (with virtually infinite cache size and very fast upload+download speed) helped reduce some of our builds runtime (incl. docker builds) quite a lot, which is something we didn't even count on.
2. The author has been extremely responsive (better than bigger startups/competitors) to fixing bugs or implementing feature requests, often times making improvements within just days.

It's super simple to configure and use, it's stable and actually cut costs. So far, no downsides. It's working super well, our cost decreased by 90%. One engineer in our team was considering developing a similar tool, because Github Actions was getting too expensive too fast. He searched it online (google) and brought as an option to the team. 

RunsOn is a true turnkey CI/CD solution. We’ve achieved up to 55% savings compared to our GitHub and in-house self-hosted runners. The transition to RunsOn was smooth, and we’re never looking back! Cyril has also been extremely responsive to the team's queries and resolved any issues quickly. Using GitHub? You need RunsOn.

We're in the process of moving from CircleCI to Github Actions. We've been using Actions Runner Controller on EKS, but hit a number of scaling issues, job pickup delays, and job cancellations.

We started trialing RunsOn to see how other options might fair compared to ARC and have been thoroughly impressed.

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%.

Timo Schäfer Software Engineer at Wikando

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.

Alec Mocatta Founder at Tably

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.

Tim Petricola Software Engineer at Alan

Less than 10 min to test, install and use. Cache download speed is blazing fast.

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.

Alec Mocatta Founder at Tably

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.

Discovered during the recording of a podcast, we changed all our CI/CD runners to RunsOn. Thanks to Julien Danjou (from Mergify) for the discovery, and Cyril Rohr for the incredible product and support. ❤️