Tigris
Tigris still ships features inside essays, and the newest one is a recycle bin.
A side-by-side editorial comparison of Manticore Search and Splunk — release velocity, themes, recent moves, and the top alternatives to consider.
Six releases in a week: one new capability, one revert, the rest corrective
Manticore is cutting point releases every day or two, and the last six are maintenance — a snippet-highlighting markup fix, a thread-stack crash case, a per-index optimize_cutoff correction that now also governs KNN, two Buddy version bumps, and a revert of UTF-8 table and field name support that was merged by mistake.
Splunk's changelog feed is mostly marketing pages and nav — actual release news is buried in the blog.
What surfaces from Splunk in this slice is marketing and documentation index content: Splunk Enterprise positioning, the InfoSec starter app, the Compatibility Matrix page, the home navigation, and a 'Latest Articles' index on the observability blog. The blog index does mention real product activity — OpenTelemetry eBPF Instrumentation in the Splunk Distribution of the OpenTelemetry Collector, OTLP log ingestion, ITSI Content Pack for Cisco Data Center Networking — but the substance lives behind those headlines, not in this feed.
Manticore is cutting point releases every day or two, and the last six are maintenance — a snippet-highlighting markup fix, a thread-stack crash case, a per-index optimize_cutoff correction that now also governs KNN, two Buddy version bumps, and a revert of UTF-8 table and field name support that was merged by mistake.
Cadence is high but the content is corrective. The only user-facing addition in this window arrives indirectly, as Unix socket support carried in by Buddy 4.4.0. The reverted UTF-8 identifier work is the one feature visible in flight, and the revert note says it landed before it was meant to rather than that it failed.
Expect UTF-8 table and field names to return in a later release once intentional, and the 28.9.x line to keep absorbing KNN and highlighting fixes at this pace.
What surfaces from Splunk in this slice is marketing and documentation index content: Splunk Enterprise positioning, the InfoSec starter app, the Compatibility Matrix page, the home navigation, and a 'Latest Articles' index on the observability blog. The blog index does mention real product activity — OpenTelemetry eBPF Instrumentation in the Splunk Distribution of the OpenTelemetry Collector, OTLP log ingestion, ITSI Content Pack for Cisco Data Center Networking — but the substance lives behind those headlines, not in this feed.
From this slice it's hard to read actual product trajectory. The breadcrumbs in the blog index point toward Splunk doubling down on OpenTelemetry as the ingestion surface (eBPF instrumentation, OTLP log ingest), broader Kubernetes monitoring coverage, and ITSI content packs for networking. Nothing here suggests a strategic shift; the work pattern is observability-feature breadth and OpenTelemetry alignment.
Until a release-notes channel feeds into this view, predictions are general. Based on the blog index, expect more OpenTelemetry-aligned ingestion improvements, additional ITSI content packs for major infrastructure categories, and continued AI-observability messaging tied to KubeCon EU 2026. A formal Splunk Enterprise release announcement is also likely soon given the Compatibility Matrix and release-notes pages being actively maintained.
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 Splunk.
Tigris still ships features inside essays, and the newest one is a recycle bin.
Workato just made itself the control plane for every MCP server in the building.
Four branches on a servicing drumbeat, with 10.0 taking the only real fixes.
Laravel runs two trains in lockstep, and 13.x is still where features land.
Two trains ship the same features minutes apart while v16 absorbs the CRM stack.
Weaviate is turning the vector database into an agent runtime with tunable search effort
See all Manticore Search alternatives → · See all Splunk alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Manticore Search is currently shipping more aggressively (velocity 5.0 vs 1.0), 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Manticore Search is currently shipping more aggressively (velocity 5.0 vs 1.0), 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.
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.
Top Splunk alternatives in DevOps are ranked by recent ship velocity. Browse the "Splunk alternatives" section above for the current picks, or visit /alternatives/splunk for the full list with editorial commentary on each.