Depot × PlanetScale
Depot x PlanetScale, CI runtimes cut in half after dropping Buildkite
CI runs in half the time vs. self-hosted runners
Constant infrastructure toil to CI that just works
Members read free
Unlock the full breakdown
Enter your email to open every case study in the library: the full screenshot, why it works, and the one thing worth stealing. One email unlocks all of them.
Free. No spam. Unsubscribe anytime.
You're in — enjoy the library.
Why it works
The case study earns its efficiency framing by grounding every claim in a specific before-and-after number, from 10-12 minutes down to 4 minutes on a dev-tooling repo to 200-400 jobs causing 20-30 minute queue stacks. The competitive switch is explicit and named, and the breaking-point anecdote about Buildkite refusing a meeting gives the trigger scene real texture. The qualitative change is handled well too: the line about not thinking about the Vitess suite anymore after years of daily attention is more persuasive than a percentage.
Steal this
Use a named breaking-point incident as the trigger scene. The Buildkite downtime refusal is a single, concrete moment that makes the switch feel inevitable rather than arbitrary, and it is quoted directly from the CTO.
Click to enlarge ↗ This is editorial commentary and curation. The case study, screenshot, and all metrics are Depot's published work; we link to the source and lead with our analysis.