Slurm
Two supported branches, both absorbing the aftershocks of the 26.05 identity change.
A side-by-side editorial comparison of Elasticsearch and TypeDB — release velocity, themes, recent moves, and the top alternatives to consider.
Agent Builder, Elastic's newest surface, is where most of this month's Kibana CVEs live.
The visible feed window is one coordinated disclosure batch: ten Kibana advisories published within a minute of each other on August 13, spanning the 8.19, 9.3, 9.4 and 9.5 branches. Four of the six most recent concern Agent Builder — private agents readable and tamperable by non-owners, an A2A JSON-RPC endpoint that derives a conversation id from user-supplied input, and a missing cross-feature privilege check. The remainder cover Fleet issuing over-scoped Elastic Agent API keys and an Elastic Defend endpoint-event disclosure via field-value suggestions.
Query caching and type renaming land, then three patches to make the schema engine hold.
TypeDB is iterating fast on the 3.12 line — four releases in five weeks. The substantive work arrived in 3.12.0 and 3.12.2: pre-created UUIDs for users in distributed deployments, exposed RocksDB memory tuning, a three-stage parse/translate/compile query cache, and the ability to rename entity, relation and attribute types. The two releases since have been fixes against the schema engine, most recently import rejections caused by coincidental combinations of inherited constraints.
The visible feed window is one coordinated disclosure batch: ten Kibana advisories published within a minute of each other on August 13, spanning the 8.19, 9.3, 9.4 and 9.5 branches. Four of the six most recent concern Agent Builder — private agents readable and tamperable by non-owners, an A2A JSON-RPC endpoint that derives a conversation id from user-supplied input, and a missing cross-feature privilege check. The remainder cover Fleet issuing over-scoped Elastic Agent API keys and an Elastic Defend endpoint-event disclosure via field-value suggestions.
Authorization is the single recurring failure mode here — every one of these is a caller-identity or privilege-check mistake, not memory safety or injection. That is the predictable cost of extending a permissions model built for dashboards and saved searches to a layer that acts on a user's behalf. Fixes are shipping inside ordinary patch releases (9.4.5, 9.5.1) rather than as a dedicated hardening effort.
Expect further Agent Builder advisories as that surface widens, and pressure to consolidate its ownership and privilege checks into one enforcement path instead of patching endpoint by endpoint.
TypeDB is iterating fast on the 3.12 line — four releases in five weeks. The substantive work arrived in 3.12.0 and 3.12.2: pre-created UUIDs for users in distributed deployments, exposed RocksDB memory tuning, a three-stage parse/translate/compile query cache, and the ability to rename entity, relation and attribute types. The two releases since have been fixes against the schema engine, most recently import rejections caused by coincidental combinations of inherited constraints.
Two threads are running at once. One is performance and operability — splitting the query cache so string-identical queries skip re-parsing, and giving operators shared memory limits across databases. The other is schema mutability: renaming types and relaxing schemas are newer capabilities, and the bug reports clustering around inherited constraints, ownership specializations and independent attributes suggest that surface is still settling. The 3.11.5 driver cutoff shows the project is willing to break compatibility to move.
Expect continued patch releases against schema relaxation and import paths before the next minor; the inherited-constraint fixes have arrived in successive versions rather than all at once.
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 TypeDB.
Two supported branches, both absorbing the aftershocks of the 26.05 identity change.
A week of reverts and prototype tags, with tuning knobs standing in for features.
Auth0 is replacing its legacy configuration surfaces one at a time, and shipping NIST defaults to new tenants only.
HashiCorp says provenance is the moat, and Packer is the first product to actually ship it.
GitHub is standardising the agent layer it doesn't own, while the model roster churns underneath.
SvelteKit 3 reaches release candidate: breaking changes are frozen and the migration path is open
See all Elasticsearch alternatives → · See all TypeDB alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Elasticsearch is currently shipping more aggressively (velocity 6.3 vs 5.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. Elasticsearch is currently shipping more aggressively (velocity 6.3 vs 5.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 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 TypeDB alternatives in DevOps are ranked by recent ship velocity. Browse the "TypeDB alternatives" section above for the current picks, or visit /alternatives/typedb for the full list with editorial commentary on each.