← Back to home
Comparison · DevOps

Grav vs Manticore Search

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

Grav vs Manticore Search: at a glance

FeatureGravManticore Search
SectorDevOpsDevOps
Velocity score2.55.0
Sparks · 30d00
Top themescms, flat-file, php, security-fixessearch-engine, open-source, sql, performance
Last editorial update2h ago2h ago
WebsiteVisit →Visit →

What is Grav?

Grav backports a Clockwork profiler security fix from 2.1.7 to its 1.7 line.

Grav's only entry in the feed is 1.7.53.6, a patch to the legacy 1.7 branch. It backports a Grav 2.1.7 security fix so Clockwork profiler data requires a configured debugger.token, even for requests arriving from localhost through a same-server reverse proxy. It also keeps accented letters intact in title-derived slugs on PHP 7.3 to 8.1 with single-byte locales.

Read the full Grav trajectory →

What is Manticore Search?

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.

Read the full Manticore Search trajectory →

Grav vs Manticore Search: editorial side-by-side

G
Grav
DEVOPS
2.5

Grav backports a Clockwork profiler security fix from 2.1.7 to its 1.7 line.

◆ Current state

Grav's only entry in the feed is 1.7.53.6, a patch to the legacy 1.7 branch. It backports a Grav 2.1.7 security fix so Clockwork profiler data requires a configured debugger.token, even for requests arriving from localhost through a same-server reverse proxy. It also keeps accented letters intact in title-derived slugs on PHP 7.3 to 8.1 with single-byte locales.

◆ Where it's heading

The fix originates on Grav 2.x and is carried back to 1.7, so the project is maintaining two lines, with 1.7 receiving security and compatibility patches for older PHP versions. With a single entry, the cadence on either branch isn't visible yet.

◆ Prediction

Expect further 1.7.53.x patches that mirror security fixes from the 2.x line. The entries don't show how long 1.7 support continues.

M5.0

Manticore 31.0.7 undoes a 2x COUNT(DISTINCT) slowdown its own collation fix caused.

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

Expect more 31.0.x patches in this vein. What new capability defines 31.x remains unclear from these entries.

Alternatives to Grav 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 Grav or Manticore Search.

See all Grav alternatives → · See all Manticore Search alternatives →

Recent activity from Grav and Manticore Search

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

  1. 13h agoManticore Search31.0.7: string COUNT(DISTINCT) 2x slowdown fixed
  2. 3d agoGravGrav 1.7.53.6: profiler token now required, slug encoding fix
  3. 3d agoManticore Search31.0.4: CI fix for bundled Debian dependencies
  4. 3d agoManticore Search31.0.3: Test Kit pinned to Executor 1.4.6
  5. 6d agoManticore Search29.18.7: Manticore Buddy sidecar bumped to 4.4.8
  6. 6d agoManticore Search29.18.6: crash dumps now name the operation and table
  7. 7d agoManticore SearchFix: COUNT(DISTINCT) on strings now respects session collation

Frequently asked questions

What is the difference between Grav and Manticore Search?

They serve adjacent needs but don't currently overlap on shipped themes. Manticore Search is currently shipping more aggressively (velocity 5.0 vs 2.5), 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 Grav 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 5.0 vs 2.5), 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 Grav?

Top Grav alternatives in DevOps are ranked by recent ship velocity. Browse the "Grav alternatives" section above for the current picks, or visit /alternatives/grav 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.