GitHub
At Universe, GitHub folds Copilot into Enterprise seats and lets Copilot Fusion pick the model.
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.
Shared themes:self-hosted
NSD vs Rivet: at a glance
| Feature | NSD | Rivet |
|---|---|---|
| Sector | DevOps | DevOps |
| Velocity score | 5.0 | 7.5 |
| Sparks · 30d | 0 | 2 |
| Top themes | dns, security, open-source, networking | actors, serverless, storage engine, s3 |
| Last editorial update | 1mo ago | 3d ago |
| Website | Visit → | — |
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 Rivet?
Rivet 3.0 Preview runs as one stateless binary on WarpDrive, with S3 as its only dependency.
Rivet has spent two months building infrastructure for long-lived actors and AI agents: BYOC in customer clouds, OpenTelemetry tracing, actor-scoped JWTs, Pi agent runtimes and agentOS Hosted VMs. On October 5 it said 3.0 would replace NATS with S3. The October 26 3.0 Preview delivers that: a new storage engine, WarpDrive, promises bottomless storage on S3 at SSD speed, and Rivet becomes a single stateless binary.
NSD vs Rivet: 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.
Rivet
7.5DEVOPS
Rivet 3.0 Preview runs as one stateless binary on WarpDrive, with S3 as its only dependency.
◆ Current state
Rivet has spent two months building infrastructure for long-lived actors and AI agents: BYOC in customer clouds, OpenTelemetry tracing, actor-scoped JWTs, Pi agent runtimes and agentOS Hosted VMs. On October 5 it said 3.0 would replace NATS with S3. The October 26 3.0 Preview delivers that: a new storage engine, WarpDrive, promises bottomless storage on S3 at SSD speed, and Rivet becomes a single stateless binary.
◆ Where it's heading
Each release removes operational burden: BYOC moved the control plane into the customer's cloud, and 3.0 reduces the self-hosted footprint to one binary plus an S3 bucket. The agent work (Pi, agentOS) sits on top as the main workload Rivet is courting.
◆ Prediction
Expect benchmarks and migration guidance for 2.x users during the preview, followed by a 3.0 GA. The entry gives no performance numbers, so the SSD-speed claim is unverified.
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.
CodeRabbit
CodeRabbit moves its review status to a GitHub check run and keeps Deep Scan coverage fresh.
Apache Arrow Rust
Arrow Rust 60.1.0 ships, redacting Parquet encryption keys and adding read-ahead planning.
Zed
Zed 1.26 adds Pyrefly for Python and debugs WebAssembly from the JavaScript debugger.
Sanity
Sanity's MCP server now advertises itself to agents through a server card and llms.txt.
Kubernetes
Kubernetes moves conformance from the cluster to the workloads running on it.
Recent activity from NSD and Rivet
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3d agoRivetIntroducing Rivet 3.0 Preview ⚡
- 17d agoRivetIntroducing agentOS 0.4 & Hosted VMs
- 22d agoRivetIntroducing Pi Durable for Rivet
- 24d agoRivetReplacing Our Message Broker with... S3? ⚡
- 28d agoRivetIntroducing Pi 1.0 for Rivet
- 1mo agoRivetIntroducing JWT Authentication for Rivet Actors
- 1mo agoNSDNSD 4.15.2 released
- 2mo agoNSDNSD 4.15.2 release candidate
- 2mo agoNSDNSD 4.15.1 security release: four CVEs fixed
- 3mo agoNSDNSD 4.15.0 released
- 4mo agoNSDNSD 4.15.0 release candidate
- 4mo agoNSDNSD 4.14.3: four CVEs including heap overflow and TLS authentication bypass
Frequently asked questions
What is the difference between NSD and Rivet?
Both compete on the same themes — self-hosted — within DevOps. Rivet is currently shipping more aggressively (velocity 7.5 vs 5.0), with 2 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 7.5 vs 5.0), with 2 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.