Fulcrum
Fulcrum is retiring Google Maps for Esri and stabilising the ArcGIS stack behind it.
A side-by-side editorial comparison of Hex and Plotly — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Hex | Plotly |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 6.3 | 0.0 |
| Sparks · 30d | 1 | 0 |
| Top themes | agents, cli, generative-apps, model-choice | dash-hosting, plotly-cloud, custom-domains, compute-credits |
| Last editorial update | 4d ago | 11h ago |
| Website | — | Visit → |
Hex pulls its agent out of the notebook and into a CLI and API
Hex ships weekly and the last two months read as one project: making the agent a surface in its own right rather than a feature living inside the notebook. The newest release exposes the agent through a CLI and an API, prints cell outputs in the terminal, and lists which resources each run touched. Generative apps got the same treatment slightly earlier, with editable app code, CSV downloads on every chart and table, and a signed embedding path.
The desktop app builder is pre-1.0, but Plotly Cloud quietly turned into a Dash hosting platform.
Two releases in this window build out Plotly Cloud as real hosting rather than a preview environment: compute modes and app sizing put a sleep-versus-always-awake dial and a resource tier on every app, and custom domains let teams serve Dash apps on a hostname they own, with DNS verification and TLS provisioning handled for them. The paid boundary sits on that line — .plotly.app URLs are free, owned domains are Pro and above. Plotly Studio meanwhile ticks through 0.0.82 to 0.0.85 with saved credentials, Winget distribution, breadcrumb navigation and a confirmation step before automatic secret redaction.
Hex ships weekly and the last two months read as one project: making the agent a surface in its own right rather than a feature living inside the notebook. The newest release exposes the agent through a CLI and an API, prints cell outputs in the terminal, and lists which resources each run touched. Generative apps got the same treatment slightly earlier, with editable app code, CSV downloads on every chart and table, and a signed embedding path.
Two things are converging: an agent that can be driven from anywhere, and generative apps as the artifact it produces. The model layer is deliberately swappable, with Claude Opus 5, Kimi K2.7, Fable 5 and an admin-set default all landing inside eight weeks, so Hex is not tying its product to one provider. Governance is arriving in step with the capability work, through spend limits, credit controls, enterprise role requests and IAM support, which is the sequence a tool follows when its buyers become platform teams.
The next move is likely unattended agent runs on a schedule or in CI, since the CLI and API remove the last reason a person has to be sitting in the notebook while it works.
Two releases in this window build out Plotly Cloud as real hosting rather than a preview environment: compute modes and app sizing put a sleep-versus-always-awake dial and a resource tier on every app, and custom domains let teams serve Dash apps on a hostname they own, with DNS verification and TLS provisioning handled for them. The paid boundary sits on that line — .plotly.app URLs are free, owned domains are Pro and above. Plotly Studio meanwhile ticks through 0.0.82 to 0.0.85 with saved credentials, Winget distribution, breadcrumb navigation and a confirmation step before automatic secret redaction.
The centre of gravity has moved from the desktop tool to the hosting product. Studio's releases are pre-1.0 hardening — navigation, credential handling, install paths — while Cloud is the side gaining capability that changes what a customer can do, and it is where the tier boundaries are being drawn. Consumption economics are becoming explicit, with idle spend and cold starts surfaced as customer-tunable settings rather than hidden platform behaviour.
The next Cloud releases most likely extend the resource and access controls a hosted app needs — finer app sizing, or authentication and access rules on custom domains — rather than adding capability to Studio.
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 Plotly.
Fulcrum is retiring Google Maps for Esri and stabilising the ArcGIS stack behind it.
Shynet went silent for two and a half years and a security audit is what woke it up.
Power BI's monthly grind: authoring defaults, DAX documentation, and cleaner axes.
BigQuery is making itself agent-callable and pulling inference inside the SQL boundary.
Lightdash is turning BI into an app platform its users' coding agents can build against.
TimescaleDB trades new features for lock contention wins and a security patch
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 Plotly alternatives in Analytics are ranked by recent ship velocity. Browse the "Plotly alternatives" section above for the current picks, or visit /alternatives/plotly for the full list with editorial commentary on each.