Depot
Depot turns its build-acceleration compute into a metered backend for AI agents.
◆Recent moves
- 8d ago
SOCI v2 support for Depot container builds
Container builds now support SOCI (Seekable OCI) v2, so compatible runtimes start after downloading only the files they need instead of pulling the whole image, cutting startup for large CUDA or PyTorch images. The index is generated at build time, with no post-push pipeline. Squarely aligned with serving ML and AI workloads.
- 9d ago
Sandbox SDK is now available in private beta
⚡ SPARKDepot opens a new product surface with a Sandbox SDK to run untrusted or agent-generated code in isolated, ephemeral sandboxes, billed per vCPU-second. This is the clearest signal of Depot positioning its compute as a backend for AI agents, not just builds.
- 15d ago
Native step retries in Depot CI
Depot CI adds a native retry: key on run steps with configurable attempts and backoff, replacing the need to vendor a marketplace retry action. A practical reliability win for flaky commands that keeps users inside the platform.
View source ↗ - 17d ago
Durable cache disks for Depot CI jobs are now available in beta
Durable, multi-write cache disks (beta) persist content between CI runs in a POSIX filesystem, enabling artifact reuse and fan-out read/write patterns across runners. Strengthens the CI platform's performance story.
- 23d ago
Depot CI API and CLI are now generally available
The Depot CI API and CLI reach general availability with full dashboard parity, an OpenAPI v3 spec, and AI run summaries, so scripts and agents can trigger, inspect, and manage runs from one contract. Key to the API-first, agent-drivable direction.
View source ↗ - 24d ago
SSH into Depot CI sandboxes now uses exec.depot.dev
SSH access to CI sandboxes moves to a dedicated host, exec.depot.dev, behind a dedicated proxy. Mostly transparent once the CLI is updated; only raw ssh users targeting api.depot.dev need to change anything.