incident.io
Nexus does the diagnosis; the rest is on-call plumbing
Comparison · Infra & APIs
Depot vs Tailscale
A side-by-side editorial comparison of Depot and Tailscale — release velocity, themes, recent moves, and the top alternatives to consider.
Depot vs Tailscale: at a glance
| Feature | Depot | Tailscale |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 6.3 | 6.3 |
| Sparks · 30d | 1 | 1 |
| Top themes | ci-cd, build-acceleration, test-analytics, source-control | tailnet-api, tailscale-services, ssh-hardening, cli-surface |
| Last editorial update | 1d ago | 3d ago |
| Website | — | — |
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 Tailscale?
Tailnets become API-provisioned resources while Tailscale hardens SSH and thins the control plane.
Tailscale is in a steady release cadence on the 1.102 line, with the substantive work landing in 1.102.1 and the two releases after it carrying only fixes and library bumps. That release added a Services-oriented CLI surface (tailscale get, whoami, service list), Serve byte metrics for Tailscale Services, and constant-time node addition and removal that cuts CPU on large tailnets. Separately, an alpha tailnet creation API turns tailnets themselves into programmable objects, and the admin console has moved to its own subdomain. A 1.98.10 backport closed two Tailscale SSH vulnerabilities on the older branch.
Depot vs Tailscale: 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.
Tailscale
6.3INFRA · APIS
Tailnets become API-provisioned resources while Tailscale hardens SSH and thins the control plane.
◆ Current state
Tailscale is in a steady release cadence on the 1.102 line, with the substantive work landing in 1.102.1 and the two releases after it carrying only fixes and library bumps. That release added a Services-oriented CLI surface (tailscale get, whoami, service list), Serve byte metrics for Tailscale Services, and constant-time node addition and removal that cuts CPU on large tailnets. Separately, an alpha tailnet creation API turns tailnets themselves into programmable objects, and the admin console has moved to its own subdomain. A 1.98.10 backport closed two Tailscale SSH vulnerabilities on the older branch.
◆ Where it's heading
Two threads are running in parallel. The first is scaling the tailnet as infrastructure: constant-time node churn, an API for creating and deleting tailnets, and a growing CLI vocabulary around Tailscale Services all point at tailnets being provisioned and torn down programmatically rather than administered by hand. The second is tightening the identity edge, with SSH permission checks patched on both the current and previous branches and Funnel certificate renewal moved to TLS-ALPN-01. The version-numbered releases increasingly carry plumbing while the named features carry the direction.
◆ Prediction
The tailnet creation API graduating from alpha, with the per-tailnet lifecycle exposed through the same CLI and policy surface as nodes, is the natural next step. Continued Services-related CLI and metrics additions on the 1.102 line look likely given how much of 1.102.1 went that way.
Alternatives to Depot and Tailscale
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 Tailscale.
werf
Four channels, one fix stream — werf's releases are mostly concurrency repairs.
ZoneMinder
1.38.4 is a security release in all but name, closing ACL gaps across the API.
Infisical
PAM and PKI now take up most of the lines in Infisical's release notes.
Biome
Biome's patch train keeps adding rules — and is quietly growing a Markdown linter.
DNSControl
DNSControl is rewriting its record internals in public, one release candidate at a time
See all Depot alternatives → · See all Tailscale alternatives →
Recent activity from Depot and Tailscale
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2d agoDepotmacOS 26 is now the default macOS version for GitHub Actions runners
- 5d agoTailscaleContainer image v1.102.2: library updates only
- 8d agoTailscalev1.102.2 fixes a Funnel incoming-connection regression
- 9d agoDepotDepot CI now supports native GitHub stacked pull requests
- 9d agoTailscalev1.102.1 adds Services CLI and constant-time node churn
- 14d agoDepotTest results are now generally available ⚡
- 14d agoTailscaleTailnet creation API ⚡
- 15d agoTailscalev1.98.10 backports two Tailscale SSH security fixes
- 20d agoTailscaleAdmin console URL change
- 22d agoDepotAI analysis available for all Depot CI workflows and jobs
- 28d 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 Tailscale?
They serve adjacent needs but don't currently overlap on shipped themes. Depot and Tailscale are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is Depot better than Tailscale?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Depot and Tailscale are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). 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 Tailscale?
Top Tailscale alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Tailscale alternatives" section above for the current picks, or visit /alternatives/tailscale for the full list with editorial commentary on each.