← Back to home
Comparison · DevOps

NSD vs Weaviate

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

NSD vs Weaviate: at a glance

FeatureNSDWeaviate
SectorDevOpsDevOps
Velocity score5.08.8
Sparks · 30d03
Top themesdns, security, open-source, networkingvector-search, agent-memory, quantization, disk-indexing
Last editorial update20d ago10h ago
WebsiteVisit →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.

Read the full NSD trajectory →

What is Weaviate?

Weaviate ships Engram agent memory, HFresh disk indexing, and 4-bit quantization in quick succession

Weaviate 1.39 is the current stable release, having GA'd the Boost API and MMR diversity selection while introducing an experimental Search REST API. Two major storage advances landed in rapid succession: HFresh, a disk-based vector index that keeps vectors off the heap entirely, and 4-bit Rotational Quantization, which compresses stored vectors with minimal accuracy loss. Above the storage layer, Engram — a named agent memory product — is the most significant architectural addition: it lets builders configure extraction topics, scopes, and retrieval modes as first-class settings rather than building memory pipelines by hand.

Read the full Weaviate trajectory →

NSD vs Weaviate: 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.

W
Weaviate
DEVOPS
8.8

Weaviate ships Engram agent memory, HFresh disk indexing, and 4-bit quantization in quick succession

◆ Current state

Weaviate 1.39 is the current stable release, having GA'd the Boost API and MMR diversity selection while introducing an experimental Search REST API. Two major storage advances landed in rapid succession: HFresh, a disk-based vector index that keeps vectors off the heap entirely, and 4-bit Rotational Quantization, which compresses stored vectors with minimal accuracy loss. Above the storage layer, Engram — a named agent memory product — is the most significant architectural addition: it lets builders configure extraction topics, scopes, and retrieval modes as first-class settings rather than building memory pipelines by hand.

◆ Where it's heading

Weaviate is executing a two-layer expansion: at the bottom, making the vector store cheaper and more flexible (quantization, disk-based indexing, query profiling); at the top, building agent-native abstractions that make Weaviate more than a search backend (Engram memory, effort tiers, Search REST API). The direction has shifted from 'fast vector database' toward 'infrastructure for AI agent memory and retrieval systems.' The consistent release of deep technical content alongside product updates suggests the team is deliberately targeting developers building production agent systems, not just evaluating vector databases.

◆ Prediction

Engram moving from guide to GA release is the most predictable next step. The experimental Search REST API, introduced in 1.39, is also positioned to stabilize — and the growing late-interaction retrieval work (multi-vector for PDFs and charts) looks like the foundation of a more formal multi-modal retrieval product rather than staying at the technique level.

Alternatives to NSD and Weaviate

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

See all NSD alternatives → · See all Weaviate alternatives →

Recent activity from NSD and Weaviate

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

  1. 1d agoWeaviateAgent Memory with Engram: A Practical Guide
  2. 6d agoWeaviate4-bit Rotational Quantization
  3. 14d agoWeaviateHFresh: Memory-Efficient Vector Search
  4. 15d agoWeaviateBuilding Foundry Part 3: From archive to creative search
  5. 20d agoNSDNSD 4.15.2 released
  6. 22d agoWeaviateHow to extract meaning from charts and tables in PDFs
  7. 27d agoWeaviateWeaviate 1.39: Boost API and MMR diversity hit GA, experimental Search REST API ships
  8. 28d agoNSDNSD 4.15.2 release candidate
  9. 28d agoNSDNSD 4.15.1 security release: four CVEs fixed
  10. 2mo agoNSDNSD 4.15.0 released
  11. 2mo agoNSDNSD 4.15.0 release candidate
  12. 3mo agoNSDNSD 4.14.3: four CVEs including heap overflow and TLS authentication bypass

Frequently asked questions

What is the difference between NSD and Weaviate?

They serve adjacent needs but don't currently overlap on shipped themes. Weaviate 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 Weaviate?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Weaviate 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 Weaviate?

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