FusionAuth
FusionAuth adds RFC 8707 resource-scoped tokens while most recent changelogs surface only upgrade boilerplate.
Comparison · DevOps
Meilisearch vs NSD
A side-by-side editorial comparison of Meilisearch and NSD — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:open-sourceself-hosted
Meilisearch vs NSD: at a glance
What is Meilisearch?
Meilisearch is trimming ~100ms sharding latency in prototype while shipping task-queue controls in stable.
Meilisearch is running two active prototype branches in parallel: the reuse-http-client track targets sharded deployments by reusing the index-scheduler's HTTP client, cutting around 100ms per proxied task. The stable v1.53.1 released independently, shipping a configurable cap on simultaneous LMDB read transactions via MEILI_EXPERIMENTAL_TASK_QUEUE_MAX_READERS — a tuning knob for operators under heavy concurrent load. The 1.52.3 stable patched a crash by reverting a search speed optimization introduced in an earlier release.
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.
Meilisearch vs NSD: editorial side-by-side
Meilisearch
5.0DEVOPS
Meilisearch is trimming ~100ms sharding latency in prototype while shipping task-queue controls in stable.
◆ Current state
Meilisearch is running two active prototype branches in parallel: the reuse-http-client track targets sharded deployments by reusing the index-scheduler's HTTP client, cutting around 100ms per proxied task. The stable v1.53.1 released independently, shipping a configurable cap on simultaneous LMDB read transactions via MEILI_EXPERIMENTAL_TASK_QUEUE_MAX_READERS — a tuning knob for operators under heavy concurrent load. The 1.52.3 stable patched a crash by reverting a search speed optimization introduced in an earlier release.
◆ Where it's heading
Sharding is becoming a first-class operational concern. The prototype branch pattern (public experimental tags before stable merges) is a deliberate quality gate: riskier changes land in a named prototype where the community can validate them before production inclusion. The operator-facing controls shipped in 1.53.1 — task queue reader cap, mini-dashboard bump — point toward a secondary track of infrastructure tuning features separate from core search capability.
◆ Prediction
The reuse-http-client prototype will stabilize into a stable release once the batch of error-context fixes (rc.1 through rc.3) settle; the 100ms-per-task gain is a compelling merge for sharded clusters. The task queue reader cap env var suggests ongoing work to make LMDB concurrency more operator-tunable.
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.
Alternatives to Meilisearch 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 Meilisearch or NSD.
Sanity
Sanity centralizes its AI context layer in a dedicated dashboard app while running the most active MCP release sprint yet.
Dapr
Dapr is hardening workflow reliability across three concurrent release branches, with actor hot-reload as the headliner.
Slurm
Slurm coordinated a 7-CVE security drop across three active branches, including a privilege escalation and SQL injection.
Scalingo
Scalingo phases out swap memory for application containers, shifting OOM behavior for new and restarted apps starting September 2026.
Aiven
Aiven completes its three-cloud BYOC story with self-service Azure, while adding AI agent governance and API secrets redaction.
See all Meilisearch alternatives → · See all NSD alternatives →
Recent activity from Meilisearch and NSD
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 9h agoMeilisearchprototype-v1.50.0-reuse-http-client.3
- 9h agoMeilisearchAdd error context for CorruptedTaskQueue in HTTP client reuse prototype
- 14h agoNSDNSD 4.15.2 released
- 1d agoMeilisearchAllow deletion of non-deserializable enqueued tasks
- 1d agoMeilisearchPrototype: reuse HTTP client when proxying tasks (~100ms savings for sharded deployments)
- 8d agoNSDNSD 4.15.2 release candidate
- 8d agoNSDNSD 4.15.1 security release: four CVEs fixed
- 9d agoMeilisearchprototype-v1.52.3-fix-crashes.6
- 21d agoMeilisearch🖇️ v1.53.1
- 1mo 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 Meilisearch and NSD?
Both compete on the same themes — open-source, self-hosted — within DevOps. Meilisearch and NSD are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is Meilisearch better than NSD?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Meilisearch and NSD are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other DevOps products to evaluate alongside.
What are the best alternatives to Meilisearch?
Top Meilisearch alternatives in DevOps are ranked by recent ship velocity. Browse the "Meilisearch alternatives" section above for the current picks, or visit /alternatives/meilisearch 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.