tidyr
tidyr replaced separate() with a family that says what it does.
A side-by-side editorial comparison of Hex and modeltime — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Hex | modeltime |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 6.3 | 0.0 |
| Sparks · 30d | 1 | 0 |
| Top themes | agents, cli, mcp, model-routing | forecasting, conformal-prediction, tidymodels, parallelism |
| Last editorial update | 1d ago | 1h ago |
| Website | — | Visit → |
Hex is moving its agent out of the notebook and onto programmable surfaces.
Hex ships a fortnightly digest, and the through-line across the last ten is agent reach. The agent now runs from a CLI and API, appears inside Codex, acts as an MCP client against the user's own apps, can search the web, and can see the generative apps it builds. Alongside that, the model layer has become a customer-facing control: a picker, an admin-set default, Auto with visible attribution, and a rotating roster including Fable 5, Kimi K2.7, Claude Opus 5 and GPT-5.6.
modeltime built conformal intervals in, then went quiet on features.
modeltime is at 1.3.3, a single change making the package robust to xgboost version shifts. The feature weight sits in 1.3.2, which added a future-based parallel backend, the maape() accuracy metric and dials helpers for ADAM engine tuning, and further back in the 1.2.8 and 1.3.0 pair that introduced conformal prediction intervals and then carried them through the nested forecasting workflow.
Hex ships a fortnightly digest, and the through-line across the last ten is agent reach. The agent now runs from a CLI and API, appears inside Codex, acts as an MCP client against the user's own apps, can search the web, and can see the generative apps it builds. Alongside that, the model layer has become a customer-facing control: a picker, an admin-set default, Auto with visible attribution, and a rotating roster including Fable 5, Kimi K2.7, Claude Opus 5 and GPT-5.6.
Hex is positioning the agent as a component other systems call rather than a feature users visit. Governance is being built out in parallel — spend limits, credit usage controls, enterprise role-request controls, signed embedding — which is the pattern of a product preparing for programmatic usage it does not directly supervise. The generative-app surface is drifting the same way, from generated output toward editable, brandable, embeddable artifacts.
Expect the CLI and API surface to deepen before the notebook UI gains much, with more of Context Studio and app management reachable programmatically, and expect the spend and role controls to keep pace as headless usage grows.
modeltime is at 1.3.3, a single change making the package robust to xgboost version shifts. The feature weight sits in 1.3.2, which added a future-based parallel backend, the maape() accuracy metric and dials helpers for ADAM engine tuning, and further back in the 1.2.8 and 1.3.0 pair that introduced conformal prediction intervals and then carried them through the nested forecasting workflow.
The arc runs from uncertainty quantification to execution. Conformal intervals arrived first and were then threaded through nested fitting, refitting and the printed forecast tables so users can see which confidence method produced an interval. The later work moves down a layer to how forecasts are computed — a portable future backend replacing foreach tuning — rather than what they express.
With only an xgboost compatibility fix since the 1.3.2 feature release, the entries do not support a confident prediction about what comes next beyond continued dependency maintenance.
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 Hex or modeltime.
tidyr replaced separate() with a family that says what it does.
performance keeps adding ways to check a model you have already fitted.
CmdStanPy is clearing deprecations ahead of a 2.0 it keeps announcing.
DoWhy adds one estimation method a year and keeps its identification edge.
OpenHouse is hardening the seams where table policies and jobs quietly fail.
silx 3.0 moved its default Qt binding to PySide6 — a migration for everyone embedding it.
See all Hex alternatives → · See all modeltime alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Hex is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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. Hex is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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 Hex alternatives in Analytics are ranked by recent ship velocity. Browse the "Hex alternatives" section above for the current picks, or visit /alternatives/hex for the full list with editorial commentary on each.
Top modeltime alternatives in Analytics are ranked by recent ship velocity. Browse the "modeltime alternatives" section above for the current picks, or visit /alternatives/modeltime for the full list with editorial commentary on each.