Manticore Search
Manticore Search in active patch mode — German morphology improvements and distributed query crash fixes.
A side-by-side editorial comparison of Elasticsearch and Exoscale — release velocity, themes, recent moves, and the top alternatives to consider.
Elasticsearch patches multiple Kibana, Fleet Server, and APM vulnerabilities in a coordinated security drop.
The most recent visible output from Elastic is entirely security advisories — CVEs patched across Kibana (path traversal, authorization bypass, DoS), Fleet Server, Filebeat, and APM Server all published on the same day. This kind of dense advisory release typically follows a coordinated security audit rather than organic bug discovery. No feature releases appear in this window. Elastic continues shipping patches simultaneously across the 8.x and 9.x release lines.
Exoscale keeps SKS on the upstream release train while the platform play sits elsewhere
Exoscale's changelog interleaves three streams: managed Kubernetes tracking upstream, a marketplace and partner directory that grows most weeks, and the occasional new managed service. Kubernetes 1.37 is now selectable on SKS for new and existing clusters, with Metrics API, Pod Certificates and ClusterTrustBundles, and Node Declared Features all arriving Stable from upstream. Upgrades stay a customer decision — existing clusters are not moved automatically, and minor versions must be stepped through in sequence.
The most recent visible output from Elastic is entirely security advisories — CVEs patched across Kibana (path traversal, authorization bypass, DoS), Fleet Server, Filebeat, and APM Server all published on the same day. This kind of dense advisory release typically follows a coordinated security audit rather than organic bug discovery. No feature releases appear in this window. Elastic continues shipping patches simultaneously across the 8.x and 9.x release lines.
Maintaining parallel 8.x and 9.x release branches means every security fix ships across multiple version trees, which signals that enterprise customers unable to migrate quickly are still a first-class consideration. The vulnerability classes concentrated in Fleet and Kibana's ML and Osquery features — path traversal, authorization scope gaps, unbounded allocation — suggest security audit attention has shifted toward the orchestration and observability layers rather than the core search engine. Whether this clears the backlog ahead of a feature release is not clear from entries alone.
A feature-bearing release is likely overdue given the all-maintenance cadence visible here. If Elastic is clearing the security backlog before a major announcement, a 9.6 or named feature release could follow. Without feature entries to triangulate on, the prediction is uncertain.
Exoscale's changelog interleaves three streams: managed Kubernetes tracking upstream, a marketplace and partner directory that grows most weeks, and the occasional new managed service. Kubernetes 1.37 is now selectable on SKS for new and existing clusters, with Metrics API, Pod Certificates and ClusterTrustBundles, and Node Declared Features all arriving Stable from upstream. Upgrades stay a customer decision — existing clusters are not moved automatically, and minor versions must be stepped through in sequence.
The SKS entries read as a European provider keeping pace rather than differentiating: version availability, container registry mirroring for Karpenter nodes, CPU Manager policies. Where Exoscale is actually moving is in what runs beside the clusters — Managed ClickHouse in August put an analytics engine on the same estate as the object storage — while the partner and marketplace posts fill the cadence between. Expect the Kubernetes entries to keep reporting upstream rather than making an argument of their own.
The next SKS entries are likely to be operational — node pool and upgrade tooling around 1.37 — with any directional move coming from another managed service rather than from the Kubernetes track.
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 Elasticsearch or Exoscale.
Manticore Search in active patch mode — German morphology improvements and distributed query crash fixes.
Rollbar's Resolve agent reads your codebase and opens a fix PR automatically — error tracker becomes error fixer.
Workato Genies now run 30-minute tasks and deploy anywhere via Headless API — enterprise autonomous agents at scale.
Weaviate is chasing retrieval quality past the vector, into documents people actually store
arrow-rs backports correctness fixes to a maintenance branch, not just the next minor
ActiveMQ's first 6.3-only release ends the all-branches-at-once pattern and makes 6.3 the live line.
See all Elasticsearch alternatives → · See all Exoscale alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Elasticsearch and Exoscale are shipping at a similar cadence (velocity 6.3 vs 6.3, 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Elasticsearch and Exoscale are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other DevOps products to evaluate alongside.
Top Elasticsearch alternatives in DevOps are ranked by recent ship velocity. Browse the "Elasticsearch alternatives" section above for the current picks, or visit /alternatives/elastic for the full list with editorial commentary on each.
Top Exoscale alternatives in DevOps are ranked by recent ship velocity. Browse the "Exoscale alternatives" section above for the current picks, or visit /alternatives/exoscale for the full list with editorial commentary on each.