Liquidsoap
Liquidsoap opens its 2.5 line with subtitles as a first-class content type and a streaming server of its own
Comparison · DevOps
Manticore Search vs NSD
A side-by-side editorial comparison of Manticore Search and NSD — release velocity, themes, recent moves, and the top alternatives to consider.
Manticore Search vs NSD: at a glance
What is Manticore Search?
Three patch releases in eight hours: Manticore's 29.0 line is being stabilized in public.
Manticore shipped 29.0.3, 29.0.4 and 29.0.5 inside a single day, three days after the 29.0.2 release notes consolidated the sharding work. Two are correctness fixes in query handling — internal sort helper columns leaking into LEFT JOIN output, and NEAR and proximity distances being reset by repeated JSON query fixup. The third hardens the binary API against malformed search counts under a reported advisory.
What is NSD?
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.
Manticore Search vs NSD: editorial side-by-side
Manticore Search
6.3DEVOPS
Three patch releases in eight hours: Manticore's 29.0 line is being stabilized in public.
◆ Current state
Manticore shipped 29.0.3, 29.0.4 and 29.0.5 inside a single day, three days after the 29.0.2 release notes consolidated the sharding work. Two are correctness fixes in query handling — internal sort helper columns leaking into LEFT JOIN output, and NEAR and proximity distances being reset by repeated JSON query fixup. The third hardens the binary API against malformed search counts under a reported advisory.
◆ Where it's heading
The pattern after a major line opens is holding: the commit-level train keeps running at multiple releases a day while the newly exposed surfaces — sharded tables, LEFT JOIN, JSON query parsing — report their edge cases back. The bugs being caught are shaped by what 29.0 changed rather than by new work, and each one arrives with regression coverage attached, which is why they land as separate patch releases rather than accumulating. Search-side work continues to split between classic full-text concerns and the vector and conversational paths.
◆ Prediction
The patch cadence should keep compressing toward the ordinary rhythm as the 29.0 edge cases drain; the next substantive item is more likely to come from the columnar and KNN thread than from sharding, which has just had its release.
NSD
0.0DEVOPS
Memory work paid off, then a serious SVCB overflow arrived — and Prometheus users get a breaking relabel.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to Manticore Search and NSD
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 Manticore Search or NSD.
Appwrite
Appwrite keeps reworking its own plumbing — Go CLI, SquashFS mounts, and an MCP layer that refreshes itself
FusionAuth
FusionAuth's feed publishes version numbers; whether they carry news is a coin flip.
Sanity
Sanity ships across every package at once, and the agent-facing surface moves fastest.
ESP-IDF
The 6.1 candidate arrives carrying the same notes the beta already shipped in June.
Auth0
Auth0 hands tenants a throttle on their own noisy apps
See all Manticore Search alternatives → · See all NSD alternatives →
Recent activity from Manticore Search and NSD
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoManticore SearchNEAR and proximity distances survive repeated JSON query fixup
- 1d agoManticore SearchInternal sort columns no longer leak into LEFT JOIN results
- 2d agoManticore SearchBinary API rejects malformed search counts before allocating
- 5d agoManticore SearchManticore 29.0 makes sharded tables operable and changes the SHARD_WRITE protocol ⚡
- 5d agoManticore Search29.0.2 bumps manticore-backup to 1.10.3 and Buddy to 4.4.1
- 7d agoManticore SearchSHOW TABLE SETTINGS now works on sharded tables
- 1mo agoNSDPrometheus metrics move zone from metric name to label
- 1mo agoNSDRelease candidate for 4.15.0 with identical notes
- 1mo agoNSDHeap overflow via crafted SVCB records patched
- 5mo agoNSDIXFR processing fix for collated add and delete records
- 5mo agoNSDRelease candidate for the 4.14.2 IXFR fix
- 5mo agoNSDMemory regression from the RDATA refactor closed
Frequently asked questions
What is the difference between Manticore Search and NSD?
They serve adjacent needs but don't currently overlap on shipped themes. Manticore Search is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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 Manticore Search better than NSD?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Manticore Search is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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 Manticore Search?
Top Manticore Search alternatives in DevOps are ranked by recent ship velocity. Browse the "Manticore Search alternatives" section above for the current picks, or visit /alternatives/manticoresearch for the full list with editorial commentary on each.
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.