Celesto vs Cirun
Celesto provides low-cost managed Linux runners from a single workspace balance. Cirun orchestrates runners in your own cloud, trading more setup for control over machines, images, and network placement.
Install Celesto CIChecked November 1, 2026. Sources and assumptions
Celesto removes the cloud-account setup and separate compute bill
Celesto Standard costs $0.0005/minute for 2 vCPU and 4 GB. Cirun’s GitHub Marketplace lists its Startup plan at $29/month, while its own cloud compute remains a separate bill. Its public home page does not publish a complete private-repository tariff; confirm the plan and repository limits before buying. Open-source projects can use the free service plan but still supply cloud resources.
Cirun Marketplace lists Startup at $29/month; cloud compute is billed separately. Open-source service plan is free. CPU count and memory alone do not establish equal hardware performance, network speed, or completed-job cost.
Managed Linux runners without cloud credentials or a second compute bill.
| Feature | Celesto | Cirun |
|---|---|---|
| Setup and flexibility | ||
| Cloud account | No customer cloud account required(Celesto has the edge) | Your cloud account and credentials |
| Private-repo pricing | Runtime consumes workspace credit; no monthly runner plan(Celesto has the edge) | Marketplace Startup $29/month, plus cloud costs; confirm current limits |
| Open-source plan | $5 one-time trial credit | Free service plan; infrastructure costs remain(Cirun has the edge) |
| Infrastructure choice | Managed Linux x64 runners | AWS, GCP, Azure, DigitalOcean, Oracle Cloud, and OpenStack(Cirun has the edge) |
| Custom hardware and images | Standard Ubuntu 24.04 image, up to 8 vCPU / 32 GB | Custom images, ARM, GPU and spot configurations(Cirun has the edge) |
| Results | GitHub Actions checks and logs | GitHub Actions checks and logs |
Setup and flexibility
- Cloud account
- CelestoNo customer cloud account required Has the edge
- CirunYour cloud account and credentials
- Private-repo pricing
- CelestoRuntime consumes workspace credit; no monthly runner plan Has the edge
- CirunMarketplace Startup $29/month, plus cloud costs; confirm current limits
- Open-source plan
- Celesto$5 one-time trial credit
- CirunFree service plan; infrastructure costs remain Has the edge
- Infrastructure choice
- CelestoManaged Linux x64 runners
- CirunAWS, GCP, Azure, DigitalOcean, Oracle Cloud, and OpenStack Has the edge
- Custom hardware and images
- CelestoStandard Ubuntu 24.04 image, up to 8 vCPU / 32 GB
- CirunCustom images, ARM, GPU and spot configurations Has the edge
- Results
- CelestoGitHub Actions checks and logs
- CirunGitHub Actions checks and logs
Choose Celesto when
- You want to run Linux CI without managing cloud credentials
- You prefer a low compute rate with no monthly runner plan
- You want compatible GitHub Actions workflows and dependency caches
Choose Cirun when
- Builds need your cloud’s private resources
- You need GPUs, ARM, custom images, or multiple cloud providers
- You already operate infrastructure and can manage cloud costs
Keep GitHub Actions. Move compatible Linux jobs.
Install Celesto’s GitHub App, link a workspace, and fund a paid runner size. This example selects Standard, 2 vCPU and 4 GB, at $0.0005/minute. Port provider-specific caches, custom images, or pipeline syntax before migrating. The Micro-only trial starts with $5 shared credit, expires after 30 days, and allows one retained sandbox at a time.
1jobs:
2 test:
3 runs-on: [self-hosted, celesto-standard]
4 steps:
5 - uses: actions/checkout@v4
6 - run: npm ci && npm testCelesto bills computer runtime including preparation and cleanup. Linux x64 only; a two-hour safety limit applies. Concurrency depends on workspace limits, credit, and capacity.
Questions before you switch
Does Cirun’s subscription cover compute?
No. Cirun launches runners on your cloud account and your cloud provider bills for those resources. Include service plan, compute, disks, and any applicable network costs. A free open-source service plan does not make the cloud resources free.
How does migration differ?
Celesto requires its GitHub App, a linked funded workspace, and a supported runs-on label. Cirun’s quickstart additionally requires cloud credentials and a .cirun.yml configuration identifying runner infrastructure. Keep jobs that need custom hardware on the platform that supports it.
How does CI dependency caching work?
Linux x64 jobs include actions/cache and setup-node/setup-python caching without changes to compatible cache steps. Cache storage has no separate charge. Default per-repository limits are 5 GiB on trial and promotional credit and 25 GiB on paid credit; caches expire after 7 idle days. CI runtime consumes workspace credit.
Which Docker workflows are supported?
Docker Engine, Buildx, and Compose are preinstalled. Docker builds, Compose workflows, and GitHub service containers are verified. Validate Docker actions and whole-job containers before migrating. Docker’s explicit --cpus flag failed the documented preflight.
Do Docker layers persist between CI jobs?
No. Each job starts fresh. Use registry caches or portable archives through actions/cache to reuse layers. Direct BuildKit type=gha,version=2 cache export failed the documented preflight.
Sources and assumptions
Pricing and capabilities checked November 1, 2026. No matched performance or network benchmark is claimed here. Cirun is a trademark of its owner; Celesto is not affiliated with it.