Hey guys,
Our company was looking into GitHub Actions self hosted solutions to save on costs and to improve speed. One interesting project I came across was runs-on .
How is it different?
Setup was pretty simple and took around 20 minutes.
It can add top 10 contributor's SSH keys in case you want to debug the job (can be set to on or off for the whole org)
Also supports S3 bucket caching to regional S3 buckets which eliminates the 10 GB limit on GitHub cache, faster cache / restore times and to save on network costs.
Caution: I'm not affiliated with the product. Please do your own research in case you want to use the product.
Our company was looking into GitHub Actions self hosted solutions to save on costs and to improve speed. One interesting project I came across was runs-on .
How is it different?
- It uses VMs instead of containers / pods which is used in GitHub actions self-hosted solutions from other vendors and GitHub Action Runner Controller (ARC)
- Uses webhooks instead of long-polls used in ARC. I've had multiple issues with jobs not picking up and very slow startup times with ARC.
- Subscription instead of a minute-based calculation. You pay an annual fee of 300 EUR instead of every minute billing (Free for OSS).
Setup was pretty simple and took around 20 minutes.
It can add top 10 contributor's SSH keys in case you want to debug the job (can be set to on or off for the whole org)
Also supports S3 bucket caching to regional S3 buckets which eliminates the 10 GB limit on GitHub cache, faster cache / restore times and to save on network costs.
Caution: I'm not affiliated with the product. Please do your own research in case you want to use the product.
