PostHog
PostHog is filling in Logs and the mobile SDKs while quietly growing a support product.
A side-by-side editorial comparison of OpenObserve and Holistics — release velocity, themes, recent moves, and the top alternatives to consider.
OpenObserve is running a stabilization train on 0.91 while 0.92 gathers features in RC
Two branches are moving at once. The 0.91 line has taken four patch releases since the start of July, each carrying two or three fixes — memtable rotation, RBAC migration for metric stream names, PagerDuty integration bugs, an anomaly-detection threshold that no longer forces a retrain. In parallel, 0.92 is accumulating in release candidates: agent-level filters, an option to disable default index fields via ZO_FEATURE_DEFAULT_INDEX_FIELDS_ENABLED, and parallel zstd compression. The substantive 0.91.0 release itself — Super Org multi-tenancy, org-level ingestion tokens, and a round of Tantivy search performance work including a footer cache and bloom-filter pruning — sits just outside the recent window.
Holistics keeps converting GUI-only BI objects into code, one class at a time.
The recent window moved custom charts into AML so they can be defined as code, built through a GUI and previewed against real data, and gave every file — dashboards, models, datasets — its own version timeline with per-file restore that does not revert anyone else's work. Smaller quality-of-life work landed alongside: theme-level color palettes, date-range presets and typed shorthands, chart suggestions in Explore, and custom currency and unit formats.
Two branches are moving at once. The 0.91 line has taken four patch releases since the start of July, each carrying two or three fixes — memtable rotation, RBAC migration for metric stream names, PagerDuty integration bugs, an anomaly-detection threshold that no longer forces a retrain. In parallel, 0.92 is accumulating in release candidates: agent-level filters, an option to disable default index fields via ZO_FEATURE_DEFAULT_INDEX_FIELDS_ENABLED, and parallel zstd compression. The substantive 0.91.0 release itself — Super Org multi-tenancy, org-level ingestion tokens, and a round of Tantivy search performance work including a footer cache and bloom-filter pruning — sits just outside the recent window.
The shape here is a project consolidating after a large release rather than chasing new surface area. The 0.92 RC contents point at operator control over ingest and index cost — letting users switch off default index fields is a storage-and-write-amplification lever, and parallel compression is the same concern from the CPU side. Agent-level filters suggest the collector-side story is being tightened too.
A 0.92.0 general release is the near-term move, carrying the index-field control and compression work, with the 0.91.x patch train tapering once it lands. Whether multi-tenancy from 0.91 gets follow-on quota or billing controls is not yet visible in the RC contents.
The recent window moved custom charts into AML so they can be defined as code, built through a GUI and previewed against real data, and gave every file — dashboards, models, datasets — its own version timeline with per-file restore that does not revert anyone else's work. Smaller quality-of-life work landed alongside: theme-level color palettes, date-range presets and typed shorthands, chart suggestions in Explore, and custom currency and unit formats.
Holistics is steadily giving GUI concepts an AML representation while keeping a visual path to the same result, and file history extends a software-engineering model to objects that were previously edited in place. The last several releases are polish on top of that spine rather than new capability, which suggests the code-first migration sets the agenda and the surface work fills in behind it.
Expect more object types to gain AML definitions and version timelines; the cadence so far has been roughly one object class per release cycle.
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 OpenObserve or Holistics.
PostHog is filling in Logs and the mobile SDKs while quietly growing a support product.
Mixpanel is becoming a component other tools provision, not a destination users visit.
Polars is teaching its engine to spill, stream, and read the lakehouse.
Plotly is turning its cloud into a metered compute platform with an enterprise on-ramp.
With Interfaces, NocoDB stops being a database view and starts being an app builder.
Neo4j is making the graph legible to agents and comfortable for humans at the same time.
See all OpenObserve alternatives → · See all Holistics alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. OpenObserve and Holistics are shipping at a similar cadence (velocity 5.0 vs 5.0, 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. OpenObserve and Holistics are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top OpenObserve alternatives in Analytics are ranked by recent ship velocity. Browse the "OpenObserve alternatives" section above for the current picks, or visit /alternatives/openobserve for the full list with editorial commentary on each.
Top Holistics alternatives in Analytics are ranked by recent ship velocity. Browse the "Holistics alternatives" section above for the current picks, or visit /alternatives/holistics for the full list with editorial commentary on each.