RMVMR
RMVMR is being tidied in lockstep with MVMR, the package it wraps
A side-by-side editorial comparison of Basedash and units — release velocity, themes, recent moves, and the top alternatives to consider.
Basedash is done answering questions about your data — it now wants to tell you what to do next.
Basedash spent July and early August building the surfaces of an AI-native BI tool: suggestions that propose questions before you type, subscriptions that push dashboards to Slack and email, audit logs that record every query the AI runs, and a developer platform exposing the whole feature set through an API. Tasks, now in research preview, changes the output shape entirely — instead of charts and answers it produces a ranked list of work with a stated rationale and expected outcome, then watches whether the metrics move. A sidebar rebuild the day before quietly names the product's five pillars: Chat, Dashboards, Automations, Insights, and Data.
units reaches 1.0 by rewriting its parser and accepting the breakage that comes with it.
units attaches physical units to R vectors on top of the udunits2 library, covering arithmetic, conversion and ggplot2 scales. Version 1.0-0 replaced the unit-expression tokenizer so numbers are consistently treated as prefixes, and expressions like ml/min/1.73m^2 now parse the way physiologists write them. Printing follows NIST conventions, and 1.0-1 is a fix pass over memory handling and parser edge cases.
Basedash spent July and early August building the surfaces of an AI-native BI tool: suggestions that propose questions before you type, subscriptions that push dashboards to Slack and email, audit logs that record every query the AI runs, and a developer platform exposing the whole feature set through an API. Tasks, now in research preview, changes the output shape entirely — instead of charts and answers it produces a ranked list of work with a stated rationale and expected outcome, then watches whether the metrics move. A sidebar rebuild the day before quietly names the product's five pillars: Chat, Dashboards, Automations, Insights, and Data.
The arc runs from self-serve querying toward prescription and closed-loop measurement. Each release chips away at the assumption that a human must decide what to look at: suggestions removed the blank prompt, subscriptions removed the visit, and Tasks removes the interpretation step. The navigation rework is the tell that this is now a multi-module product rather than a chat box with extras — and the enterprise scaffolding arriving alongside it, audit logs covering AI queries plus retention controls, is what makes an autonomous analyst deployable rather than a demo.
Tasks graduating from research preview will be the release to watch; the outcome-tracking loop it describes only has value once it has run long enough to show whether its recommendations worked. Expect Tasks to become a sixth sidebar module and to be exposed through the developer platform API, since that is where every other Basedash capability has landed.
units attaches physical units to R vectors on top of the udunits2 library, covering arithmetic, conversion and ggplot2 scales. Version 1.0-0 replaced the unit-expression tokenizer so numbers are consistently treated as prefixes, and expressions like ml/min/1.73m^2 now parse the way physiologists write them. Printing follows NIST conventions, and 1.0-1 is a fix pass over memory handling and parser edge cases.
The long 0.8-x run was accretion — ggplot2 scales absorbed from ggforce, ud_convert(), matrix methods, steady performance work — while known parsing defects stayed in place. The 1.0 release finally traded backwards compatibility for correct parsing, and 1.0-1's pointer-wrapping and exception-propagation work suggests the C++ glue is being hardened behind it. Fixes cluster at the udunits2 boundary, which remains the main source of surprises.
Expect continued patch releases against udunits2 quirks and the new tokenizer's fallout rather than new surface area, with the ggplot2 integration and conversion helpers already in place.
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 units.
RMVMR is being tidied in lockstep with MVMR, the package it wraps
geoarrow tracks the GeoArrow spec and otherwise just keeps compiling
n2khab keeps retracting interpretations of habitat data it can't actually support
tidypolars is grinding toward complete dplyr coverage, one supported function at a time
OneSampleMR found that argument order in a formula was silently changing its estimates
bpbounds found the same swapped-cell bug twice and clamped its bounds back into range
See all Basedash alternatives → · See all units 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 7.5 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 7.5 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 units alternatives in Analytics are ranked by recent ship velocity. Browse the "units alternatives" section above for the current picks, or visit /alternatives/units-r for the full list with editorial commentary on each.