Migrating from Ubicloud to Latchkey: What Changes
Both Ubicloud and Latchkey attach managed GitHub Actions runners with a one-line runs-on change, so switching between them is low-friction. The practical difference is what happens when a job fails for a transient reason.
According to Ubicloud's docs, you adopt its runners by changing the ubuntu-latest label to a Ubicloud label such as ubicloud-standard-2. Latchkey works the same way: a one-line runs-on swap, your YAML and actions unchanged. So a migration between the two is mostly a label change. Where they differ is reliability: Latchkey adds self-healing CI, where transient and mechanical failures (out-of-memory kills, disk-full errors, registry timeouts) are detected, fixed, and retried automatically instead of leaving you to re-run a red build. Here is what actually changes when you move.
Ubicloud vs Latchkey at a glance
| Capability | Ubicloud | Latchkey |
|---|---|---|
| Drop-in managed runners | Yes (label swap) | Yes (label swap) |
| Cheaper than GitHub-hosted | Yes (per Ubicloud pricing) | Yes (up to 70% lower per minute) |
| Open source | Yes | No |
| x64 and arm64 runners | Yes (per Ubicloud docs) | Yes |
| Self-healing CI (auto-retry transient failures) | No | Yes |
| AI build optimization | No | Yes |
| Best known for | Open source + low sticker price | Self-healing + low-cost runners |
What stays the same
- The switch is a one-line
runs-onchange on both platforms, so your workflows, actions, and YAML are untouched. - Both run standard GitHub Actions runners, so
actions/checkout,actions/cache, and the rest of your steps behave the same. - Both price under GitHub-hosted runners, so you are comparing two cheaper options rather than trading cost for savings.
What Ubicloud is genuinely good at
Ubicloud is an open-source cloud (its runner stack is part of the open-source ubicloud/ubicloud project on GitHub), and it competes aggressively on price. According to Ubicloud's pricing page, it bills per minute and headlines significant savings versus GitHub Actions, plus a small monthly credit. If open-source infrastructure and the lowest sticker price are your top priorities, that is a real and honest strength. Verify current Ubicloud pricing on their site, since vendor pricing changes.
What Latchkey adds
Latchkey is built around self-healing CI. On its managed runners, transient and mechanical failures are detected and retried automatically, so you stop paying for re-runs and stop babysitting red builds. It also applies AI build optimization to speed up pipelines, and prices up to 70% lower per minute than GitHub Actions. The trade-off to be honest about: Latchkey is not open source. If open source is a hard requirement, Ubicloud fits that need in a way Latchkey does not.
How to run the migration
- Pick one representative workflow to pilot rather than switching everything at once.
- Change its
runs-onlabel from your Ubicloud label back toubuntu-latest, then to your Latchkey label. - Run it a few times, including on a branch that has been flaky, so you can see self-healing recover a transient failure.
- Compare the bill and the green-build rate against Ubicloud before rolling out more workflows.
The verdict
If open source and the lowest sticker price are your priority, Ubicloud is a solid choice and worth keeping. If your real pain is flaky re-runs and you want runners that recover from transient failures on their own, Latchkey is the stronger fit. Because both are a one-line swap, you can pilot Latchkey on a single workflow and compare against your real Ubicloud builds before committing.
Frequently asked questions
Is migrating from Ubicloud to Latchkey difficult?
runs-on label change, so switching is mostly editing that label. Your workflow YAML and actions stay the same.