CI/CD runners
Faster builds.
Flat costs.
Dedicated runners.
Rightsize runs your CI/CD on dedicated bare-metal runners, fully managed. Builds finish sooner on fast CPUs with warm local caches, and you pay a flat monthly price instead of paying by the minute.
Works with
- GitHub Actions
- GitLab CI
- Buildkite
- Jenkins
Faster builds
High-clock CPUs, local NVMe and warm caches on every run.
Flat monthly cost
No per-minute meter. Build as often as you like.
Single-tenant
Your code never shares a machine with anyone else.
Any CI system
GitHub Actions, GitLab CI, Buildkite and Jenkins.
The economics
Per-minute CI gets expensive as you grow. Dedicated runners don't.
- 01Per-minute pricing charges for every build, every retry and every flaky test.
- 02Caches, Docker layers and static IPs are often sold as add-ons.
- 03A dedicated runner costs the same each month, however much it builds.
What you get
Everything fast CI needs. Nothing you have to run.
Fast, dedicated hardware
High-clock CPUs and local NVMe, used only by your jobs. No noisy neighbours slowing builds down.
Warm caches, included
Dependency and Docker layer caches stay on the runner's local disk between builds. No per-GB cache fees.
No waiting in the queue
Runner capacity is sized to your peak concurrency, and we adjust it as your team grows.
Works with your CI
GitHub Actions, GitLab CI, Buildkite and Jenkins. Switch with a one-line runner label change.
Secure by design
Single-tenant runners and least-privilege access. Static IPs for allowlisting, included.
Fully managed
We maintain images, patch the OS, monitor runners and tune your pipelines. Your team just pushes code.
How it works
Benchmark first. Switch when the numbers say so.
- 01
We benchmark your pipelines.
We run your real workflows on dedicated hardware and measure build time and cost against today.
You getA side-by-side report of build times and monthly cost
- 02
We set up your runners.
We provision dedicated runners, build your images and warm the caches, in the region you choose.
You getRunners registered to your CI, ready to take jobs
- 03
You change one line.
Point your jobs at the new runner label. We monitor, patch and keep tuning from there.
You getFaster builds at a flat monthly cost
Compare
Three ways to run CI. One flat, fast and managed.
- Pricing
- RightsizeYes:Flat monthly price
- Per-minute hostedNo:Billed per minute, per job
- DIY self-hostedPartly:Servers plus engineering time
- Cost as you build more
- RightsizeYes:Stays flat
- Per-minute hostedNo:Rises with every minute
- DIY self-hostedPartly:Flat, but upkeep grows
- Hardware
- RightsizeYes:Dedicated, single-tenant
- Per-minute hostedPartly:Shared, multi-tenant
- DIY self-hostedYes:Yours to choose and run
- Build caches
- RightsizeYes:Warm on local NVMe, included
- Per-minute hostedPartly:Remote, or a paid add-on
- DIY self-hostedPartly:You build and maintain it
- CI systems
- RightsizeYes:GitHub Actions, GitLab CI, Buildkite, Jenkins
- Per-minute hostedPartly:Often GitHub Actions only
- DIY self-hostedYes:Any, if you set it up
- Static IPs
- RightsizeYes:Included
- Per-minute hostedPartly:Often a paid add-on
- DIY self-hostedYes:Yes
- Maintenance
- RightsizeYes:Fully managed by Rightsize
- Per-minute hostedYes:Managed by the provider
- DIY self-hostedNo:Your team patches and fixes
- Sudden bursts
- RightsizePartly:Sized to your peak; overflow on request
- Per-minute hostedYes:Elastic on demand
- DIY self-hostedNo:Limited to your servers
Fit
Built for teams that build all day. Honest about when it isn't.
Yes:Great fit for dedicated runners
- Yes:Teams running CI throughout the working day
- Yes:Monorepos and heavy Docker builds
- Yes:Large test suites that run on every pull request
- Yes:Teams on GitLab CI, Buildkite or Jenkins, not just GitHub
- Yes:Regulated teams that can't build on shared machines
No:Probably stay per-minute
- No:A handful of builds a week: per-minute is cheaper
- No:Rare spikes far above your normal load
- No:Short-lived projects you'll shut down within weeks
FAQ
Common questions. Straight answers.
Do we need to rewrite our pipelines?
No. You change the runner label in your workflow (runs-on in GitHub Actions, tags in GitLab CI). Steps, scripts and secrets stay as they are.
How much faster will our builds be?
It depends on your pipeline. Builds usually gain the most from faster CPUs and warm caches. We benchmark your real workflows first, so you see the difference before you commit.
How does pricing work?
A flat monthly price per dedicated runner, sized from your benchmark. Caches and static IPs are included. There's no per-minute billing.
What happens when we need more capacity?
We size runners to your peak concurrency and add capacity as you grow. For rare spikes, jobs can overflow to your existing hosted runners.
Is our code safe?
Runners are single-tenant: your jobs never share a machine with another customer. We follow least-privilege access and keep runners patched.
Which operating systems do you support?
Linux runners on x86 and ARM. Talk to us about Windows and macOS.
Get in touch
Get a CI benchmark.
Tell us which CI you use and how long your pipelines take. We'll benchmark them on dedicated hardware and show you the difference in speed and cost.
What happens next
- 01We reply by email and agree which pipelines to benchmark.
- 02We run them on dedicated runners and measure time and cost.
- 03You get a side-by-side report, then decide.