Omni
Omni ships weekly, and almost every week the headline item is an AI feature.
A side-by-side editorial comparison of hdnom and Holistics — release velocity, themes, recent moves, and the top alternatives to consider.
hdnom is in pure custodial mode, absorbing glmnet's changes so its users don't have to
hdnom builds nomograms and validation/calibration workflows for high-dimensional Cox survival models on top of glmnet, ncvreg and penalized. The package's own interface has been stable since the 6.0.0 refactor in 2019; every release since has been maintenance. The recent run is entirely about surviving glmnet's evolution — a lambda-selection rule argument, then a cox.ties argument pinning the old tie handling.
Holistics is adding governance to the AI layer it spent the summer building.
Holistics ships small, frequent notes - often one or two sentences - covering three strands at once: AI features in Explore and Chat, as-code control over presentation through AML, and workspace hygiene like file history and dark mode. The August entries turn to the AI layer's edges rather than its capabilities, with an AI user attribute for restricting what the assistant can reach. Several entries are barely a line long, so scope frequently has to be read from the headline.
hdnom builds nomograms and validation/calibration workflows for high-dimensional Cox survival models on top of glmnet, ncvreg and penalized. The package's own interface has been stable since the 6.0.0 refactor in 2019; every release since has been maintenance. The recent run is entirely about surviving glmnet's evolution — a lambda-selection rule argument, then a cox.ties argument pinning the old tie handling.
The releases track two upstream pressures with no feature work of its own. glmnet is the larger one: its 4.1-9 change to how Cox cross-validation errors are normalized made lambda.1se select null models far more often, forcing hdnom to expose a rule argument and switch its examples to lambda.min. R-devel is the other, producing a steady trickle of strict-headers, deprecated-symbol and check-note fixes. The pattern is consistent — absorb the upstream change, default to whatever preserves existing behaviour, let users opt into the new one.
The cox.ties default is explicitly pinned to "breslow" to silence glmnet's migration warning, which is a deferral rather than a decision; expect a future release to flip that default to "efron" once glmnet completes the transition.
Holistics ships small, frequent notes - often one or two sentences - covering three strands at once: AI features in Explore and Chat, as-code control over presentation through AML, and workspace hygiene like file history and dark mode. The August entries turn to the AI layer's edges rather than its capabilities, with an AI user attribute for restricting what the assistant can reach. Several entries are barely a line long, so scope frequently has to be read from the headline.
The AI work has moved through a recognizable sequence: capability first with chart suggestions, then observability with AI Chat Insights for admins, and now access control with an AI-specific user attribute. Alongside it, Holistics keeps pulling presentation into AML - custom charts, theme palettes, currency formats - so the things analysts used to click are versioned as code. File history is the join between the two threads, giving every dashboard, model, and dataset its own restorable timeline.
With capability, visibility, and access control now in place for the AI layer, the next step is likely audit or policy depth - logging what the assistant answered against which data - rather than new AI surfaces.
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 hdnom or Holistics.
Omni ships weekly, and almost every week the headline item is an AI feature.
silx settles into maintenance a release after its PySide6 migration
Plotly is turning its cloud into a metered compute platform with an enterprise on-ramp.
aniread stops asking you to know which tracker wrote the file
Rho's release machinery finally produced a stable build — and it shipped no new product.
Usermaven closed the loop: data comes in from anywhere, and now it goes back out.
See all hdnom 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. hdnom 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. hdnom 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 hdnom alternatives in Analytics are ranked by recent ship velocity. Browse the "hdnom alternatives" section above for the current picks, or visit /alternatives/hdnom 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.