← Back to home
Comparison · Analytics

Basedash vs vellumwidget

A side-by-side editorial comparison of Basedash and vellumwidget — release velocity, themes, recent moves, and the top alternatives to consider.

Basedash vs vellumwidget: at a glance

FeatureBasedashvellumwidget
SectorAnalyticsAnalytics
Velocity score7.56.3
Sparks · 30d11
Top themesbi, ai-analyst, external-sharing, apir-graphics, interactive-widgets, declarative-interaction, shiny
Last editorial update51m ago3d ago
WebsiteVisit →Visit →

What is Basedash?

Basedash keeps pushing its data out of the workspace — now to people without accounts

Basedash is a BI tool built around an AI data analyst, and the last month has been about getting its output to more places: an API that exposes chat, insights, automations and dashboards; scheduled snapshots to email and Slack; and now a link that opens a live, filterable dashboard for someone with no Basedash account. Alongside that distribution work sits a research-preview agent, Tasks, that reads company data and produces a ranked to-do list. Audit logs, including a record of every query the AI runs, arrived in the same window.

Read the full Basedash trajectory →

What is vellumwidget?

vellumwidget is dissolving its own API: interaction now lives in the plot spec, not the widget call.

vellumwidget compiles a vellum scene or a vellumplot plot into a self-contained client-side htmlwidget with hover, select, brush, lasso, pan/zoom and export, and no server round-trip. The two-way Shiny story is complete: interactions surface as reactive inputs keyed by output id, and vellumwidget_proxy() drives an already-rendered widget from the server without re-rendering it. The last two releases are fidelity work rather than new surface, calibrating hit-testing from the rendered positions of marks and rendering the raster base image at 2x for HiDPI screens.

Read the full vellumwidget trajectory →

Basedash vs vellumwidget: editorial side-by-side

B
Basedash
ANALYTICS
7.5

Basedash keeps pushing its data out of the workspace — now to people without accounts

◆ Current state

Basedash is a BI tool built around an AI data analyst, and the last month has been about getting its output to more places: an API that exposes chat, insights, automations and dashboards; scheduled snapshots to email and Slack; and now a link that opens a live, filterable dashboard for someone with no Basedash account. Alongside that distribution work sits a research-preview agent, Tasks, that reads company data and produces a ranked to-do list. Audit logs, including a record of every query the AI runs, arrived in the same window.

◆ Where it's heading

Two arcs are running in parallel. One narrows the gap between viewing data and acting on it — suggestions before you type a prompt, then Tasks writing the work item and tracking whether the metric moved. The other decouples consumption from seats: API, subscriptions, and public links each reach an audience that never logs in. The interface work (module-anchored sidebar, per-user table sorting that doesn't rewrite the author's SQL) reads as load-bearing for both.

◆ Prediction

Tasks leaving research preview is the release that decides how much of this is real; its value depends entirely on the outcome-tracking loop having run long enough to show whether its recommendations worked. Expect the sharing surface to grow permissions and expiry controls next, since a link that works without an account is the first place governance pressure lands.

V
vellumwidget
ANALYTICS
6.3

vellumwidget is dissolving its own API: interaction now lives in the plot spec, not the widget call.

◆ Current state

vellumwidget compiles a vellum scene or a vellumplot plot into a self-contained client-side htmlwidget with hover, select, brush, lasso, pan/zoom and export, and no server round-trip. The two-way Shiny story is complete: interactions surface as reactive inputs keyed by output id, and vellumwidget_proxy() drives an already-rendered widget from the server without re-rendering it. The last two releases are fidelity work rather than new surface, calibrating hit-testing from the rendered positions of marks and rendering the raster base image at 2x for HiDPI screens.

◆ Where it's heading

The direction is declarative. 0.7.0 removed the interaction-intent arguments from as_widget() outright, dropping the signature from roughly 36 arguments to 24 and moving highlight, filter and cross-filter into vellumplot's spec via select_point(), condition() and filter_by(). Each release since has enacted more of that compiled spec on the frozen scene, from conditional encodings to single-view filters to cross-view cross-filtering, leaving the widget as an interpreter of the plot rather than a configuration surface of its own. The bug fixes track the same theme the engine's do: measured geometry and rendered geometry must not drift.

◆ Prediction

The notes name the remaining hold-outs explicitly, saying hover_mode, crosshair, legend_click, select_mode and the tooltip-appearance arguments remain only until their spec equivalents land, so the next releases most likely move those into vellumplot and shrink as_widget() further. The scale binds flagged as following the filter work are the other stated next step.

Alternatives to Basedash and vellumwidget

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 vellumwidget.

See all Basedash alternatives → · See all vellumwidget alternatives →

Recent activity from Basedash and vellumwidget

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 2d agoBasedashIntroducing public sharing: live dashboards for anyone
  2. 5d agoBasedashIntroducing Tasks: your operations, on autopilot
  3. 6d agoBasedashA sidebar that follows what you’re working on
  4. 12d agoBasedashIntroducing Basedash Subscriptions
  5. 13d agoBasedashSort and arrange tables without changing the chart
  6. 18d agovellumwidget2x raster base image for HiDPI, and exact element hit-testing
  7. 19d agoBasedashIntroducing Basedash audit logs
  8. 23d agovellumwidgetInteraction moves into the plot spec; as_widget() sheds a third of its arguments
  9. 1mo agovellumwidgetAxis-aware zoom re-ticks the axes instead of scaling the whole scene
  10. 1mo agovellumwidgetSelectable native SVG text, and crisp canvas redraw when zooming raster
  11. 1mo agovellumwidgetServer-side proxy drives a rendered widget without re-rendering it
  12. 1mo agovellumwidgetShiny input read-back, and keyboard plus screen-reader access by default

Frequently asked questions

What is the difference between Basedash and vellumwidget?

They serve adjacent needs but don't currently overlap on shipped themes. Basedash is currently shipping more aggressively (velocity 7.5 vs 6.3), with 1 editorial sparks in the last 30 days against 1. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is Basedash better than vellumwidget?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Basedash is currently shipping more aggressively (velocity 7.5 vs 6.3), with 1 editorial sparks in the last 30 days against 1. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.

What are the best alternatives to Basedash?

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.

What are the best alternatives to vellumwidget?

Top vellumwidget alternatives in Analytics are ranked by recent ship velocity. Browse the "vellumwidget alternatives" section above for the current picks, or visit /alternatives/vellumwidget for the full list with editorial commentary on each.