Advertisement · 728 × 90

Posts by Depot

Post image

Depot CI made this starter pack extinct.

2 days ago 1 0 0 0

CI math pt 4: The Agent Bottleneck

Your agent writes a 3-line fix. It needs CI to validate it.

GitHub Actions: Push, queue, full 15-minute pipeline. Your agent is now blocked.

Depot CI: Run that one job against uncommitted changes. No push, no queue.

Same fix, no bottleneck

2 days ago 0 0 0 0

251,420. That is the number of hours we saved developers last week.

That is all.

3 days ago 0 0 0 0
Preview
What we need from CI for agentic engineering Agents can write and push code in seconds, but CI still takes minutes to give them feedback. That mismatch is the biggest bottleneck in agentic engineering today, and it's why CI needed to be rebuilt…

Agents write code in seconds. CI takes minutes to tell them if it works.

The agent isn't context switching. It's blocked.

depot.dev/blog/ci-for-...

3 days ago 0 0 0 0

👉 depot.dev/blog/the-end...

4 days ago 0 0 0 0
Post image

The old CI debugging loop vs Depot CI.

👇

4 days ago 0 0 1 0
Video

Bossman is relentless about two things... speed and DX. So, when one of our engineers suggested 'depot ci migrate secrets-and-vars' it was an absolute no brainer.

One command imports all your GitHub Actions secrets and variables into Depot CI. No copy-pasting.

4 days ago 0 0 0 0

CI Math Part 3: The Minute Tax

Your job runs 61 seconds.

GitHub Actions: Rounds up. Bills 2 minutes. $0.016.
Depot CI: Bills 61 seconds. $0.0061.

Same job. 2.6x the cost. Just from rounding.

6 days ago 0 0 0 0
Advertisement
Post image

Slow CI is no longer inevitable.

6 days ago 0 0 0 0

depot.dev/blog/the-end...

1 week ago 0 0 0 0

Edit YAML. Commit. Push. Wait. Squint at logs. Guess. Repeat.

This is now a thing of the past. 🧵

1 week ago 0 0 1 0

It was a beautifully, busy week launching Depot CI, but don't for a second think that I forgot about our weekly post!

This past week, we saved developers 258,790 hours.

1 week ago 0 0 0 0

That no workflow shall be rewritten merely to change the platform that runs it.

We have been patient. We have waited for cold starts. We have scrolled through logs. We have paid the tax.

We will pay it no longer.

1 week ago 0 0 0 0

That no developer shall push to GitHub merely to test their CI.

That no dependency shall be installed from scratch when it was installed ten minutes ago.

That no failure shall be debugged by reading a log file when a live shell exists. 👇

1 week ago 0 0 1 0
Post image

We, the Developers, refuse to pay the tax on speed.

We hold these truths to be self-evident:

That no job shall be billed by the minute when it runs for three seconds.

That no workflow shall run in sequence when its steps are independent. 👇

1 week ago 0 0 1 0
Post image

Reading log files to debug CI is a tax on speed.

'depot ci ssh' drops you into the sandbox. Same environment. Same state. Live.

Debug your CI the same way you debug everything else — interactively.

1 week ago 0 0 0 0
Advertisement

CI Math Part 2: Parallel Steps

Lint: 30s. Typecheck: 30s. Tests: 30s.

GitHub Actions: 30 + 30 + 30 = 90s. Runs each step one at a time.
Depot CI: 30s. Runs all three at once.

Same steps. Same job. One takes 3x longer.

1 week ago 0 0 0 0

You shouldn't have to push to GitHub to test your CI.

'depot ci run' runs your workflow against your local working tree. Uncommitted changes included. No push required.

Test your CI the same way you test your code — before you commit.

1 week ago 2 0 0 1

CI Math:

GitHub Actions: 45s startup = 1 minute billed
Depot CI: 2-3s startup = 3 seconds billed

Same job. One costs 20x more before it runs a single line of code.

1 week ago 1 0 2 0
Post image

We built Depot CI with per-second billing because anything else is a tax on speed.

1 week ago 0 0 0 0
Post image

Absolutely loving the energy at KubeCon!

1 week ago 0 0 0 0

depot.dev/docs/ci/quickstart

1 week ago 0 0 0 0
Video

"How hard is it to migrate to Depot CI?"

One command: depot ci migrate

It discovers your workflows in .github/, copies them to .depot/, detects your secrets, and configures them. Commit, push, and merge — your workflows are running on Depot CI.

quickstart in 🧵

1 week ago 0 0 1 0
Post image

Depot CI in a nutshell:

1 week ago 0 0 0 0
Preview
Now available: Depot CI We're excited to announce that Depot CI, our own programmable CI engine, is now generally available to everyone who wants to accelerate their CI in this new era of software engineering.

Migration is one command: depot ci migrate.

Your existing workflows, marketplace actions, and reusable workflows all work without modification.

depot.dev/blog/now-available-depot-ci
depot.dev/products/ci

1 week ago 0 0 0 0
Advertisement

Run CI against uncommitted changes without pushing. Target specific jobs. SSH into running jobs. Grab logs from the CLI. Per-second billing, no minimums.

Same interface for engineers and agents.

1 week ago 0 0 1 0

Push code and you're in a running job in three seconds.

Prewarmed sandbox.

Dependencies there.

Custom image loaded.

Every layer of the system is ours to optimize.

1 week ago 0 0 1 0

That 70% is the pain we've all felt. And with agents writing code at 10x velocity, CI is the bottleneck in a way it never was before.

That's Depot CI. A new orchestrator. A new compute layer. All of it.

1 week ago 0 0 1 0

We built our own CI engine. Here's why.

For 3 years we've been making builds faster. Docker builds 40x faster. GitHub Actions 3x faster. But we could only optimize 30% of the system. The other 70% was someone else's code.

1 week ago 0 0 1 0
Post image

We are VERY excited to announce the launch of Depot CI. 🚀

Check out the full launch post here: depot.dev/blog/now-ava...

1 week ago 1 0 0 0