Cheap runners are just one part of the equation: nobody likes slow runs, even if it's cheap.
RunsOn gives you access to some of the fastest machines on the market, thanks to AWS extensive hardware selection.
Which makes RunsOn the fastest provider of self-hosted, fully ephemeral runners on the market.
We automatically build and publish copies of the official runner images at most 24h after their official release, so that you can be certain that your workflows will always work on either GitHub runners, or your own RunsOn runners.
RunsOn's answer:
10x cheaper than GitHub official runners. Runs in your own AWS account. More secure than sharing your secrets with other third-party tools like BuildJet or Warpbuild.
RunsOn's answer:
Cheap, fast, on-premise alternative to maintaining self-hosted runners.
RunsOn's answer:
CTO / Senior developers
RunsOn's answer:
Built a similar product for one of my clients, reduced CI build cost by 10 times, and improve build speed from 1h to 20min.
RunsOn might be a bit more popular than BuildJet for GitHub Actions. We know about 6 links to it since March 2021 and only 5 links to BuildJet for GitHub Actions. We are tracking product recommendations and mentions on various public social media platforms and blogs. They can help you identify which product is more popular and what people think of it.
Disclaimer: Co-founder of https://buildjet.com/for-github-actions While more cores can certainly help with certain types of projects, such as those that can be easily parallelized, this is not always the case. For example, web app projects won't benefit as much from additional cores. Another important factor to consider is the single-core performance of each vCPU. Many server-class CPUs, such as those used by... - Source: Hacker News / over 2 years ago
Congratulations on the launch. It looks pretty much like a self-hosted version of https://buildjet.com/for-github-actions. - Source: Hacker News / over 2 years ago
I'm a bit biased as one of the founders of BuildJet, but we solve this exact issue. BuildJet for GitHub Actions, plugs elegantly into GitHub Actions. With 1-line change in your config, you get 2x speed for half of GitHub's price. Check it out @ https://buildjet.com/for-github-actions. - Source: Hacker News / almost 3 years ago
With BuildJet for GitHub Actions, you can get up to 64 vCPU as a GitHub Actions runner. We plug right into your existing setup and have a significantly higher per core performance compared to the native runner. Check us out here: https://buildjet.com/for-github-actions. - Source: Hacker News / about 3 years ago
Incoming shameless plug; if you don’t have to handle the hosting runners, but still to reap the benefits of having proper hardware (close to the metal). Check out BuildJet for GitHub actions[1] - 2x the speed for half the price. Easy to install and easy to revert. [1] https://buildjet.com/for-github-actions. - Source: Hacker News / over 3 years ago
RunsOn is a self-hosted runner manager for GitHub Actions that you can install in your own AWS account. It will automatically spawn EC2 VMs as self-hosted runners for your GitHub Actions workflows. - Source: dev.to / 8 months ago
I'm working on https://runs-on.com, a self-hosted solution to get 10x cheaper GitHub Actions runners with support for Linux x64 and arm64. This month I've been refining Windows support and hopefully this gets fully shipped before Aug 31st! - Source: Hacker News / 8 months ago
You could also be interested in https://runs-on.com. Must be installed in your AWS account (1-click cloudformation template), and then you can use any instance type offered by AWS. - Source: Hacker News / 10 months ago
> We were using self-hosted runners which were not as efficient as we thought so we spawned EC2 instances and connected them to the github network to be runners, but we had such an amount of issues that we wanted to go back to non-self hosted For those hitting that same kind of issue (and you are many), you should check out my product https://runs-on.com. 1-click install, 1-click upgrades, and from 7x to 16x... - Source: Hacker News / 11 months ago
> while we can boot the Actions runner within 5 seconds of a job starting, it can take GitHub 10+ seconds to actually deliver that job to the runner This. I went the same route with regards to boot time optimisations for [1] (cleaning up the AMI, cloud-init, etc.), and can boot a VM from cold in 15s (I can't rely on prewarming pools of machines -- even stopped -- since RunsOn doesn't share machines with multiple... - Source: Hacker News / 12 months ago
Social Post - A simple way to send messages from GitHub Actions
Cirun.io - GitHub Actions on your Cloud!
GitHub Actions - Automate your workflow from idea to production
VS Code - Build and debug modern web and cloud applications, by Microsoft
Actionsflow - Free Zapier alternative based on Github Actions
Post to HackerNews - A Github action to post to news.ycombinator.com based on a github event (eg: git push)