4 ms·
> 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
by crohr 2y 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 https://runs-on.com. 1-click install, 1-click upgrades, and from 7x to 16x cheaper runners on AWS.
- threecheese 2y agoBrilliant idea!! I just dug through your docs. You significantly undercut GitHub on runner pricing, using your customers’ infrastructure for both runners and their orchestration, which is managed by your software, some cloudformation, and amis that you maintain and license in return for a small slice of that savings. I love it, and if our cloudops org ever threatens to charge back CI to our budget I’ll be a customer.