Fulcrum
Fulcrum is retiring Google Maps for Esri and stabilising the ArcGIS stack behind it.
A side-by-side editorial comparison of Basedash and Plotly — release velocity, themes, recent moves, and the top alternatives to consider.
Basedash turned its AI analyst into an API, then spent two weeks making it auditable
Basedash is an AI data analyst that spent July becoming two things at once: an agent that acts, and infrastructure other products build on. Actions let it write SQL and operate in Stripe, HubSpot, or anything behind an MCP connector; the developer platform exposes chat, daily insights, automations, and dashboards through the public API. The most recent releases are the counterweight to both — SCIM provisioning, then audit logs that record every query the AI itself runs.
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.
Basedash is an AI data analyst that spent July becoming two things at once: an agent that acts, and infrastructure other products build on. Actions let it write SQL and operate in Stripe, HubSpot, or anything behind an MCP connector; the developer platform exposes chat, daily insights, automations, and dashboards through the public API. The most recent releases are the counterweight to both — SCIM provisioning, then audit logs that record every query the AI itself runs.
Two tracks are converging. The agent keeps gaining reach — write access, MCP connectors, unprompted suggestions drawn from your own data — while the surrounding controls arrive just behind it, each release answering the objection the previous one created. The MotherDuck connector marks a third track: the more the analyst is sold as an API, the more it has to speak to whatever warehouse the customer already runs.
Expect governance to extend to Actions specifically — per-connector or per-action approval policy, since audit logs now record agent writes but the entries describe approval as a case-by-case prompt. More data sources after MotherDuck are the safer bet.
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 Basedash 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
See all Basedash alternatives → · See all Plotly alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Basedash 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. Basedash 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 Basedash alternatives in Analytics are ranked by recent ship velocity. Browse the "Basedash alternatives" section above for the current picks, or visit /alternatives/basedash 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.