SimpleSAMLphp
Two maintenance branches, patched in lockstep, with release notes that say nothing but a checksum.
Comparison · DevOps
Manticore Search vs Meilisearch
A side-by-side editorial comparison of Manticore Search and Meilisearch — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:search-engine
Manticore Search vs Meilisearch: at a glance
What is Manticore Search?
Manticore ships UUID document IDs, then spends a week reverting and patching around auth.
The substantive release in this window is 28.6.6, which added UUID document IDs for real-time tables — including generated IDs, equality and IN filters, and UUID-keyed REPLACE, UPDATE, and DELETE — plus an ordered, limited GROUP_CONCAT. Since then the feed is maintenance at commit granularity: two Buddy dependency bumps, a KNN optimize-cutoff config fix, a backup version bump, and a revert of UTF-8 table and field name support that was merged by mistake. A separate patch restored USER() parsing that broke when authentication was introduced.
What is Meilisearch?
Meilisearch shipped 1.52, then spent the same day reverting most of it.
Four releases landed on a single day. Both of 1.52.0's headline items — experimental SSE routes for tasks and batches, and an O(1) rewrite of document formatting — were reverted within a week, in 1.52.2 and 1.52.3. Meanwhile 1.53.0 went out the same day with sharding for foreign filters and new index size statistics. The additions that have actually held are in query capability: dynamic search rules gained filter-based activation conditions in 1.51.0.
Manticore Search vs Meilisearch: editorial side-by-side
Manticore Search
5.0DEVOPS
Manticore ships UUID document IDs, then spends a week reverting and patching around auth.
◆ Current state
The substantive release in this window is 28.6.6, which added UUID document IDs for real-time tables — including generated IDs, equality and IN filters, and UUID-keyed REPLACE, UPDATE, and DELETE — plus an ordered, limited GROUP_CONCAT. Since then the feed is maintenance at commit granularity: two Buddy dependency bumps, a KNN optimize-cutoff config fix, a backup version bump, and a revert of UTF-8 table and field name support that was merged by mistake. A separate patch restored USER() parsing that broke when authentication was introduced.
◆ Where it's heading
Two threads are visible. The feature thread is loosening Manticore's assumptions about document identity and result shaping, which matters for systems ingesting from sources that already have their own keys. The maintenance thread is the cost of the recently added authentication layer and the Buddy sidecar — USER() parsing, Unix socket support, config precedence for cutoffs — the kind of follow-on work that appears after a subsystem lands and starts colliding with existing SQL surface.
◆ Prediction
UTF-8 table and field names are likely to return deliberately, since the revert was explicitly an accidental merge rather than a rejection of the feature. Expect further Buddy version bumps to carry the user-visible changes, as they have twice in this window.
Meilisearch
6.3DEVOPS
Meilisearch shipped 1.52, then spent the same day reverting most of it.
◆ Current state
Four releases landed on a single day. Both of 1.52.0's headline items — experimental SSE routes for tasks and batches, and an O(1) rewrite of document formatting — were reverted within a week, in 1.52.2 and 1.52.3. Meanwhile 1.53.0 went out the same day with sharding for foreign filters and new index size statistics. The additions that have actually held are in query capability: dynamic search rules gained filter-based activation conditions in 1.51.0.
◆ Where it's heading
Engine work is pushing along two axes — distributed operation, where foreign filters can now resolve documents across the network and the retrieval limit rose from 100 to 1000, and search-time programmability, where rules can activate on facet filters and pin results. The revert pattern is the other signal: push-based task streaming and the formatting optimization both went out before they were solid, which suggests the release train is running ahead of validation.
◆ Prediction
The reverted SSE streaming routes and the formatting optimization are the obvious candidates to return in a later release once their underlying issues are resolved — neither was withdrawn for lack of intent.
Alternatives to Manticore Search and Meilisearch
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.
Auth0
Auth0 is rebuilding identity around actors that operate on someone else's behalf.
Zeebe
Camunda's 8.10 alpha threads a business ID through every layer of the orchestration stack.
Gravity Forms
Gravity Forms shipped 3.0 with accessibility on by default, then went back to add-on maintenance.
GitHub
GitHub is building the accounting layer for its agent platform, not just more agents.
GravityView
Unions let one View stack entries from many forms — no shared field, no code.
See all Manticore Search alternatives → · See all Meilisearch alternatives →
Recent activity from Manticore Search and Meilisearch
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 14h agoMeilisearchSearch formatting speedup from 1.52.0 reverted
- 15h agoMeilisearchExperimental task and batch SSE routes reverted
- 18h agoMeilisearchHealth route checks made blocking, search traces removed
- 20h agoMeilisearchForeign filters gain sharding; index size exposed in stats
- 1d agoManticore Search28.9.1: fix: more sync optimize_cutoff_KNN
- 3d agoManticore SearchBuddy 4.4.0 brings Unix socket support
- 4d agoManticore Search28.8.1: Revert "feat: support UTF-8 table and field names (#4772)"
- 4d agoManticore Search28.8.0: Bump buddy version from 4.2.0 to 4.3.0 (#4778)
- 7d agoMeilisearchPush-based task streaming and faster result formatting
- 10d agoManticore SearchUUID document IDs and ordered GROUP_CONCAT land in 28.6.6
- 11d agoManticore Search28.6.6: Allow 'USER' to be function
- 14d agoMeilisearchDynamic search rules can activate on facet filter conditions
Frequently asked questions
What is the difference between Manticore Search and Meilisearch?
Both compete on the same themes — search-engine — within DevOps. Meilisearch is currently shipping more aggressively (velocity 6.3 vs 5.0), with 0 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 Meilisearch?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Meilisearch is currently shipping more aggressively (velocity 6.3 vs 5.0), with 0 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 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.