Depot

““Given how many PRs we run each day,” Paul said, “even just a few minutes per PR translates to more engineer time.””

“"The most expensive mistake we can make as an engineering-driven company is slowing engineers down. Engineering time is a very valuable resource for us, and knowing that Depot is saving us time is super powerful."”

““We’re swapping money for developer time because it’s always a good investment,””

““In fact,” Paul continued, “once they messaged us in Slack and said, We realized you’re spending too much money – here’s the PR that will make you spend less money with us . Seeing another company with the same principles and the same values in that area – that’s the thing that sold me on Depot.””

““Multiple times, we jumped into Slack and asked, Why is this like that? This might be broken , and we got back a PR into our repo.””

““Docker always seems like black magic to me,””

““We aim to be very responsive to our customers. Our ideal support interaction is to be able to say, It’s building right now, and it’ll be out in 30 minutes .””

“"There's no reason for most people to visit Depot because they can just ignore the fact that the build is working. It always does the thing it's supposed to do. For us, this is really good, because it's a part of the system that we want to just work."”

“"Around here, we say PostHog ships weirdly fast , and you can't say PostHog ships weirdly fast if you're waiting for an hour and 45 minutes."”

“They've been using Depot for three months now, and they just love it. It's been so much faster for them.”

“I have not thought about it since, nor has the team, and we were thinking about it every day for a while.”

“It's refreshing to have a provider like this that just works. Everywhere I've worked there have been squabbles or disagreements or annoyances about CI.”

“You guys have built what we couldn't build without spending a ton of time away from our core business,”

“We decommissioned the runner queue, and it really just worked, and it made our builds faster and less flaky.”

“I just moved everything over to Depot, and that problem completely went away,”

“I'm already seeing run times cut in half or even better on some of our CI jobs, just by moving to runners. And I'm excited about what we can do with Depot to speed things up even more.”

“We always want to give our developers the best tools. That's just our philosophy. I have no interest in giving them anything but the best, I have no interest in wasting their time using subpar tools. Depot hit that sweet spot of being a drop-in replacement for our manual toil, while also giving us an option to evolve in the future.”

“This came to a head when Buildkite was having database problems and asked us to accept a multi-hour downtime window for their service, where we just couldn't do any CI. We're a global company. We have people all over the world who rely on our CI and CD. When they refused to take a meeting with us to talk about it…it just felt very non-collaborative.”

“I'll push code and then... I still have this kind of knee-jerk reaction. I need to go check: how far is it along?”

“We got the best of both worlds. We didn't have to move out of that ecosystem, but we actually get runners that work consistently.”

“We can now rely on the fact that when we push code our Actions will always run. GitHub being down is unrelated. At least we know that the actual Action runners will work.”

“We connected [Depot GitHub Actions runners] and our builds just started running. We no longer had random tasks that never got picked up, or tasks living for hours without being able to kill them.”

“There's been a number of times where we've had mission critical bug fixes get completely blocked. There's nothing worse than fixing a bug quickly and wanting to tell the customer, 'Hey, 2 minutes after you noticed this bug, we fixed it'. But then we wait another 30 minutes just to get builds out.”

“"We observed a 20% decrease in build time just by changing one line,"”

“"I feel like Depot is an embedded team at Jane,"”