Tailscale vs Depot
Side-by-side trajectory, velocity, and editorial themes.
Tailscale fills out enterprise plumbing while opening a new front in AI-agent control.
The mainline Tailscale client and Terraform provider continue to ship steadily — v1.98 with MagicDNS and Linux subnet-router fixes, Terraform v0.29 adding first-class Tailscale Services support. Admin-console work (domain management, device posture visibility, paid-tier scaling for tagged resources) targets enterprise operability. Underneath the routine version cadence, the recent Aperture beta points the company up the stack into AI-agent governance.
Two threads are running in parallel. The connectivity product is hardening for larger deployments: Terraform-native service modeling, posture surfacing in the console, and explicit billing levers for tagged resources past the 50-device line. The second thread, Aperture, repositions Tailscale's identity-and-policy primitives as a control plane for LLM calls and agent tools — same trust model, new target workload.
Expect Aperture to graduate out of beta with broader provider coverage and tighter ties to Tailscale ACLs, while the core client continues a predictable point-release cadence. The enterprise plumbing improvements suggest paid-tier expansion (more usage-based dials) before the next big platform push.
Depot is rounding out Depot CI into a credible GitHub Actions alternative, and just shipped nested virtualization.
Eight of the last ten changelog entries are Depot CI updates: a new workflow summary page, environment-aware secret and variable variants, CLI commands for metrics, JSON status output, live log streaming, workflow listing and inspection, run cancel/rerun/retry/dispatch, and a DEPOT_JOB_URL env var in every job. Registry got pull-through cache improvements with provider presets. The dominant theme is filling in the feature surface a serious CI platform needs.
Depot is methodically closing the gap between its CI product and the incumbents. The recent run reads like a checklist: workflow UX, secrets, metrics, log streaming, scriptable CLI surface — the table-stakes ergonomics teams expect before migrating off GitHub Actions or CircleCI. The May 20 nested virtualization release expands what kinds of workloads Depot CI can host at all, not just how nicely it hosts them, which is a different and more aggressive move.
Expect more workload-expansion moves following the nested virtualization release — likely Android-specific tooling, deeper matrix/sharding UX (the workflow page already groups matrix failures), and continued CLI parity work. The secrets-and-variables variant model looks set up to grow into broader policy-as-code for CI configuration.
See more alternatives to Tailscale →
See more alternatives to Depot →