Whatagraph
Whatagraph keeps fixing what breaks when one account runs a thousand sources.
A side-by-side editorial comparison of distributions3 and Lightdash — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | distributions3 | Lightdash |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 6.3 | 7.5 |
| Sparks · 30d | 1 | 2 |
| Top themes | r-package, probability-distributions, empirical-distributions, likelihood-inference | business-intelligence, ai-agents, content-as-code, developer-experience |
| Last editorial update | 5h ago | 46m ago |
| Website | Visit → | — |
distributions3 0.3.0 adds sample-based distributions and likelihood derivatives
An R package giving probability distributions a consistent object interface - d/p/q/r functions, moments, and prodist() methods that pull a fitted distribution out of a regression object. Version 0.3.0 is the first substantive release under Achim Zeileis's maintenance, and it widens what a distribution is allowed to be: Empirical() represents a distribution by a random sample rather than by parameters, and numerical fallbacks now fill in cdf(), pdf(), quantile(), random() and the moments for any object that implements only some of them. New score() and hessian() generics compute first and second derivatives of the log-likelihood with respect to the parameters, analytically for a few distributions and numerically for the rest.
Lightdash keeps handing authoring to outside agents and keeping the governed layer for itself.
Lightdash has spent two months rebuilding around agents rather than around its own web editor. Data apps are scaffolded and iterated locally with Cursor, Claude Code or Codex and uploaded for the instance to build; Deep Research runs multi-step investigations against the warehouse; content as code now covers charts, dashboards, spaces, permissions, virtual views, AI agents, automations, users, groups and roles. The conventional BI surface is still maintained — SQL Runner big numbers, filter groups, timezone handling — but it is no longer where new capability lands. The newest release is a CLI slug rename that keeps Lightdash and the local files in step.
An R package giving probability distributions a consistent object interface - d/p/q/r functions, moments, and prodist() methods that pull a fitted distribution out of a regression object. Version 0.3.0 is the first substantive release under Achim Zeileis's maintenance, and it widens what a distribution is allowed to be: Empirical() represents a distribution by a random sample rather than by parameters, and numerical fallbacks now fill in cdf(), pdf(), quantile(), random() and the moments for any object that implements only some of them. New score() and hessian() generics compute first and second derivatives of the log-likelihood with respect to the parameters, analytically for a few distributions and numerically for the rest.
Growth used to arrive as new distribution families contributed from outside - the extreme-value set, Erlang, later the Poisson binomial. This release changes the axis: alongside two new distributions it adds an inference layer (score, hessian) and a forecast-evaluation one (crps() methods against scoringRules), which are capabilities about distributions rather than more of them. Dependency weight is being cut at the same time, with ggplot2 demoted to Suggests and glue replaced by base R sprintf().
With numeric fallbacks and the derivative generics in place, expect analytic score() and hessian() methods to be filled in across more of the distribution catalogue. The constructor-default change is the likeliest source of follow-up fixes, since calls like Poisson() now return a length-zero distribution where they previously errored.
Lightdash has spent two months rebuilding around agents rather than around its own web editor. Data apps are scaffolded and iterated locally with Cursor, Claude Code or Codex and uploaded for the instance to build; Deep Research runs multi-step investigations against the warehouse; content as code now covers charts, dashboards, spaces, permissions, virtual views, AI agents, automations, users, groups and roles. The conventional BI surface is still maintained — SQL Runner big numbers, filter groups, timezone handling — but it is no longer where new capability lands. The newest release is a CLI slug rename that keeps Lightdash and the local files in step.
The split is deliberate: authoring and interrogation move outward to whatever agent the user already runs, while the governed metrics, permissions and build stay inside Lightdash. The slug-rename command is a small marker of how far that has gone — refactoring tools are now needed for the repository rather than for the web UI, because that is where the content lives. Deep Research extends the same bet from generating artifacts to conducting analysis, testing competing explanations and validating numbers instead of emitting a chart.
Expect more repository-side maintenance commands of the slug-rename kind — moves, deletes, bulk edits across content-as-code files — since the agent workflow now produces content faster than the CLI can tidy it.
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 distributions3 or Lightdash.
Whatagraph keeps fixing what breaks when one account runs a thousand sources.
A 4.4.0 tag appears, but the feed carries only its release plumbing
Basedash keeps pushing its data out of the workspace — now to people without accounts
RStudio ships through release branches, and the notes are commit messages
dbt Fusion's second beta is adapter work: ClickHouse gets materializations, indexes, and catalogs
Fulcrum is betting its whole map stack on Esri, with a hard Google Maps cutoff on September 1.
See all distributions3 alternatives → · See all Lightdash alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Lightdash is currently shipping more aggressively (velocity 7.5 vs 6.3), with 2 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Lightdash is currently shipping more aggressively (velocity 7.5 vs 6.3), with 2 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.
Top distributions3 alternatives in Analytics are ranked by recent ship velocity. Browse the "distributions3 alternatives" section above for the current picks, or visit /alternatives/distributions3-r for the full list with editorial commentary on each.
Top Lightdash alternatives in Analytics are ranked by recent ship velocity. Browse the "Lightdash alternatives" section above for the current picks, or visit /alternatives/lightdash for the full list with editorial commentary on each.