Countly
Countly is running two release lines on autopilot while quietly hardening its self-hosted core.
A side-by-side editorial comparison of HyperDX and OpenHouse — release velocity, themes, recent moves, and the top alternatives to consider.
HyperDX is widening its PromQL and metrics support toward Grafana-style dashboards.
HyperDX ships as a monorepo of versioned packages (app, api, CLI, common-utils, collector), so one release shows up as several changelog entries. The 2.40.0 wave on October 1 adds multi-expression PromQL charts, PromQL macros, a minimum auto granularity per metric source, a Trace logs tab, and a StatsD receiver in the collector. Mid-September focused on alerting-as-code, with Terraform export for dashboard tile alerts.
OpenHouse is building the governance and optimizer plumbing a self-managing Iceberg catalog needs.
LinkedIn's OpenHouse ships near-daily releases focused on control-plane safety: generic lock reasons, SYSTEM_ONLY locks that block user reads and writes during maintenance, and a now-enforced 7-day snapshot reference retention on every table. In parallel the optimizer gained commit-stats collection and was restructured into libraries. Production-driven fixes, such as the HTS predicate incident, show the system running at scale.
HyperDX ships as a monorepo of versioned packages (app, api, CLI, common-utils, collector), so one release shows up as several changelog entries. The 2.40.0 wave on October 1 adds multi-expression PromQL charts, PromQL macros, a minimum auto granularity per metric source, a Trace logs tab, and a StatsD receiver in the collector. Mid-September focused on alerting-as-code, with Terraform export for dashboard tile alerts.
The product is closing feature gaps with Grafana on metrics, several of which it names outright, such as the per-datasource 'Min interval' equivalent. It's also widening ingestion, with StatsD/DogStatsD going straight into the collector. Alongside that, there's steady work on query cost (bounded Map-key scans) and on keeping the CLI's terminal charts in sync with the web app.
Expect more PromQL and metrics-dashboard parity work and further Terraform/API coverage of dashboards and alerts in the next minor release.
LinkedIn's OpenHouse ships near-daily releases focused on control-plane safety: generic lock reasons, SYSTEM_ONLY locks that block user reads and writes during maintenance, and a now-enforced 7-day snapshot reference retention on every table. In parallel the optimizer gained commit-stats collection and was restructured into libraries. Production-driven fixes, such as the HTS predicate incident, show the system running at scale.
The work points toward automated, system-driven table maintenance. Locks distinguish system actions from user actions, retention policies are enforced platform-wide, and the optimizer restructure exists explicitly to enable in-process, commit-driven analysis. OpenHouse is moving from a catalog that stores policies to one that runs them.
The next likely step is commit-driven optimizer analysis running inside the optimizer service, which the v0.5.502 restructure was explicitly done to unblock, probably using SYSTEM_ONLY locks during compaction or rewrites.
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 HyperDX or OpenHouse.
Countly is running two release lines on autopilot while quietly hardening its self-hosted core.
Kubecost's public feed is a string of release-candidate version bumps toward 3.3.
Holistics is putting AI to work on top of the warehouse's own semantic layer.
Clarity keeps turning bot traffic and AI citations into a second analytics product.
OpenCTI ships near-daily, steering security coverage and AI work through XTM One.
Basedash is turning chat and MCP into the main way dashboards get built.
See all HyperDX alternatives → · See all OpenHouse alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. HyperDX 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. HyperDX 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 Analytics products to evaluate alongside.
Top HyperDX alternatives in Analytics are ranked by recent ship velocity. Browse the "HyperDX alternatives" section above for the current picks, or visit /alternatives/hyperdx for the full list with editorial commentary on each.
Top OpenHouse alternatives in Analytics are ranked by recent ship velocity. Browse the "OpenHouse alternatives" section above for the current picks, or visit /alternatives/openhouse for the full list with editorial commentary on each.