Liquidsoap
Liquidsoap opens its 2.5 line with subtitles as a first-class content type and a streaming server of its own
A side-by-side editorial comparison of NSD and Sanity — release velocity, themes, recent moves, and the top alternatives to consider.
Memory work paid off, then a serious SVCB overflow arrived — and Prometheus users get a breaking relabel.
NSD's recent history runs through three arcs. The 4.14.0 release refactored RDATA storage to cut memory footprint, a regression was reported immediately for zones with large RRsets, and 4.14.1 closed that gap so consumption dropped in all cases. In June, 4.14.3 fixed two CVEs, one a heap overflow of up to 65,509 attacker-controlled bytes reachable through a crafted SVCB record. Then 4.15.0 moved zone identity in Prometheus metrics from the metric name into a label, with an explicit warning that current users must adapt. Every release ships as an rc1 with identical notes before the final.
Sanity ships across every package at once, and the agent-facing surface moves fastest.
Sanity releases as a fleet: MCP server, Studio, JavaScript client, Media Library and UI all cut versions within days of each other, and the changelog reads as one stream of package releases. The current window is dominated by two lanes — the MCP server steadily gaining tools agents can call, and a round of modernization breakage in the client libraries (ESM-only, Node 22.12 floor). Studio v6.10.0 now bundles the App SDK, so custom Studio tools can call SDK hooks without wiring their own provider.
NSD's recent history runs through three arcs. The 4.14.0 release refactored RDATA storage to cut memory footprint, a regression was reported immediately for zones with large RRsets, and 4.14.1 closed that gap so consumption dropped in all cases. In June, 4.14.3 fixed two CVEs, one a heap overflow of up to 65,509 attacker-controlled bytes reachable through a crafted SVCB record. Then 4.15.0 moved zone identity in Prometheus metrics from the metric name into a label, with an explicit warning that current users must adapt. Every release ships as an rc1 with identical notes before the final.
This is a mature authoritative nameserver where the remaining work is footprint, correctness and observability rather than protocol features. The memory refactor and its follow-up show a project willing to ship a structural change and then immediately correct for reported regressions. The SVCB overflow is a reminder that newer record types are where the parsing risk now lives, since the older ones have been fuzzed for two decades. NLnet Labs also rotated its release signing key at the start of 2026 and documents the fingerprint in each announcement.
Expect the Prometheus relabeling to generate follow-up fixes as operators hit dashboard breakage, and continued attention to newer record type parsing. The rc-then-final rhythm makes the next release predictable in shape if not in content.
Sanity releases as a fleet: MCP server, Studio, JavaScript client, Media Library and UI all cut versions within days of each other, and the changelog reads as one stream of package releases. The current window is dominated by two lanes — the MCP server steadily gaining tools agents can call, and a round of modernization breakage in the client libraries (ESM-only, Node 22.12 floor). Studio v6.10.0 now bundles the App SDK, so custom Studio tools can call SDK hooks without wiring their own provider.
The MCP server is where the capability surface is actually growing — asset upload, schema discovery, CORS management — each release handing agents another operation that previously needed a human in the dashboard. The library work underneath is consolidation: one module system, one supported Node line, fewer dependencies, and now one SDK shared between Studio extensions and standalone apps. Read together, Sanity is narrowing the number of ways to build against it while widening what an agent can do unattended.
Expect the MCP tool list to keep absorbing dashboard operations — deploy, dataset and role management are the obvious remaining gaps — and the ESM-only floor to propagate to the packages that have not taken it yet. The releases are per-package, so a single dated entry rarely tells the whole story of a given week.
Other DevOps 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 NSD or Sanity.
Liquidsoap opens its 2.5 line with subtitles as a first-class content type and a streaming server of its own
Appwrite keeps reworking its own plumbing — Go CLI, SquashFS mounts, and an MCP layer that refreshes itself
FusionAuth's feed publishes version numbers; whether they carry news is a coin flip.
The 6.1 candidate arrives carrying the same notes the beta already shipped in June.
Auth0 hands tenants a throttle on their own noisy apps
Vitest 5 is in bug-fix mode: the second RC is almost entirely hardening
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Sanity is currently shipping more aggressively (velocity 7.5 vs 0.0), with 0 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. Sanity is currently shipping more aggressively (velocity 7.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other DevOps products to evaluate alongside.
Top NSD alternatives in DevOps are ranked by recent ship velocity. Browse the "NSD alternatives" section above for the current picks, or visit /alternatives/nsd for the full list with editorial commentary on each.
Top Sanity alternatives in DevOps are ranked by recent ship velocity. Browse the "Sanity alternatives" section above for the current picks, or visit /alternatives/sanity for the full list with editorial commentary on each.