GitHub
At Universe, GitHub folds Copilot into Enterprise seats and lets Copilot Fusion pick the model.
Comparison · DevOps
Manticore Search vs Tigris
A side-by-side editorial comparison of Manticore Search and Tigris — release velocity, themes, recent moves, and the top alternatives to consider.
Manticore Search vs Tigris: at a glance
| Feature | Manticore Search | Tigris |
|---|---|---|
| Sector | DevOps | DevOps |
| Velocity score | 5.0 | 5.0 |
| Sparks · 30d | 0 | 0 |
| Top themes | search-engine, open-source, sql, performance | object-storage, foundationdb, geo-replication, s3-compatibility |
| Last editorial update | 2d ago | 2mo ago |
| Website | Visit → | — |
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.
What is Tigris?
Tigris keeps publishing its architecture, and the newest post opens up the storage engine itself.
This feed is Tigris's engineering blog, and it alternates between protocol critique and descriptions of how the product answers it. The most recent post opens the internals: how Tigris composes ACID metadata, global placement, caching, replication, and background work on FoundationDB into a multi-region object store. Before it came the Recycle Bin — deletion of objects and buckets on top of immutable storage in an active-active geo-replicated database — plus two posts dissecting SigV4 and presigned URLs, and one on agent-native onboarding through tigris init --agent.
Manticore Search vs Tigris: editorial side-by-side
Manticore Search
5.0DEVOPS
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.
Tigris
5.0DEVOPS
Tigris keeps publishing its architecture, and the newest post opens up the storage engine itself.
◆ Current state
This feed is Tigris's engineering blog, and it alternates between protocol critique and descriptions of how the product answers it. The most recent post opens the internals: how Tigris composes ACID metadata, global placement, caching, replication, and background work on FoundationDB into a multi-region object store. Before it came the Recycle Bin — deletion of objects and buckets on top of immutable storage in an active-active geo-replicated database — plus two posts dissecting SigV4 and presigned URLs, and one on agent-native onboarding through tigris init --agent.
◆ Where it's heading
The writing is doing product work. Each protocol post establishes a problem — SigV4's canonicalization and clock skew, presigned URLs as deliberate replay attacks, S3 egress pricing on ClickHouse restores — and positions Tigris behavior as the answer, which makes the blog a migration funnel rather than a changelog. The architecture post is a different move: publishing the FoundationDB composition is a credibility play aimed at buyers who need to believe a newer object store can hold multi-region data.
◆ Prediction
Expect the protocol-critique-then-Tigris-answer format to continue, with the egress-cost framing recurring as the clearest paid migration path. Feature announcements will likely stay embedded in essays rather than appearing as release notes.
Alternatives to Manticore Search and Tigris
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 Tigris.
CodeRabbit
CodeRabbit moves its review status to a GitHub check run and keeps Deep Scan coverage fresh.
Apache Arrow Rust
Arrow Rust 60.1.0 ships, redacting Parquet encryption keys and adding read-ahead planning.
Zed
Zed 1.26 adds Pyrefly for Python and debugs WebAssembly from the JavaScript debugger.
Sanity
Sanity's MCP server now advertises itself to agents through a server card and llms.txt.
Kubernetes
Kubernetes moves conformance from the cluster to the workloads running on it.
See all Manticore Search alternatives → · See all Tigris alternatives →
Recent activity from Manticore Search and Tigris
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3d agoManticore Search31.0.7: string COUNT(DISTINCT) 2x slowdown fixed
- 6d agoManticore Search31.0.4: CI fix for bundled Debian dependencies
- 6d agoManticore Search31.0.3: Test Kit pinned to Executor 1.4.6
- 8d agoManticore Search29.18.7: Manticore Buddy sidecar bumped to 4.4.8
- 9d agoManticore Search29.18.6: crash dumps now name the operation and table
- 9d agoManticore SearchFix: COUNT(DISTINCT) on strings now respects session collation
- 2mo agoTigrisBuilding a global object store on FoundationDB
- 2mo agoTigrisExtending immutability: deletion without losing data
- 2mo agoTigrisSigV4 authentication is surprisingly complicated
- 3mo agoTigrisHumans don't install software themselves anymore, their agents do
- 3mo agoTigrisThe Most Expensive ClickHouse Query Is the Restore
- 3mo agoTigrisPresigned URLs are technically a security vuln
Frequently asked questions
What is the difference between Manticore Search and Tigris?
They serve adjacent needs but don't currently overlap on shipped themes. Manticore Search and Tigris 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.
Is Manticore Search better than Tigris?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Manticore Search and Tigris 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.
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 Tigris?
Top Tigris alternatives in DevOps are ranked by recent ship velocity. Browse the "Tigris alternatives" section above for the current picks, or visit /alternatives/tigris for the full list with editorial commentary on each.