Depot vs Celesto CI: Runner Costs Compared
ملخص
Pixel’s announcement compares Depot and Celesto CI for GitHub Actions, including runner prices, machine sizes, platforms, storage, and included usage. It highlights Celesto’s Linux runtime rate of about $0.000667 per minute versus Depot’s $0.006 at 2 vCPU and 8 GB, helping the community weigh cost against platform features.
DEV Community
Depot vs Celesto CI: what are you paying for?
I build Celesto CI. Depot and Celesto both let you keep GitHub Actions while moving jobs to managed runners. The difference is what you want to buy: Depot offers a broader build platform, larger machines and more operating systems. Celesto offers a much lower Linux runtime rate without a monthly CI subscription. At 2 vCPU and 8 GB RAM, Depot lists $0.006/minute for additional Linux usage. Celesto Memory lists about $0.000667/minute. That is roughly 89% less per running minute, or about nine times the runtime per dollar before allowances. It is not a claim that Celesto finishes builds nine times faster. This comparison covers Depot's GitHub Actions runners, not its separate Depot CI product. Prices and documentation were checked on November 15, 2026. All prices are USD. Comparison Depot GitHub Actions runners Celesto CI Linux x64, 2 vCPU / 8 GB $0.006/min additional usage $0.00066667/min, celesto-memory Linux x64, 4 vCPU / 16 GB $0.012/min additional usage $0.00133333/min, celesto-large Linux x64, 8 vCPU / 32 GB $0.024/min additional usage $0.00266667/min, celesto-xl Monthly plan Developer $20; Startup $200; Business custom No recurring CI platform subscription; runtime uses workspace credit Included usage and trial Developer includes 2,000 base runner minutes/month; Startup 20,000. Seven-day trial advertised One-time $5 Micro trial, up to 20,000 minutes, expires after 30 days; not a recurring allowance CPU range 2 to 64 vCPU on Linux 1 to 8 vCPU Platforms Linux x64 and ARM, Windows, macOS Ubuntu 24.04 Linux x64 Local disk at 2 vCPU / 8 GB 100 GB, with a 2 GB memory-backed disk accelerator 40 GB Dependency cache 25 GB shared cache/registry storage on Developer; 250 GB on Startup; $0.20/GB-month additional storage Default 25 GiB per paid repository and 100 GiB per paid workspace, no separate cache storage charge Docker Local builds plus a separately priced remote container-build product Docker Engine, Buildx, Compose, service containers and type=gha layer caching Repository ownership GitHub organization required for this runner product Personal accounts and organizations Migration Connect Depot, then change runs-on Install the GitHub App, link a funded workspace, then change runs-on Sources: Depot runner specifications, Depot pricing, Depot runner overview, Celesto setup and sizes, Celesto caching and Docker support. The CPU and RAM match in the price rows. The machines do not: disk capacity, physical processors, storage and software images differ. Speed: compare the workflow, not two marketing numbers Depot advertises runners up to 3x faster and caching up to 10x faster than GitHub-hosted runners. Those are Depot's claims against GitHub, not measurements against Celesto. Celesto publishes open workflows, results and source runs. Its November 14 provider snapshot, including a November 15 Docker rerun, does not contain Depot. It cannot settle which of these two providers is faster. There is still a useful buying question: how much time must a higher-priced runner save to justify its rate? At the matched 2-vCPU / 8-GB list rates, Depot would need roughly one-ninth of Celesto's billable runtime to reach the same compute charge, before plan fees and allowances. A 2x speedup alone would not offset a roughly 9x rate. That is arithmetic, not a benchmark prediction. For an actual test, run the same commit several times on both. Keep CPU, RAM and architecture aligned. Separate cold builds from warm-cache runs. Measure queue wait, preparation, dependency restoration, build, tests and cleanup. If a Depot remote builder does some of the work, record its bill too. Cost: include the plan, then subtract its minutes The per-minute gap matters most when CI runs all day. Coding agents can increase that volume: more pushes mean more chances to run the same checks. Here is a Linux-only illustration at 2 vCPU / 8 GB. It assumes equal billable runtime and excludes tax, storage overages, remote builders, discounts, trial credit and billing roundin...

Powered by Readybot.io