DNSControl
DNSControl v5 is feature-frozen with a ship date, and rc9 is pure provider cleanup
A side-by-side editorial comparison of Tailscale and ZoneMinder — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Tailscale | ZoneMinder |
|---|---|---|
| Sector | Infra & APIs | Infra & APIs |
| Velocity score | 6.3 | 2.5 |
| Sparks · 30d | 1 | 0 |
| Top themes | networking, zero-trust, kubernetes, multi-tenancy | security-hardening, rbac, api-authorization, maintenance-branch |
| Last editorial update | 13h ago | 7d ago |
| Website | — | Visit → |
Tailscale is turning the tailnet itself into something a script provisions and pages through.
Two threads run in this window. The client and operator releases are maintenance-grade — a Funnel regression fix, library-only container updates, Kubernetes operator work on PeerRelays, workload identity federation and IPv6 egress. The more consequential thread is the tailnet management API: creation landed in alpha at the end of July, and the list endpoint has now been paginated, with a hard 100-result default for organizations holding more.
1.38.4 is a security release in all but name, closing ACL gaps across the API.
The 1.38 line is in maintenance, and 1.38.4 is almost entirely authorization work: per-monitor access control enforced on event, frame, zone, tag and media endpoints, two auth bypasses fixed in token validation, and SQL injection and overflow hardening. The 1.36 branch still receives backports, with 1.36.38 carrying its own SQL injection fix. The last feature release was 1.38.0 in February, which brought role-based access control, WebRTC and Go2RTC streaming, and the split of monitor function into separate capturing, analysing, and recording settings.
Two threads run in this window. The client and operator releases are maintenance-grade — a Funnel regression fix, library-only container updates, Kubernetes operator work on PeerRelays, workload identity federation and IPv6 egress. The more consequential thread is the tailnet management API: creation landed in alpha at the end of July, and the list endpoint has now been paginated, with a hard 100-result default for organizations holding more.
Tailscale has spent this period on two different customers at once. The operator work serves platform teams running Tailscale inside Kubernetes, where the gaps being closed are reconciliation loops, stale DNS ConfigMaps and cert-renewal backoff. The tailnet API work serves a different shape entirely: organizations holding enough tailnets that a hundred is a page boundary, which only happens when tailnets are allocated per customer or per environment rather than per company. The second thread is the one that changes what Tailscale is for.
Pagination on list implies the creation API is being used at volume, so expect the alpha to gain the management operations a fleet needs — policy templating or bulk configuration across tailnets. The client release line looks settled on 1.102.x maintenance in the near term.
The 1.38 line is in maintenance, and 1.38.4 is almost entirely authorization work: per-monitor access control enforced on event, frame, zone, tag and media endpoints, two auth bypasses fixed in token validation, and SQL injection and overflow hardening. The 1.36 branch still receives backports, with 1.36.38 carrying its own SQL injection fix. The last feature release was 1.38.0 in February, which brought role-based access control, WebRTC and Go2RTC streaming, and the split of monitor function into separate capturing, analysing, and recording settings.
Every release since 1.38.0 has been consolidation of what that release opened up. RBAC shipped as a headline feature in February, and the four maintenance drops since have been finding the endpoints it did not cover — the familiar pattern when a permission model is retrofitted onto an API that predates it. Cadence is slow and irregular, months apart, with a 1.39 spec bump already visible in the repo but nothing from that series shipped.
Expect more per-endpoint ACL fixes on the 1.38 line before anything from 1.39 reaches release.
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 Tailscale or ZoneMinder.
DNSControl v5 is feature-frozen with a ship date, and rc9 is pure provider cleanup
Casdoor is spending its release cadence moving auth checks from the client to the server
ESPHome ships on a calendar, and the August beta train is now five builds deep
Strimzi's 1.2.0 candidate closes with a logging fix and nothing else
Prowler's assistant decides what to do with findings; the patches keep the scanner honest
NetBox adds a cooling data model — the first new infrastructure domain since power
See all Tailscale alternatives → · See all ZoneMinder alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Tailscale is currently shipping more aggressively (velocity 6.3 vs 2.5), 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Tailscale is currently shipping more aggressively (velocity 6.3 vs 2.5), 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.
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.
Top ZoneMinder alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "ZoneMinder alternatives" section above for the current picks, or visit /alternatives/zoneminder for the full list with editorial commentary on each.