Cloud CI runners work well when you’re getting started with GitHub or GitLab. But as your team grows, CI turns into an operational burden. Costs rise, runners need tuning, and self-hosting starts to feel inevitable.
The real problem with CI today isn’t performance — it’s billing. You’re charged for the allocated instance resources, even if your job is mostly idle. We changed that.
RunMyJob uses a load-based billing model — you’re charged only for the CPU and memory your job actually consumes, measured every second in real time.
- High-performance VMs by default (12 vCPU / 32 GB RAM free)
- Business tier: 48 vCPU / 96 GB RAM
We don’t resell AWS or Hetzner. We run our own bare-metal infrastructure in Tier III data centers.
If you’re using GitHub Actions or GitLab CI and tired of managing runners or paying for overhead, we’d love your feedback. Happy to go deeper into how it works.
beslanb•8mo ago
Cloud CI runners work well when you’re getting started with GitHub or GitLab. But as your team grows, CI turns into an operational burden. Costs rise, runners need tuning, and self-hosting starts to feel inevitable.
The real problem with CI today isn’t performance — it’s billing. You’re charged for the allocated instance resources, even if your job is mostly idle. We changed that.
RunMyJob uses a load-based billing model — you’re charged only for the CPU and memory your job actually consumes, measured every second in real time. - High-performance VMs by default (12 vCPU / 32 GB RAM free) - Business tier: 48 vCPU / 96 GB RAM
We don’t resell AWS or Hetzner. We run our own bare-metal infrastructure in Tier III data centers.
If you’re using GitHub Actions or GitLab CI and tired of managing runners or paying for overhead, we’d love your feedback. Happy to go deeper into how it works.