Sign in

Depot

@depot.dev
90 followers 11 following 814 posts

Software delivery built for machine scale.

PostsRepliesMedia
Depot @depot.dev · 29/09/2026
Anthropic, Linear, and Lindy all reached the same conclusion this month: CI is now the bottleneck. Kyle on why validation has to move to where agents write the code. depot.dev/blog/ci-is-c...
depot.dev
CI is changing
AI agents can generate code faster than traditional CI can validate it. We need to change how we think about CI to keep delivery fast and maintain trust.
001
Depot @depot.dev · 28/09/2026
asking aws for ec2 capacity it doesn't have still burns rate limit tokens. rob used a multi-armed bandit with thompson sampling to make better guesses and keep jobs moving. new on working theory: newsletter.depot.dev/p/the-multi-...
newsletter.depot.dev
The multi-armed bandit approach to securing EC2 instances
When boxes are MIA, the multi-armed bandit saves the day.
000
Depot @depot.dev · 24/09/2026
depot engineers have opinions. now they have a newsletter. working theory covers topics like ai engineering, infrastructure, security, and the challenges of delivering software today. depot.dev/newsletter
depot.dev
Working Theory | The Depot newsletter
Perspectives from engineers on software engineering, AI, infrastructure, security, and the problems we’re working through.
000
Depot @depot.dev · 22/09/2026
How the Depot Metal autoscaler grew from a pressure loop that fit on a napkin into a system that pairs compute with storage hosts across AZs, in about 8,000 lines. depot.dev/blog/autosca...
depot.dev
The evolution of the Depot Metal autoscaler
Depot Metal's autoscaler grew from a simple pressure loop into a topology-aware system for compute and storage. Next, it must predict demand and converge on desired capacity.
010
Depot @depot.dev · 17/09/2026
before moving more github actions traffic to depot metal, iris load tested the control plane by replaying synthetic github webhooks into preview. depot.dev/blog/how-we-...
depot.dev
How we load tested Depot Metal before scaling up
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.
000
Depot @depot.dev · 16/09/2026
posted up at the Inference office all day Oct 6 for SF Tech Week. co-work + pizza in the afternoon, drinks and Depot Donuts once it gets dark. come by. luma.com/i3y4poqn
luma.com
SF Tech Week: 💻🍕🍩🍸🥃 DevTools Drink Up // Depot x Inference · Luma
Join Depot and Inference for a casual SF Tech Week co-working day that turns into a happy hour with demos and networking at the Inference office by the…
000
Depot @depot.dev · 11/09/2026
multi-platform docker builds are slow mostly because of qemu emulation. depot runs native amd64 and arm64 builders instead. wito shows a build drop from ~30 minutes to 16 seconds. youtu.be/UEACT6c3sm4?...
youtu.be
How Depot cuts Docker builds from 30 minutes to 16 seconds
YouTube video by Depot
010
Depot @depot.dev · 10/09/2026
the github control plane goes down and your jobs never dispatch, so all your ci redundancy is moot. luke walked through how depot ci runs github actions workflows without it, keeping runs alive through outages. depot.dev/blog/github-...
depot.dev
GitHub Actions without GitHub
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.
000
Depot @depot.dev · 09/09/2026
we had some fun and built a benchmark that computes the 20th fibonacci number by running each of its 18 steps in its own ci runner. each step takes about a second, so what you're really watching is the runner start up. depot.dev/blog/the-fib...
depot.dev
Introducing the Fibonacci Benchmark™ for CI runners
Taking the Sandbox TTI benchmarks one step further for fun.
000
Depot @depot.dev · 04/09/2026
the whole reason we reimplemented lvm: its volume-group lock is held ~100ms per op. we launch microvms up to 200 times a second in parallel, and that single lock, not the data path, is what breaks the latency target. depot.dev/blog/why-i-r...
depot.dev
Why I reimplemented LVM (with worse guarantees)
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, ...
000
Depot @depot.dev · 03/09/2026
delegation does not transfer ownership. an agent can write the change, but you still own how the system behaves in production. so iris keeps the parts that build context: planning decisions, close review, a limit on parallel work. depot.dev/blog/delegat...
depot.dev
How I delegate the work, not my judgment
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 productio...
000
Depot @depot.dev · 01/09/2026
end of summer glow up 💅 new paint, same machine scale.
000
Depot @depot.dev · 31/08/2026
a container can build in seconds and still crawl on deploy, because every node pulls and decompresses gigabytes it never reads to boot. soci fetches only the bytes needed to start. the index gets written at build time. depot.dev/blog/why-soc...
depot.dev
Why SOCI belongs in the build
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 in...
000
Depot @depot.dev · 28/08/2026
the branch-PR-review-merge workflow is muscle memory for every engineer. now that agents write consistently good code, it's the primary bottleneck. kyle argues software delivery should be built like infrastructure, not a better pull request. depot.dev/blog/github-...
depot.dev
GitHub is the wrong shape for this new world
GitHub isn't just falling short on performance and reliability. The whole collaboration paradigm is the wrong shape for how we build software now.
000
Depot @depot.dev · 26/08/2026
we built a fibonacci benchmark that runs each step in its own ci runner. 18 workflows, each doing about a second of math, so the sequential test mostly comes down to cold-start time. here's how it works. depot.dev/blog/the-fib...
depot.dev
Introducing the Fibonacci Benchmark™
Taking the Sandbox TTI benchmarks one step further for fun.
000
Depot @depot.dev · 25/08/2026
when we rebuilt depot registry's garbage collector, tlc checked 14m+ states in 21 minutes and verified in the model that a committed manifest never loses its blob. wito walks through the whole gc model and how to run one yourself. depot.dev/blog/tla-ver...
depot.dev
Improving system safety with Temporal Logic of Actions (TLA+)
Formal verification never seemed worth it: writing a faithful TLA+ spec took too long. But now agents can write the spec from your code. We tried it on the rebuilt Depot Registry garbage collector, an...
000
Depot @depot.dev · 19/08/2026
our review setup: a csv export, a python script, an ai filter. we still fell behind. the fix was in @posthog.com's sidebar: ai engineering. reviews now take 30 min a week. depot.dev/blog/using-p...
depot.dev
How we use PostHog to keep our AI assistant on track
Keeping our AI assistant working well is a human responsibility at Depot. PostHog's AI engineering features turned our never-ending reviews into 30 minutes a week.
000
Depot @depot.dev · 18/08/2026
tracking 3 projects through linear updates worked fine. at 15, the same format broke. watts on why the fix wasn't a better template, it was naming the principle underneath and changing the shape to fit. depot.dev/blog/why-you...
depot.dev
Why your team processes suck
A team process without a principle underneath it is a real problem. Here's why the "why" is worth protecting as you scale.
001
Depot @depot.dev · 17/08/2026
origin enters early beta today, and depot ci is there from day one. bring your existing github actions workflows and get faster, more reliable ci without github. depot.dev/blog/depot-i...
depot.dev
Depot CI is now available in Origin
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.
000
Depot @depot.dev · 13/08/2026
we reimplemented lvm for our microvm hypervisors, with worse guarantees on purpose. its ~100ms volume-group lock was fine weekly but brutal at 200 launches/sec. keeping device-mapper, new control plane, ~100x faster allocation. depot.dev/blog/why-i-r...
depot.dev
Why I reimplemented LVM (with worse guarantees)
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, ...
000
Depot @depot.dev · 12/08/2026
noisy test failures burn hours: people reread the same logs, retry jobs to see if a failure disappears, and slowly stop trusting failures that point at something worth fixing. one approach: give each failure a stable identity you can compare over time. depot.dev/blog/failure...
depot.dev
Failure fingerprints: Comparing test failures over time
To make recurring test failures easier to reason about we needed to include historical context. Here's how we derive a stable identity for each test and a fingerprint for each failure, so you can tell...
000
Depot @depot.dev · 11/08/2026
an agent can hand you a fix that works and passes its tests but could still be the wrong call for your system. you only catch that if you've kept enough context to challenge it. iris on where she stays involved to keep that context. depot.dev/blog/delegat...
depot.dev
How I delegate the work, not my judgment
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 productio...
000
Depot @depot.dev · 10/08/2026
when the agent's code breaks at 2am, you're the one on call, not the agent. here's a practical ai-assisted workflow for staying responsible for what ships: linter guardrails, reference tests, and reviewable prs. depot.dev/blog/staying...
depot.dev
Staying in control of your codebase in the AI era
AI can produce code faster than you can review it, but you're still the one on call when it breaks. You need an AI-assisted workflow you trust: linter guardrails, reference tests the agent can copy, t...
020
Depot @depot.dev · 06/08/2026
cloud-native worked because we built on a few composable primitives: compute, storage, networking. kyle's take: software delivery needs the same shift. he names the six infrastructure primitives to build on. depot.dev/blog/github-...
depot.dev
GitHub is the wrong shape for this new world
GitHub isn't just falling short on performance and reliability. The whole collaboration paradigm is the wrong shape for how we build software now.
010
Depot @depot.dev · 05/08/2026
ci logs are a good starting point, but they're noisy and don't give you data you can filter or join across runs. structured test results let you ask which tests fail most, which are slow, and what's getting worse org-wide. now ga in depot. depot.dev/blog/now-ava...
depot.dev
Now available: Test results in your CI jobs
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 automati...
000
Depot @depot.dev · 04/08/2026
tar is sequential and gzip is stream-oriented, so to read one file in a container layer you unpack everything before it. soci adds metadata that lets the runtime seek directly to the bytes it needs. depot.dev/blog/why-soc...
depot.dev
Why SOCI belongs in the build
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 in...
000
Depot @depot.dev · 03/08/2026
deleting from a content-addressable store is trickier than writing to one. you can't re-check s3 and delete in one step, so we record the version gc inspected and delete only that, staying safe even against a concurrent re-push. depot.dev/blog/tla-ver...
depot.dev
Improving system safety with Temporal Logic of Actions (TLA+)
Formal verification never seemed worth it: writing a faithful TLA+ spec took too long. But now agents can write the spec from your code. We tried it on the rebuilt Depot Registry garbage collector, an...
010
Depot @depot.dev · 31/07/2026
usage events tell you people are using your ai assistant. to see what they're trying to accomplish, you need traces: the user's question, the response, latency, session grouping, and where the conversation started. depot.dev/blog/using-p...
depot.dev
How we use PostHog to keep our AI assistant on track
Keeping our AI assistant working well is a human responsibility at Depot. PostHog's AI engineering features turned our never-ending reviews into 30 minutes a week.
000
Depot @depot.dev · 30/07/2026
test results are now ga in depot ci and github actions. ingest junit xml from your ci to get pass/fail/error/skip counts on every job, plus org-wide analytics for flaky, slow, and recurring failures. depot.dev/changelog/20...
depot.dev
Test results are now generally available | Changelog | Depot
120
Depot @depot.dev · 29/07/2026
kyle wrote up something we've been chewing on: the branch-pr-review-merge workflow was built for humans at human speed. agents blew past that, and github's collaboration model is now the bottleneck. depot.dev/blog/github-...
depot.dev
GitHub is the wrong shape for this new world
GitHub isn't just falling short on performance and reliability. The whole collaboration paradigm is the wrong shape for how we build software now.
000
Depot @depot.dev · 28/07/2026
best test for a process you inherited: ask what breaks if you delete it. "nothing, but people would be annoyed" means it's a ritual with no principle left. watts on keeping the why alive as you scale. depot.dev/blog/why-you...
depot.dev
Why your team processes suck
A team process without a principle underneath it is a real problem. Here's why the "why" is worth protecting as you scale.
010
Depot @depot.dev · 24/07/2026
we cut our slowest ci job from 6m 40s to 2m 36s. maxed vitest parallelism to use spare cpu (3m 54s), then sharded across 2 jobs with depot test splitting, now in beta. depot.dev/docs/ci/how-...
depot.dev
Split Depot CI tests with historical timing data
Split a test suite across matrix jobs with historical JUnit timing data, then run and report every shard.
000
Depot @depot.dev · 23/07/2026
fingerprint a failure too strictly and every run looks like a brand-new bug. too broadly and unrelated failures get lumped together. getting that balance right was the whole challenge, and we wrote up how we approached it. depot.dev/blog/failure...
depot.dev
Failure fingerprints: Comparing test failures over time
To make recurring test failures easier to reason about we needed to include historical context. Here's how we derive a stable identity for each test and a fingerprint for each failure, so you can tell...
000
Depot @depot.dev · 22/07/2026
the trick to getting consistent code out of an agent is constraint. cap cyclomatic complexity, function length, and file length. those guardrails force the agent to break work into small, readable units. depot.dev/blog/staying...
depot.dev
Staying in control of your codebase in the AI era
AI can produce code faster than you can review it, but you're still the one on call when it breaks. You need an AI-assisted workflow you trust: linter guardrails, reference tests the agent can copy, t...
000
Depot @depot.dev · 20/07/2026
tla+ always felt like too many weeks of modeling to win a prioritization fight, so we never budgeted it. now an agent writes the spec from our go, sql, and s3 calls while we make the judgment calls. tlc explored 14.3m states and caught a race we'd have shipped. depot.dev/blog/tla-ver...
depot.dev
Improving system safety with Temporal Logic of Actions (TLA+)
Formal verification never seemed worth it: writing a faithful TLA+ spec took too long. But now agents can write the spec from your code. We tried it on the rebuilt Depot Registry garbage collector, an...
000
Depot @depot.dev · 17/07/2026
Depot is now available in the Stripe Projects developer preview. Run 'stripe projects add depot', pick a plan, and get a Depot API token in your environment, ready for CI, runners, and fast container builds. depot.dev/blog/stripe-...
depot.dev
Depot is now available in Stripe Projects
Depot is joining the Stripe Projects developer preview. Developers and their agents can now set up Depot from the terminal: create or link an organization, pick a plan, and get a token back that unloc...
000
Depot @depot.dev · 16/07/2026
@planetscale.com's Vitess suite could fire 200–400 jobs from one PR. On a fixed runner fleet they queue up 20-30 min deep. A fixed fleet is the ceiling. Elastic capacity removes it, so there's nothing to queue behind. depot.dev/customers/pl...
depot.dev
How PlanetScale scrapped Buildkite and runs CI in half the time with Depot
How PlanetScale scrapped Buildkite and runs CI in half the time with Depot
010
Depot @depot.dev · 15/07/2026
keeping our ai assistant sherlock on track used to be endless manual toil: csv exports, a python script, a spreadsheet. we moved to posthog's ai observability and now weekly reviews take 30 minutes. depot.dev/blog/using-p...
depot.dev
How we use PostHog to keep our AI assistant on track
Keeping our AI assistant working well is a human responsibility at Depot. PostHog's AI engineering features turned our never-ending reviews into 30 minutes a week.
021
Depot @depot.dev · 13/07/2026
the same standup can feel like an interrogation or the most valuable 15 minutes of your day. the difference isn't the format, it's the principle underneath: control vs. connection. watts on protecting the why. depot.dev/blog/why-you...
depot.dev
Why your team processes suck
A team process without a principle underneath it is a real problem. Here's why the "why" is worth protecting as you scale.
000
Depot @depot.dev · 09/07/2026
Depot Code is now in private beta. It's the git host we wanted after three years accelerating everything downstream of source control: a diskless git server that stores content in S3 and scales horizontally. Regular git under the hood. depot.dev/blog/now-ava...
depot.dev
Now available: Depot Code in private beta
Source control has become the bottleneck at the top of the delivery loop. So we built our own: a diskless git server backed by blob storage that scales horizontally, mirrors your GitHub repos, and plu...
100
Depot @depot.dev · 07/07/2026
Depot CI and Sandbox workloads are now running on Depot Metal, our new 4th-gen compute platform. Benchmarks show them running 30% faster, with nothing to migrate. Built on bare-metal EC2 with microVMs and dedicated NVMe storage. depot.dev/blog/announc...
depot.dev
Announcing Depot Metal
Depot Metal is our next-generation compute and storage platform. Depot CI and Sandboxes are now running on it, with benchmarks showing workloads 30% faster and more optimizations on the way. You don't...
000
Depot @depot.dev · 02/07/2026
two test failures can look different and still represent the same failure pattern. the hard part isn't collecting failures. it's knowing when two failures are the same. iris shows how failure fingerprinting cuts noise and keeps the pieces that identify the pattern. depot.dev/blog/failure...
depot.dev
Failure fingerprints: Comparing test failures over time
To make recurring test failures easier to reason about we needed to include historical context. Here's how we derive a stable identity for each test and a fingerprint for each failure, so you can tell...
010
Depot @depot.dev · 01/07/2026
AI can generate code in seconds. That doesn't mean the hard part is solved. Someone still has to understand, review, maintain, and debug that code months later. Engineering guardrails like linting, reference tests, coding standards, and reviewable pull requests help make it easier to maintain.
110
Depot @depot.dev · 30/06/2026
New case study with @planetscale.com. PlanetScale runs CI at massive scale. After moving their CI workloads to Depot, they cut CI time in half on many workloads, eliminated runner management, and stopped thinking about CI. Read the full story: depot.dev/customers/pl...
depot.dev
How PlanetScale scrapped Buildkite and runs CI in half the time with Depot
How PlanetScale scrapped Buildkite and runs CI in half the time with Depot
010
Depot @depot.dev · 16/06/2026
Writing code stopped being the bottleneck. Validating it became one. When an agent ships a feature in 20 minutes, a 20-minute CI pipeline is the constraint. The code is done. The pipeline is what you're waiting on.
100
Depot @depot.dev · 16/06/2026
Your agent ships in seconds. Depot gives it unlimited concurrency, so nothing sits in a queue.
000
Depot @depot.dev · 15/06/2026
When your CI is agent-operable, a failed run is structured data, not a wall of logs. `depot ci diagnose --output json` returns the failed step and the error lines that matter. Your agent reads it, fixes the code, moves on.
000
Depot @depot.dev · 12/06/2026
1/ Paranoia used to be optional. AI-assisted bug hunting ended that. 🧵
220
Depot @depot.dev · 11/06/2026
macOS 26 (Tahoe) is now on Depot GitHub Actions runners. Change one line, `runs-on: depot-macos-26`, and you're on Apple M4 with Xcode 26 and the macOS 26 SDKs preinstalled. Simulators baked in too, no per-run downloads. depot.dev/blog/now-available-macos-26-github-actions
000
Depot @depot.dev · 10/06/2026
Reading CI logs is mostly scrolling past the 2,000 lines that don't matter to find the 4 that do. `depot ci diagnose --run <id>` Hands you the 4.
110