More Scaling DevTools episodes

AI broke traditional infra - with Kyle from Depot.dev @ AIE Europe thumbnail

AI broke traditional infra - with Kyle from Depot.dev @ AIE Europe

Published 18 May 2026

Duration: 00:10:51

Depot CI emerges as a next-gen CI/CD engine targeting AI-driven workflows by providing infrastructure control, multi-language SDKs, and sandboxed execution, addressing scalability gaps in traditional tools strained by AI-generated code, while highlighting Europe's evolving tech landscape in AI research.

Episode Description

In this episode, Kyle Galbraith from Depot shares the story behind building Depot CI and why traditional infrastructure is "crumbling" under the weigh...

Overview

Depot CI is a newly developed, custom CI/CD engine designed to support multiple programming languages, utilizing a TypeScript or Python SDK and built on Depots proprietary sandbox technology. It aims to replace traditional tools like GitHub Actions by offering full infrastructure control, enabling teams to own and manage their pipelines without relying on external platforms. The tool is positioned to address growing challenges in modern software development, particularly the strain caused by AI-generated code and agent-driven workflows, which existing CI/CD systems are ill-equipped to handle due to their outdated, human-centric designs. Current tools struggle with scalability, bottlenecks in source control, testing, and pull request processes, and the exponential increase in code volume driven by AI agents. This has led to reliability issues and difficulties in maintaining code quality and infrastructure under the pressures of AI-augmented development.

The discussion highlights the urgent need for new, scalable infrastructure primitives tailored for AI-driven workflows. Depot CI seeks to bridge these gaps by offering agent-friendly tools that can manage the complexity and volume of AI-generated code. Looking ahead, Depot plans to expand its platform by supporting multiple CI/CD pipeline syntaxes (e.g., Circle CI, Jenkins) through an open-source, pluggable system, while emphasizing community-driven development. Long-term goals include creating a unified ecosystem that integrates source control, CI/CD, code review, and collaboration tools to scale small teams to large organizations using AI agents. Additionally, there is a broader push to rethink collaboration paradigms and infrastructure design to align with the agent-driven development era.

The text also touches on insights into the European tech scene, noting Londons influence as a tech hub shaped by its financial sector and regional differences in tech activity, with cities like Berlin, Amsterdam, and Barcelona showing growing innovation. Europe is increasingly contributing to AI research and large language model advancements, though it still lags behind regions like San Francisco in scale. These observations underscore the global context of infrastructure challenges and evolving development practices driven by AI and automation.

What If

  • What if you leveraged Depot CI's sandbox technology to automate AI-generated code testing in your solo project?

    • Concrete move: Write a custom pipeline using Depot's TypeScript SDK to automatically run AI-generated code through isolated sandbox environments for security and performance checks.
    • Why now: Existing CI/CD tools can't scale with AI's code volume; Depot's sandbox provides full infrastructure control to handle this.
    • Expected upside: Reduce manual testing overhead by 70% and ensure code reliability at scale.
  • What if you built a plugin for Depot CI to integrate AI agents into your CI/CD workflow for real-time code review?

    • Concrete move: Develop a plugin using Depot's pluggable architecture that triggers AI agents (e.g., for linting or documentation) during pipeline execution.
    • Why now: Current tools lack agent-friendly integration; Depot's open-source model allows you to shape the future of collaboration.
    • Expected upside: Cut code review cycles by 50% and improve code quality through AI-augmented feedback.
  • What if you prioritized Depot CI's multi-syntax support to migrate legacy Jenkins pipelines to a unified system?

    • Concrete move: Use Depot's open-source compatibility layer to rewrite your Jenkins pipelines into Depot CI's syntax, enabling cross-team collaboration.
    • Why now: Legacy tools like Jenkins can't handle AI-scale workflows; Depot's flexibility future-proofs your infrastructure.
    • Expected upside: Reduce maintenance costs by 60% and align your CI/CD with modern, scalable practices.

Takeaway

  • Adopt Depot CI's SDK for Custom Pipelines: Use Depot's TypeScript or Python SDK to build and automate CI/CD pipelines tailored to your project's needs, ensuring full control over infrastructure and scalability for AI-generated workflows.
  • Leverage Proprietary Sandbox Technology: Implement Depot's sandboxed environment for testing AI/agent workflows, ensuring isolation and reliability without relying on outdated tools like GitHub Actions.
  • Integrate AI Agents for Code Review: Deploy AI-augmented agents to automate code quality checks and reduce manual review burdens, addressing challenges in maintaining reliability under high-volume AI-driven development.
  • Contribute to Open-Source Plugin Ecosystem: Participate in Depot CI's pluggable system by developing or adopting community-driven plugins to support multiple CI/CD syntaxes (e.g., Jenkins, CircleCI), enhancing flexibility for your workflow.
  • Design Agent-Friendly Infrastructure: Prioritize infrastructure that scales with AI-generated code by using Depot's tools to unify source control, CI/CD, and collaboration workflows into a cohesive, scalable ecosystem.

Recent Episodes of Scaling DevTools

1 May 2026 Charity Majors on AI, Observability, and the Future of Software

Evolving software development challenges highlight the shift from code generation costs to observability as a critical bottleneck, advocating for product coherence over syntax, durable code over disposable iterations, and strategic AI integration amid persistent gaps in leadership and observability adoption.

14 Apr 2026 Lawrence Jones from Incident.io @ AIE Europe: building an AI SRE

Advancements in AI-driven SRE include automated root cause analysis tools for managing production system complexity, challenges in scaling AI due to logging and data variability, the need for human expertise in contextual reasoning, handling vast log telemetry, and examples of AI uncovering undocumented system behaviors while emphasizing centralized incident management, ambient analysis tools, and the upcoming AI Incident System (AIS).

More Scaling DevTools episodes