Depot CI now caches the source code for GitHub Actions in Depot Code, reducing repeat downloads from GitHub without requiring any workflow changes.

We built a production-shaped load test to find control-plane limits before moving more GitHub Actions traffic to Depot Metal. Each run made our scaling changes measurable.

Depot CI runs GitHub Actions workflows without GitHub’s control plane, keeping CI online during outages and making workflows portable to new forges like Origin.

Taking the Sandbox TTI benchmarks one step further for fun.

Launching today in early beta, Origin code hosting features a Depot app to run your existing GitHub Actions workflows on Depot CI for better performance and reliability without GitHub.

Our microVMs launch in under a second, and assembling their block devices in parallel put LVM's roughly 100ms volume group-wide lock directly in the critical path. We kept the kernel's device-mapper, wrote our own control plane and gave up crash safety our ephemeral workloads never needed, making allocation roughly 100x faster.

Agents can investigate, plan, and implement faster than I can, but reading a final diff is not the same as understanding why the system works the way it does. I own how the system behaves in production, so I want to keep building my intuition about it.

Most of a large container's startup goes to pulling and decompressing files it never reads to boot. SOCI makes the image seekable so the runtime loads only the bytes it needs, and Depot writes that index during the build, so the image can lazy-load the instant it's pushed.

GitHub isn't just falling short on performance and reliability. The whole collaboration paradigm is the wrong shape for how we build software now.

Report JUnit from your Depot CI or Depot GitHub Actions jobs to see failures in context. A single command runs your suite and uploads the report. Split suites by historical timing and they'll automatically rebalance over time.