Lightdash
Lightdash keeps handing authoring to outside agents and keeping the governed layer for itself.
A side-by-side editorial comparison of oblicubes and Whatagraph — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | oblicubes | Whatagraph |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 0.0 | 5.0 |
| Sparks · 30d | 0 | 0 |
| Top themes | r, data-viz, grid-graphics, ggplot2 | reporting, agencies, integrations, reliability |
| Last editorial update | 4d ago | 46m ago |
| Website | Visit → | — |
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.
Whatagraph keeps fixing what breaks when one account runs a thousand sources.
Whatagraph is working on the parts of agency reporting that break under volume rather than on new analysis capability. Stored data removed live API calls from render time in the Basis rebuild, connection failover keeps widgets alive when one teammate's token expires, and report shortcuts let a heavy report be split into a hub with supporting detail. Presentation control arrives steadily alongside — automatic conditional formatting, per-metric decimal places, chosen comparison colors. The newest change moves unified-field mapping into the Source Group builder, so a cross-channel group can be fixed in place instead of rebuilt.
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.
Whatagraph is working on the parts of agency reporting that break under volume rather than on new analysis capability. Stored data removed live API calls from render time in the Basis rebuild, connection failover keeps widgets alive when one teammate's token expires, and report shortcuts let a heavy report be split into a hub with supporting detail. Presentation control arrives steadily alongside — automatic conditional formatting, per-metric decimal places, chosen comparison colors. The newest change moves unified-field mapping into the Source Group builder, so a cross-channel group can be fixed in place instead of rebuilt.
The through-line is reliability and workflow cost at agency scale, where one account runs hundreds or thousands of sources across several people. Each release picks a specific moment where that scale used to force a detour — a dead token, a forty-widget report, a half-built source group — and removes the detour rather than adding a capability. Integration work stays additive and named: Ahrefs Rank Tracker, WhatConverts, Snowflake, bol., each filling a stated reporting gap rather than broadening a connector catalog.
Expect the same volume-driven treatment applied to the remaining multi-step setup flows, and further integrations chosen to close named gaps rather than to grow the connector count.
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 oblicubes or Whatagraph.
Lightdash keeps handing authoring to outside agents and keeping the governed layer for itself.
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 oblicubes alternatives → · See all Whatagraph alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Whatagraph is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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. Whatagraph is currently shipping more aggressively (velocity 5.0 vs 0.0), with 0 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 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.
Top Whatagraph alternatives in Analytics are ranked by recent ship velocity. Browse the "Whatagraph alternatives" section above for the current picks, or visit /alternatives/whatagraph for the full list with editorial commentary on each.