Migrate from WarpBuild and the label is the easy part: every size maps onto a size somewhere else at a comparable rate. What does not map is the part of WarpBuild that is not a runner, which is a metered cache and a snapshot restore priced per job, and those are the lines that decide whether the move saves money or just moves it.
The four metered lines a WarpBuild pipeline can carry, and which of them have an equivalent elsewhere. Prices read from warpbuild.com/pricing on 2026-09-21.
WarpBuild sells two different products under one name, and which one you are on changes the whole migration. The managed runners are an ordinary metered fleet in its cloud. The bring-your-own-cloud mode is a control plane over machines in your own AWS, GCP or Azure account at a flat $0.002 a minute, and leaving that is a decision about your cloud account rather than about a rate.
Either way, three things come off the bill with their features attached: cache storage, cache operations and snapshots.…