← Back to home
Comparison · DevOps

Manticore Search vs SimpleSAMLphp

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

Manticore Search vs SimpleSAMLphp: at a glance

FeatureManticore SearchSimpleSAMLphp
SectorDevOpsDevOps
Velocity score6.35.0
Sparks · 30d10
Top themessearch engine, sharding, patch cadence, query correctnesssaml, identity, security-releases, maintenance
Last editorial update23h ago8d ago
WebsiteVisit →Visit →

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 →

What is SimpleSAMLphp?

Two maintenance branches, patched in lockstep, with release notes that say nothing but a checksum.

SimpleSAMLphp is running parallel 2.4 and 2.5 maintenance branches and patching both on the same day whenever a fix lands. The August releases are a coordinated security drop across the 2.5 line plus a 2.4 bugfix a day earlier. Release bodies carry no changelog text at all — just a download link, upgrade-notes pointer, and SHA256 checksums, so the feed tells operators when to patch but never what changed.

Read the full SimpleSAMLphp trajectory →

Manticore Search vs SimpleSAMLphp: editorial side-by-side

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.

S5.0

Two maintenance branches, patched in lockstep, with release notes that say nothing but a checksum.

◆ Current state

SimpleSAMLphp is running parallel 2.4 and 2.5 maintenance branches and patching both on the same day whenever a fix lands. The August releases are a coordinated security drop across the 2.5 line plus a 2.4 bugfix a day earlier. Release bodies carry no changelog text at all — just a download link, upgrade-notes pointer, and SHA256 checksums, so the feed tells operators when to patch but never what changed.

◆ Where it's heading

This is pure maintenance cadence, not product development. The pattern across the last ten releases is consistent: security issues get simultaneous twin tags on both supported branches, everything else lands as branch-local bugfix points. The only release in the window that documented its own content was v2.4.6/v2.5.1 in May, which listed three GHSA advisories.

◆ Prediction

Expect the next tags to continue the twin-branch pattern — a paired 2.4.x and 2.5.x whenever an advisory lands, with content again deferred to the external changelog.

Alternatives to Manticore Search and SimpleSAMLphp

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 SimpleSAMLphp.

See all Manticore Search alternatives → · See all SimpleSAMLphp alternatives →

Recent activity from Manticore Search and SimpleSAMLphp

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. 1d 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. 6d agoManticore SearchSHOW TABLE SETTINGS now works on sharded tables
  7. 8d agoSimpleSAMLphpSecurity release on the 2.5 branch (re-tagged)
  8. 9d agoSimpleSAMLphpSecurity release on the 2.5 branch
  9. 9d agoSimpleSAMLphpBugfix release on the 2.4 maintenance branch
  10. 1mo agoSimpleSAMLphpBugfix release on the 2.4 maintenance branch
  11. 2mo agoSimpleSAMLphpBugfix release on the 2.5 branch
  12. 2mo agoSimpleSAMLphpBugfix release on the 2.4 maintenance branch

Frequently asked questions

What is the difference between Manticore Search and SimpleSAMLphp?

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 Manticore Search better than SimpleSAMLphp?

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 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 SimpleSAMLphp?

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