GitHub
At Universe, GitHub folds Copilot into Enterprise seats and lets Copilot Fusion pick the model.
A side-by-side editorial comparison of Manticore Search and Meilisearch — release velocity, themes, recent moves, and the top alternatives to consider.
Manticore 31.0.7 undoes a 2x COUNT(DISTINCT) slowdown its own collation fix caused.
Manticore Search's 31.x tags so far are fixes rather than features. 31.0.3 and 31.0.4 were CI and packaging work; 31.0.7 restores string COUNT(DISTINCT) speed after the 29.18.5 collation fix made it 2x slower (1.1 s to 2.4 s on the logs10m benchmark) by calling tolower() per byte. A lookup table replaces the call without changing hash values, so secondary indexes and histograms stay compatible.
Meilisearch tightens sharding latency and index authorization in a flurry of maintenance releases.
Meilisearch is deep in active maintenance, shipping bug-fix point releases and a series of prototype branches targeting sharding performance. The v1.53.x line addresses search-result correctness (stop-word highlighting, exactness ranking edge cases) and a security hardening fix tying authorization checks to index opening. Alongside stable releases, the reuse-http-client prototype branch is testing a ~100ms-per-request latency reduction for users running clustered setups.
Manticore Search's 31.x tags so far are fixes rather than features. 31.0.3 and 31.0.4 were CI and packaging work; 31.0.7 restores string COUNT(DISTINCT) speed after the 29.18.5 collation fix made it 2x slower (1.1 s to 2.4 s on the logs10m benchmark) by calling tolower() per byte. A lookup table replaces the call without changing hash values, so secondary indexes and histograms stay compatible.
October has been correctness work on string handling (range filters, collation-aware COUNT(DISTINCT)) followed by fixing the performance cost of those fixes. The 31.x line still appears in the feed without notes on what features justified the major version.
Expect more 31.0.x patches in this vein. What new capability defines 31.x remains unclear from these entries.
Meilisearch is deep in active maintenance, shipping bug-fix point releases and a series of prototype branches targeting sharding performance. The v1.53.x line addresses search-result correctness (stop-word highlighting, exactness ranking edge cases) and a security hardening fix tying authorization checks to index opening. Alongside stable releases, the reuse-http-client prototype branch is testing a ~100ms-per-request latency reduction for users running clustered setups.
The team is working two tracks simultaneously: quality stabilization on the stable line and infrastructure-level optimizations on prototype branches for sharding. The addition of MEILI_EXPERIMENTAL_TASK_QUEUE_MAX_READERS suggests increasing attention to LMDB resource limits under high concurrent load—a pattern pointing toward larger deployments. Expect the HTTP client reuse optimization to land in a stable minor once the prototype cycle closes.
The next stable release will likely absorb the reuse-http-client prototype changes, delivering measurable latency improvement for multi-node deployments. If the crash-fix branch work uncovered a systemic allocator issue (mimalloc swap), expect a follow-on patch for stability.
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 Meilisearch.
At Universe, GitHub folds Copilot into Enterprise seats and lets Copilot Fusion pick the model.
CodeRabbit moves its review status to a GitHub check run and keeps Deep Scan coverage fresh.
Arrow Rust 60.1.0 ships, redacting Parquet encryption keys and adding read-ahead planning.
Zed 1.26 adds Pyrefly for Python and debugs WebAssembly from the JavaScript debugger.
Sanity's MCP server now advertises itself to agents through a server card and llms.txt.
Kubernetes moves conformance from the cluster to the workloads running on it.
See all Manticore Search alternatives → · See all Meilisearch alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — open-source, performance — within DevOps. Manticore Search and Meilisearch 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Manticore Search and Meilisearch 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.
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.
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.