GitHub
GitHub Copilot tightens enterprise governance while AI security scanning drops its CodeQL prerequisite
Comparison · DevOps
NSD vs Sanity
A side-by-side editorial comparison of NSD and Sanity — release velocity, themes, recent moves, and the top alternatives to consider.
NSD vs Sanity: at a glance
What is NSD?
NSD patched 8 CVEs across two dedicated security releases and added EDNS0 padding and PROXYv2 access controls.
NSD released three significant versions in quick succession: 4.15.1 fixed four CVEs including a TCP-window-throttle DoS, a UDP cookie-option DoS, an IP ACL bypass for some address ranges, and a PROXYv2 port ACL bypass. 4.15.2 followed with feature additions — HHIT/BRID RR type support, new SVCB service parameter keys (docpath, pvd, oots), EDNS0 padding over TLS per RFC 7830/8467, and configurable PROXYv2 access control — alongside another substantial round of hardening fixes, many reported by Palo Alto Networks. The 4.15.0 release introduced a breaking change to Prometheus metrics, moving zone names from metric labels to label values.
What is Sanity?
Sanity's MCP server hits v2.33 with safer publishing guards as Studio bug-fix cadence accelerates
Sanity is running two parallel tracks simultaneously: Studio (v6.14.x) is receiving rapid bug-fix releases targeting real-world pain — Portable Text data-loss risks, appearance theming inconsistencies, popover UX regressions. At the same time, the MCP server is iterating weekly from v2.31 to v2.33, adding revision guards for safer publishing, distributed-tracing auth fixes, and token-efficient query responses. The combined picture is a team hardening both the human-facing editor and the AI-tool-facing API interface.
NSD vs Sanity: editorial side-by-side
NSD
5.0DEVOPS
NSD patched 8 CVEs across two dedicated security releases and added EDNS0 padding and PROXYv2 access controls.
◆ Current state
NSD released three significant versions in quick succession: 4.15.1 fixed four CVEs including a TCP-window-throttle DoS, a UDP cookie-option DoS, an IP ACL bypass for some address ranges, and a PROXYv2 port ACL bypass. 4.15.2 followed with feature additions — HHIT/BRID RR type support, new SVCB service parameter keys (docpath, pvd, oots), EDNS0 padding over TLS per RFC 7830/8467, and configurable PROXYv2 access control — alongside another substantial round of hardening fixes, many reported by Palo Alto Networks. The 4.15.0 release introduced a breaking change to Prometheus metrics, moving zone names from metric labels to label values.
◆ Where it's heading
NSD is in a security-intensive maintenance phase with a consistent external contributor: Qifan Zhang at Palo Alto Networks has reported the majority of bugs fixed in the 4.15.x cycle, including heap overflows, assertion failures on malformed records, and multiple DoS vectors. This external security research pressure is accelerating the quality of NSD's defensive posture. Protocol completeness work (new RR types, SVCB parameters) continues alongside the security fixes.
◆ Prediction
The PROXYv2 improvements suggest NSD deployments behind TLS-terminating load balancers are a growing use case — expect additional configuration controls for encrypted-DNS setups. The experimental multi-catalog-consumer-zones flag may graduate to stable in a future release.
Sanity
7.5DEVOPS
Sanity's MCP server hits v2.33 with safer publishing guards as Studio bug-fix cadence accelerates
◆ Current state
Sanity is running two parallel tracks simultaneously: Studio (v6.14.x) is receiving rapid bug-fix releases targeting real-world pain — Portable Text data-loss risks, appearance theming inconsistencies, popover UX regressions. At the same time, the MCP server is iterating weekly from v2.31 to v2.33, adding revision guards for safer publishing, distributed-tracing auth fixes, and token-efficient query responses. The combined picture is a team hardening both the human-facing editor and the AI-tool-facing API interface.
◆ Where it's heading
Sanity is building the MCP server into a production-grade write interface for AI agents. The `ifRevisionId` guard in v2.33 — which causes publishing to fail if a draft changed since the caller read it — is the kind of concurrency safety needed before AI agents can reliably edit live content. Studio stability work is catching up after a period of fast feature shipping. Expect MCP tool coverage to broaden and the auth/schema layers to continue hardening for enterprise-scale deployments.
◆ Prediction
The next MCP server release will likely add more write-path safety features — document locking or conflict detection. Studio v6.15 will address remaining edge cases exposed by the MCP surface's broader read/write coverage.
Alternatives to NSD and Sanity
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.
CodeRabbit
CodeRabbit adds TypeScript config and an attack surface mapper, stretching well past code review.
Gravity Forms
Gravity Forms ships an MCP server, putting AI assistants on a direct line to WordPress form data.
Speakeasy
Speakeasy becomes the enterprise control plane for MCP server access and AI tool governance.
Kubernetes
Kubernetes v1.37 matures its memory management and scheduling stack for AI/ML workloads.
NATS
NATS 2.15 introduces a desired-state reconciliation engine for JetStream, making cluster operations safe to run mid-flight.
Recent activity from NSD and Sanity
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 11h agoSanitySanity Studio v6.14.1: Fixes Portable Text editor data issue and contrast for comments
- 12h agoSanityMCP server v2.33.0: Safer publishing and clearer document errors
- 1d agoSanitySanity Studio v6.14.0: Fixes cut off popovers, a history restore bug, and reference search unexpectedly closing
- 1d agoSanitySanity React App SDK v3.2.0: Simplified GROQ type generation
- 1d agoSanityMCP server v2.32.3: More reliable authentication with distributed tracing
- 5d agoSanityMCP server v2.32.2: Smaller query responses and clearer tool arguments
- 13d agoNSDNSD 4.15.2 released
- 21d agoNSDNSD 4.15.2 release candidate
- 21d agoNSDNSD 4.15.1 security release: four CVEs fixed
- 2mo agoNSDNSD 4.15.0 released
- 2mo agoNSDNSD 4.15.0 release candidate
- 2mo agoNSDNSD 4.14.3: four CVEs including heap overflow and TLS authentication bypass
Frequently asked questions
What is the difference between NSD and Sanity?
They serve adjacent needs but don't currently overlap on shipped themes. Sanity is currently shipping more aggressively (velocity 7.5 vs 5.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.
Is NSD better than Sanity?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Sanity is currently shipping more aggressively (velocity 7.5 vs 5.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.
What are the best alternatives to NSD?
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.
What are the best alternatives to Sanity?
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.