Comment by arusahni
5 days ago
> We still use GitHub Actions but our monthly bill is now flat because we pay for a server.
Caveat here being that GitHub is exploring charging a usage-based fee for self-hosted GitHub Action runners [1]. While they've halted it for now, it's something worth being aware of as you assess your costs. This is probably a drop in the bucket compared to the order of magnitude savings you've described.
[1]: https://github.blog/changelog/2025-12-16-coming-soon-simpler...
Allegedly this is because whenever you have a self-hosted runner, it's actually a Microsoft-hosted runner that is notifying your runner and then polling for it to complete. I wish I was joking.
Self-hosted runners make a ton of API calls during job execution, so they might not be completely wrong here.
That's for console output and status.
Also note that managing self-hosted runners with Kubernetes is no walk in the park.
Haha, we don't use Kubernetes. It is a single large server with plenty of space for runners. It is as simple and boring as it gets. The only fun part is that we use Firecracker for the actual runners. It is provides nice isolation and it is very easy to work with.
https://fireactions.io/ ?
1 reply →
Thanks. I did not know.