OpenMetadata
OpenMetadata 2.0.8 widens Hex, Sigma and BigQuery coverage while 2.1 waits in release candidates.
A side-by-side editorial comparison of Count and Grafana Loki — release velocity, themes, recent moves, and the top alternatives to consider.
Count's agent now shows the chain of cells and assumptions behind every answer it gives.
Count is a data-canvas analytics tool organized around an AI agent. Its late-October release added Reasoning Chains, which link each claim and chart in an agent answer back to the cells, sources and assumptions behind it. Over the summer it rebuilt the agent with web data and auto layout, moved Python to a server sandbox with any PyPI package, and added longer agent conversations, a faster empty-canvas start and catalog views that stay populated while they refresh.
Loki 4.0 reaches RC3 and narrows S3 storage classes to Standard and Standard-IA.
Loki 4.0 is moving through release candidates. RC1's notes list the breaking changes: the V2 query engine unplugged, Simple Scalable Deployment targets and old /api/prom endpoints removed, protobuf as the default frontend encoding, and several deprecated settings and metrics dropped. RC2 removed every index backend but TSDB, and RC3 adds one more break, limiting S3 storage classes to STANDARD and STANDARD_IA, plus a compactor delete fix.
Count is a data-canvas analytics tool organized around an AI agent. Its late-October release added Reasoning Chains, which link each claim and chart in an agent answer back to the cells, sources and assumptions behind it. Over the summer it rebuilt the agent with web data and auto layout, moved Python to a server sandbox with any PyPI package, and added longer agent conversations, a faster empty-canvas start and catalog views that stay populated while they refresh.
Count is making the agent the main way to work in the canvas, then adding the checks that let people trust its output. Reasoning Chains and server-side Python with managed secrets point at analysis that can be audited and run on real data. Steady fix lists for agent edits show the agent is still being hardened.
Expect more ways to inspect and correct agent work, building on Reasoning Chains. The entries don't show whether chains will extend to Slack answers.
Loki 4.0 is moving through release candidates. RC1's notes list the breaking changes: the V2 query engine unplugged, Simple Scalable Deployment targets and old /api/prom endpoints removed, protobuf as the default frontend encoding, and several deprecated settings and metrics dropped. RC2 removed every index backend but TSDB, and RC3 adds one more break, limiting S3 storage classes to STANDARD and STANDARD_IA, plus a compactor delete fix.
Each candidate trims a bit more legacy surface, so 4.0 is a cleanup major that pushes installs onto TSDB and the microservices or single-binary layouts. The Operator had prepared this path since 0.11 and 0.12.
Expect a few more RCs with small breaking changes, then 4.0.0 GA and an Operator release that drops the removed schemas.
Other Analytics 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 Count or Grafana Loki.
OpenMetadata 2.0.8 widens Hex, Sigma and BigQuery coverage while 2.1 waits in release candidates.
Dovetail lets admins choose which connectors members can plug into the workspace.
Dagster drops Python 3.10 and lets agents run schedules and sensors through MCP.
OpenHouse adds time-zone-aware retention and per-database table caps.
Countly 25.03.59 defaults to Node 26, supports MongoDB 9 and tightens app scoping.
Kubecost cuts three 3.3.2 release candidates in two days, still without notes.
See all Count alternatives → · See all Grafana Loki alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Count and Grafana Loki 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. Count and Grafana Loki 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 Analytics products to evaluate alongside.
Top Count alternatives in Analytics are ranked by recent ship velocity. Browse the "Count alternatives" section above for the current picks, or visit /alternatives/count for the full list with editorial commentary on each.
Top Grafana Loki alternatives in Analytics are ranked by recent ship velocity. Browse the "Grafana Loki alternatives" section above for the current picks, or visit /alternatives/loki for the full list with editorial commentary on each.