My CI bill was over $1,000 last month.
That's what happens when agents ship all day. One repo hit 522 PR attempts in 2 weeks. CI isn't a checkbox anymore. It's the bottleneck and one of the biggest line items.
So I built a ci-health skill: measure, find the top failure, fix the root cause, gate it so it never comes back.
And I just signed up for @usejog. One line in runs-on, runners up to 80% cheaper than GitHub's.
Ship faster. Spend smarter.
you’d be crazy not to switch to @usejog
Replying to @poornima
Claude Code, Codex, Dot, Bot, and friends.
@usejog has a good one: usejog.com/
We’ve almost doubled our compute capacity since this post. Just waiting for the servers to be delivered.
In recent years, GitHub actions have often been in an unavailable state, with long queuing times leading to CI failures. We can consider using third-party CI services as an alternative. Jog @usejog is a good choice, you can earn 5000 credits through my invitation link. usejog.com/join/handsomezhuz…
CI is now #2 on my list of costs, right below tokens.
Our GitHub Actions usage went from $341 in August to $3,096 in October, that's insane!
Had a chat with @mattgapp about some options to save money without slowing everything to a halt!
1) AWS Spot + @RunsOnRunsOn
TIL, Spot is discounted spare computing capacity from AWS. You can rent it cheaper, but AWS can reclaim it when it needs the capacity back.
RunsOn connects GitHub Actions to runners in your own AWS account, so you don’t have to build all the plumbing yourself.
Works even better if you have both GitHub and AWS credits!
2) Rent servers from cheaper providers like @OVHcloud or @Hetzner_Online.
Run your own GitHub Actions runners there, or use @buildkite to manage the pipelines. More stuff to maintain, but worth looking at.
3) Use a managed runner provider like @usejog or @useblacksmith.
Both are pitching cheaper and faster GitHub Actions runners. From my explorations, Blacksmith seems more focused on speed and caching, while Jog is really pushing on price. Both claim savings, so we’ll see what happens on our actual builds.
Probably worth trying them on our actual builds rather than comparing landing-page numbers.
We're going to see a lot more of these popping up! @boatdotdev is another interesting one on the VM/CI side. Will check them out!
Had a fun chat with @0xZoZoZo who is shipping like crazy. My recommendation was 1) if you have free money (cloud credits) and you don't have something better to spend them on, then use them for CI or 2) if you don't have free money, then you should consider alternatives like Blacksmith or @usejog. We're very focused on speed and caching btw - check out Jog Max.
CI is now #2 on my list of costs, right below tokens.
Our GitHub Actions usage went from $341 in August to $3,096 in October, that's insane!
Had a chat with @mattgapp about some options to save money without slowing everything to a halt!
1) AWS Spot + @RunsOnRunsOn
TIL, Spot is discounted spare computing capacity from AWS. You can rent it cheaper, but AWS can reclaim it when it needs the capacity back.
RunsOn connects GitHub Actions to runners in your own AWS account, so you don’t have to build all the plumbing yourself.
Works even better if you have both GitHub and AWS credits!
2) Rent servers from cheaper providers like @OVHcloud or @Hetzner_Online.
Run your own GitHub Actions runners there, or use @buildkite to manage the pipelines. More stuff to maintain, but worth looking at.
3) Use a managed runner provider like @usejog or @useblacksmith.
Both are pitching cheaper and faster GitHub Actions runners. From my explorations, Blacksmith seems more focused on speed and caching, while Jog is really pushing on price. Both claim savings, so we’ll see what happens on our actual builds.
Probably worth trying them on our actual builds rather than comparing landing-page numbers.
We're going to see a lot more of these popping up! @boatdotdev is another interesting one on the VM/CI side. Will check them out!





















