← Back to home
Comparison · DevOps

Groonga vs Manticore Search

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

Groonga vs Manticore Search: at a glance

FeatureGroongaManticore Search
SectorDevOpsDevOps
Velocity score5.06.3
Sparks · 30d01
Top themesfull-text-search, embeddings, vector-search, query-functionssearch engine, sharding, patch cadence, query correctness
Last editorial update9d ago1d ago
WebsiteVisit →Visit →

What is Groonga?

A veteran full-text engine quietly growing embedding functions alongside its string toolkit.

Groonga ships small, precise releases roughly monthly, each documenting changes with runnable examples and crediting the reporter by name. The 16.0 line opened in February 2026 with an annual major release that deliberately carried no backward-incompatible changes. Recent work splits between conventional search functions — a new string_truncate(), vector support in between() — and a language model path where language_model_vectorize() consumes GGUF models from HuggingFace and TokenLanguageModelKNN handles query and passage prefixes. Contributor counts per release run to a handful of people.

Read the full Groonga trajectory →

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.

Read the full Manticore Search trajectory →

Groonga vs Manticore Search: editorial side-by-side

G
Groonga
DEVOPS
5.0

A veteran full-text engine quietly growing embedding functions alongside its string toolkit.

◆ Current state

Groonga ships small, precise releases roughly monthly, each documenting changes with runnable examples and crediting the reporter by name. The 16.0 line opened in February 2026 with an annual major release that deliberately carried no backward-incompatible changes. Recent work splits between conventional search functions — a new string_truncate(), vector support in between() — and a language model path where language_model_vectorize() consumes GGUF models from HuggingFace and TokenLanguageModelKNN handles query and passage prefixes. Contributor counts per release run to a handful of people.

◆ Where it's heading

The embedding functions are the notable thread. A search engine of this vintage adding model-backed vectorization as ordinary functions, callable from the same query language as everything else, is positioning for hybrid retrieval without a separate vector store in the stack. The rest of the cadence is characteristic of the project: careful compatibility work, Windows packaging problems chased across multiple releases, and build-system fixes contributed by downstream packagers.

◆ Prediction

Expect indexing support for the vector cases that currently work without an index — between() on vectors is explicitly flagged as unindexed — and further options on the language model functions. The project's no-breaking-changes stance on major releases suggests continuity rather than a rearchitecture.

M6.3

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.

Alternatives to Groonga and Manticore Search

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 Groonga or Manticore Search.

See all Groonga alternatives → · See all Manticore Search alternatives →

Recent activity from Groonga and Manticore Search

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

  1. 1d agoManticore SearchNEAR and proximity distances survive repeated JSON query fixup
  2. 1d agoManticore SearchInternal sort columns no longer leak into LEFT JOIN results
  3. 2d agoManticore SearchBinary API rejects malformed search counts before allocating
  4. 4d agoManticore SearchManticore 29.0 makes sharded tables operable and changes the SHARD_WRITE protocol
  5. 5d agoManticore Search29.0.2 bumps manticore-backup to 1.10.3 and Buddy to 4.4.1
  6. 7d agoManticore SearchSHOW TABLE SETTINGS now works on sharded tables
  7. 11d agoGroongaNew string_truncate() function with omission-mark handling
  8. 1mo agoGroongabetween() accepts vector values, though without index support
  9. 2mo agoGroongaSecond attempt at the missing Windows runtime DLL
  10. 3mo agoGroongaMissing Windows runtime DLL restored to the archive
  11. 3mo agoGroongaUbuntu 26.04 support and an ODR fix that unblocks LTO builds
  12. 4mo agoGroongalanguage_model_vectorize() gains a prefix option

Frequently asked questions

What is the difference between Groonga and Manticore Search?

They serve adjacent needs but don't currently overlap on shipped themes. Manticore Search is currently shipping more aggressively (velocity 6.3 vs 5.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 Groonga better than Manticore Search?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Manticore Search is currently shipping more aggressively (velocity 6.3 vs 5.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 Groonga?

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

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.