authentik
Seven release candidates in eight days, and rc7 quietly carries the endpoint agent.
Comparison · Infra & APIs
Depot vs werf
A side-by-side editorial comparison of Depot and werf — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:ci-cd
Depot vs werf: at a glance
| Feature | Depot | werf |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 6.3 | 5.0 |
| Sparks · 30d | 1 | 0 |
| Top themes | ci-cd, build-acceleration, test-analytics, source-control | ci-cd, kubernetes, build-concurrency, multi-channel |
| Last editorial update | 3h ago | 1h ago |
| Website | — | Visit → |
What is Depot?
Depot is expanding from faster builds into the whole CI stack — tests, source control, and its own metal.
Depot has spent the last month building outward from build acceleration. Test results went generally available with JUnit ingest, org-wide flaky and slow test analytics, and timing-based shard balancing. Underneath that, Depot Metal moved CI and Sandboxes onto bare-metal microVMs the company controls end to end, and Depot Code entered private beta as a diskless git server backed by blob storage. The smaller releases fill in the surrounding surface: Tailscale access to private networks, GitLab OIDC, Datadog CI Visibility, stacked pull requests, and macOS 26 runners on M4.
What is werf?
Four release channels, one build engine — werf's changelog is mostly concurrency bugs.
werf publishes across alpha, beta, ea, stable and dev channels simultaneously, so the same fix often appears under several tags within minutes. The 2.x line is in maintenance: the recurring subject is build concurrency — parallel Buildah recovery failures, serialized concurrent base image pulls, retries when a cached image id is missing, races during Docker builds, and panics on late worker logs. A 3.x line runs alongside on the dev channel, where the feature work actually lands.
Depot vs werf: editorial side-by-side
Depot
6.3INFRA · APIS
Depot is expanding from faster builds into the whole CI stack — tests, source control, and its own metal.
◆ Current state
Depot has spent the last month building outward from build acceleration. Test results went generally available with JUnit ingest, org-wide flaky and slow test analytics, and timing-based shard balancing. Underneath that, Depot Metal moved CI and Sandboxes onto bare-metal microVMs the company controls end to end, and Depot Code entered private beta as a diskless git server backed by blob storage. The smaller releases fill in the surrounding surface: Tailscale access to private networks, GitLab OIDC, Datadog CI Visibility, stacked pull requests, and macOS 26 runners on M4.
◆ Where it's heading
Each layer Depot adds is one it previously rented — compute from cloud runners, source hosting from GitHub, test insight from nothing at all. Owning the storage and hypervisor tiers is what makes the performance claims possible, and owning test data is what turns a build accelerator into something that reports on the pipeline rather than just running it faster. The pattern suggests Depot is positioning as the full CI platform, with speed as the entry point rather than the product.
◆ Prediction
Depot Code should move from private to open beta with tighter Depot CI integration, since a git server the company controls is what makes source-aware caching and test selection possible. Expect the test analytics to grow toward selecting which tests to run, not only how to split them.
werf
5.0INFRA · APIS
Four release channels, one build engine — werf's changelog is mostly concurrency bugs.
◆ Current state
werf publishes across alpha, beta, ea, stable and dev channels simultaneously, so the same fix often appears under several tags within minutes. The 2.x line is in maintenance: the recurring subject is build concurrency — parallel Buildah recovery failures, serialized concurrent base image pulls, retries when a cached image id is missing, races during Docker builds, and panics on late worker logs. A 3.x line runs alongside on the dev channel, where the feature work actually lands.
◆ Where it's heading
Development has effectively split. The 2.x channels get defensive fixes to the existing build path, while 3.1.0 on dev carries the additions — embedded kubeconform schemas, a per-project meta-repo safeguard with migration, additional patch files with an option to disable defaults, and a values-schema validation escape hatch. The dev branch is also where the local-loop work sits, with a persistent dev-index so --dev stops re-reading unchanged files and self-healing for a stale worktree lock left by a killed run.
◆ Prediction
The 2.x channels look set to keep absorbing build-concurrency and host-cleanup fixes while 3.x accumulates features on dev ahead of promotion. When the 3.x line reaches the stable channel isn't something these entries indicate.
Alternatives to Depot and werf
Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either Depot or werf.
Ansible
Four maintenance branches move in lockstep, with the actual changes hidden behind a link.
Ably
Ably is building an agent transport layer on its realtime core, shipping AI SDK versions every ten days.
Casdoor
One commit, one release: nine tags in a week, tightening org-level control and credential handling.
Cronicle
Cronicle has spent 2026 hardening the paths that let a scheduler run arbitrary commands
oVirt
A virtualization manager coasting on backports, with releases years apart
Recent activity from Depot and werf
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 10h agowerfv2.76.0 [alpha]
- 1d agoDepotmacOS 26 is now the default macOS version for GitHub Actions runners
- 4d agowerfSignature tag update (not a release)
- 4d agowerfv2.75.3 [beta,ea,stable]
- 4d agowerfv2.75.4 [alpha]
- 5d agowerfv3.1.0 [dev]
- 8d agoDepotDepot CI now supports native GitHub stacked pull requests
- 11d agowerfwerf 3.0.2 build-log progress index fix
- 13d agoDepotTest results are now generally available ⚡
- 21d agoDepotAI analysis available for all Depot CI workflows and jobs
- 27d agoDepotSplit CI test suites with historical timing data (beta)
- 1mo agoDepotDepot CI now supports Tailscale
Frequently asked questions
What is the difference between Depot and werf?
Both compete on the same themes — ci-cd — within Infra & APIs. Depot is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is Depot better than werf?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Depot is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.
What are the best alternatives to Depot?
Top Depot alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Depot alternatives" section above for the current picks, or visit /alternatives/depot for the full list with editorial commentary on each.
What are the best alternatives to werf?
Top werf alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "werf alternatives" section above for the current picks, or visit /alternatives/werf for the full list with editorial commentary on each.