← Back to home
Comparison · DevOps

NSD vs Rivet

A side-by-side editorial comparison of NSD and Rivet — release velocity, themes, recent moves, and the top alternatives to consider.

NSD vs Rivet: at a glance

FeatureNSDRivet
SectorDevOpsDevOps
Velocity score5.08.8
Sparks · 30d03
Top themesdns, security, open-source, networkingactor-model, byoc, mcp, agent-infrastructure
Last editorial update12d ago1d ago
WebsiteVisit →

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.

Read the full NSD trajectory →

What is Rivet?

Rivet positions its Actors runtime as the infrastructure layer for enterprise-ready, AI-native application deployment.

Rivet has shipped three substantive capability moves in rapid succession: BYOC (Bring Your Own Cloud, letting enterprises run Rivet's control plane inside their own AWS or GCP VPCs), MCP integration (exposing Rivet Actors as a first-class tool in Claude Code, Cursor, Codex, and Gemini CLI), and Dynamic Apps (a V8-isolate-based runtime for deploying AI-generated applications for end users). Underneath all of this is the Actors model — a durable, stateful compute primitive built on open-source infrastructure. Durable Streams, a zero-disk SQLite storage engine with S3 tiering, and the agentOS execution API round out the technical foundation.

Read the full Rivet trajectory →

NSD vs Rivet: editorial side-by-side

N
NSD
DEVOPS
5.0

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.

R
Rivet
DEVOPS
8.8

Rivet positions its Actors runtime as the infrastructure layer for enterprise-ready, AI-native application deployment.

◆ Current state

Rivet has shipped three substantive capability moves in rapid succession: BYOC (Bring Your Own Cloud, letting enterprises run Rivet's control plane inside their own AWS or GCP VPCs), MCP integration (exposing Rivet Actors as a first-class tool in Claude Code, Cursor, Codex, and Gemini CLI), and Dynamic Apps (a V8-isolate-based runtime for deploying AI-generated applications for end users). Underneath all of this is the Actors model — a durable, stateful compute primitive built on open-source infrastructure. Durable Streams, a zero-disk SQLite storage engine with S3 tiering, and the agentOS execution API round out the technical foundation.

◆ Where it's heading

Rivet is building toward a single answer to a specific question: where does agent-generated, user-facing software actually run? The BYOC move unlocks regulated industries and large enterprises who can't send data to a SaaS control plane. MCP turns Rivet's Actors into something any AI client can discover and call without bespoke integration. Dynamic Apps makes Rivet the runtime, not just the infrastructure, for user-generated software. The through-line is that Rivet wants every AI agent — whether built by a developer or generated at runtime — to run on the Actors primitive with Rivet managing the lifecycle.

◆ Prediction

BYOC on AWS/GCP is the foundation; Azure support and SOC 2 certification are the logical next steps to close enterprise deals. Expect MCP to expand to more clients (OpenAI Codex, Copilot, Windsurf) as the MCP ecosystem grows, and Dynamic Apps to get versioning and rollback — the missing piece for user-facing production deployments.

Alternatives to NSD and Rivet

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 Rivet.

See all NSD alternatives → · See all Rivet alternatives →

Recent activity from NSD and Rivet

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 1d agoRivetIntroducing Rivet BYOC
  2. 6d agoRivetIntroducing Rivet MCP
  3. 13d agoNSDNSD 4.15.2 released
  4. 13d agoRivetDurable Streams now supports Rivet Actors
  5. 16d agoRivetIntroducing Dynamic Apps: Deploy AI-Generated Apps for Your Users
  6. 21d agoNSDNSD 4.15.2 release candidate
  7. 21d agoNSDNSD 4.15.1 security release: four CVEs fixed
  8. 1mo agoRivetRivet ships zero-disk SQLite with S3-tiered cold storage
  9. 1mo agoRivetIntroducing agentOS Execution API for JavaScript and Python
  10. 2mo agoNSDNSD 4.15.0 released
  11. 2mo agoNSDNSD 4.15.0 release candidate
  12. 2mo agoNSDNSD 4.14.3: four CVEs including heap overflow and TLS authentication bypass

Frequently asked questions

What is the difference between NSD and Rivet?

They serve adjacent needs but don't currently overlap on shipped themes. Rivet is currently shipping more aggressively (velocity 8.8 vs 5.0), with 3 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 Rivet?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Rivet is currently shipping more aggressively (velocity 8.8 vs 5.0), with 3 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 Rivet?

Top Rivet alternatives in DevOps are ranked by recent ship velocity. Browse the "Rivet alternatives" section above for the current picks, or visit /alternatives/rivet for the full list with editorial commentary on each.