Depot

mark your calendars, something big is coming tuesday

Who’s got fast builds and a merch store? We do. If you've been waiting for a reason to rep Depot, this is it → depot.dev/merch Hooking you up on your first order: 50% off: ALL-ORDPCT50-LAUNCH-03-26 free shipping: ALL-FREESHIP-LAUNCH-03-26

every time i wait for CI to finish on github runners, i think about how grateful i am to @depotdev's team for providing runners for building @heliumbrowser releases it would've been impossible to keep up with github's runners due to how resource-hungry chromium builds are

@uwukko @heliumbrowser Just glad we can help make your day a bit brighter and a bit speedier. 😍

Dev Marketing & technical writing days before a launch

Check out how @astral_sh made CI runs up to 4.7x faster with Depot. depot.dev/customers/astr… @charliermarsh

@charliermarsh Huge congrats from the team here at Depot.

We've entered into an agreement to join OpenAI as part of the Codex team. I'm incredibly proud of the work we've done so far, incredibly grateful to everyone that's supported us, and incredibly excited to keep building tools that make programming feel different.

You may not like it, but this is what peak dev marketing looks like.

Just your friendly weekly reminder that we saved developers 249,790 hours last week.

Your agent writes code in seconds. Then it waits for CI. That's the bottleneck now.

Some badass engineering team absolutely crushing it.

CI was designed for a world where you write code, push, open a PR, and wait. That world is gone. Now you're commanding a fleet of agents generating code across multiple branches at a pace that would have been unimaginable three years ago. And all of it has to flow through CI.

One week from today, CI as you know it... changes forever.

@0xblacklight Happy to have you! You can get in early for Depot CI here too if you’re interested. docs.google.com/forms/d/e/1FAI…

had a github actions workflow to ship a build hang every time I tried to run it for no reason ran it on @depotdev and it passed the first try

@posthog @PlanetScale luma.com/al8bui4v?tk=dt…

We are throwing a party with @PostHog & @PlanetScale @ KubeCon Amsterdam! If you want to join us for tacos, sliders, an open bar, and great company check out the link in 🧵. When? Wednesday, March 25th | 6:30pm-9:30pm Where? The Harbour Club | Amsterdam, Zuid

The real value isn't one optimization — it's having a reusable tool. Now whenever we change standby pool logic, we quantify the tradeoff instead of guessing. Build a simulator. Calibrate it. Share it with your team. It's worth the investment. Full post: depot.dev/blog/how-simul…

We reused the same framework for Depot CI job scheduling. Surprising finding: the best way to assign jobs to VMs was "pick the first host with enough capacity" — not "pick the most-loaded host to run hot." Counterintuitive, but the signal was clear.

We had a standby pool algorithm with 12+ tunable parameters and no safe way to test changes without risking customer latency. So we built a simulator, ran hyperparameter optimization on it, and found a config that was both faster AND cheaper. Thread on how we did it 🧵