← Back to home
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

FeatureManticore SearchTigris
SectorDevOpsDevOps
Velocity score6.35.0
Sparks · 30d10
Top themessearch engine, sharding, patch cadence, query correctnessobject-storage, immutability, agent-native, s3-compatibility
Last editorial update1d ago7d ago
WebsiteVisit →

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

Tigris still ships features inside essays, and the newest one is a recycle bin.

The feed is a blog, not a changelog, and each post is an engineering argument that happens to carry a product change. This window has three: a recycle bin for objects and buckets built on immutable storage so deletion in a geo-replicated active-active system stops meaning data loss, agent-native onboarding via tigris init --agent, and a CLI that migrates an entire bucket from any S3-compatible provider in one command. The rest are essays on SigV4, presigned URLs, and ClickHouse restore economics.

Read the full Tigris trajectory →

Manticore Search vs Tigris: 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.

T
Tigris
DEVOPS
5.0

Tigris still ships features inside essays, and the newest one is a recycle bin.

◆ Current state

The feed is a blog, not a changelog, and each post is an engineering argument that happens to carry a product change. This window has three: a recycle bin for objects and buckets built on immutable storage so deletion in a geo-replicated active-active system stops meaning data loss, agent-native onboarding via tigris init --agent, and a CLI that migrates an entire bucket from any S3-compatible provider in one command. The rest are essays on SigV4, presigned URLs, and ClickHouse restore economics.

◆ Where it's heading

Two arguments run underneath everything: object storage should be the durable state layer for agents, and S3 compatibility is a surface to be explained rather than merely claimed. The SigV4 and presigned-URL posts are the second argument in practice — publishing where the protocol is dangerous is a credibility play against the incumbent. The recycle bin extends the immutability story into a place immutable systems usually struggle, which is undoing a mistake.

◆ Prediction

Expect more posts that pair a protocol critique with the Tigris behavior that answers it; the egress-cost framing from the ClickHouse post is the one most likely to recur as a paid migration path.

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.

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.

  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. 5d 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. 8d agoTigrisExtending immutability: deletion without losing data
  8. 13d agoTigrisSigV4 authentication is surprisingly complicated
  9. 22d agoTigrisHumans don't install software themselves anymore, their agents do
  10. 1mo agoTigrisThe Most Expensive ClickHouse Query Is the Restore
  11. 1mo agoTigrisPresigned URLs are technically a security vuln
  12. 1mo agoTigrisMigrate your data with the Tigris CLI

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

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