Whatagraph
Whatagraph keeps fixing what breaks when one account runs a thousand sources.
A side-by-side editorial comparison of Lightdash and oblicubes — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Lightdash | oblicubes |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 7.5 | 0.0 |
| Sparks · 30d | 2 | 0 |
| Top themes | business-intelligence, ai-agents, content-as-code, developer-experience | r, data-viz, grid-graphics, ggplot2 |
| Last editorial update | 1h ago | 4d ago |
| Website | — | Visit → |
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.
A tiny grid renderer for oblique-projection cubes, complete since its first release.
oblicubes draws 3D cubes and cuboids in oblique projection as grid grobs, with ggplot2 geom wrappers and a height-matrix helper for turning elevation data into coordinates. The entire feature set arrived in the initial 0.1.2 release, adapted from coolbutuseless's isocubes and cj-holmes's isocuboids. The two releases since have widened compatibility rather than added anything.
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.
oblicubes draws 3D cubes and cuboids in oblique projection as grid grobs, with ggplot2 geom wrappers and a height-matrix helper for turning elevation data into coordinates. The entire feature set arrived in the initial 0.1.2 release, adapted from coolbutuseless's isocubes and cj-holmes's isocuboids. The two releases since have widened compatibility rather than added anything.
The package is finished and its maintainer is treating it that way. 1.0.0 removed the R 4.1 native pipe from examples specifically so earlier R versions could use it — reaching backward, not forward — and added image alt text. The only change since is swapping a deprecated dplyr call in examples.
Expect nothing beyond occasional dependency deprecation fixes; the release pattern shows a small, deliberately complete package being kept installable.
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 Lightdash or oblicubes.
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
distributions3 0.3.0 adds sample-based distributions and likelihood derivatives
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
See all Lightdash alternatives → · See all oblicubes 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 0.0), with 2 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. Lightdash is currently shipping more aggressively (velocity 7.5 vs 0.0), with 2 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 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.
Top oblicubes alternatives in Analytics are ranked by recent ship velocity. Browse the "oblicubes alternatives" section above for the current picks, or visit /alternatives/oblicubes-r for the full list with editorial commentary on each.