Whatagraph
Whatagraph keeps fixing what breaks when one account runs a thousand sources.
Comparison · Analytics
GDPuc vs Lightdash
A side-by-side editorial comparison of GDPuc and Lightdash — release velocity, themes, recent moves, and the top alternatives to consider.
GDPuc vs Lightdash: at a glance
| Feature | GDPuc | Lightdash |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 0.0 | 7.5 |
| Sparks · 30d | 0 | 2 |
| Top themes | economics, currency-conversion, data-harmonisation, r-package | business-intelligence, ai-agents, content-as-code, developer-experience |
| Last editorial update | 4d ago | 2h ago |
| Website | Visit → | — |
What is GDPuc?
A GDP unit converter that keeps widening which currencies and deflators it will accept
GDPuc converts GDP figures between currencies, base years and price bases, using World Bank conversion factors, and is used as a dependency inside the madrat/magclass modelling stack. The 1.6.x line introduced xCU as a unit — local currency of any country x — added arguments for non-default iso3c and year columns, and made the package work with madrat caching and region mappings. The most recent release fixes a bug in iso3c column selection.
What is Lightdash?
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.
GDPuc vs Lightdash: editorial side-by-side
GDPuc
0.0ANALYTICS
A GDP unit converter that keeps widening which currencies and deflators it will accept
◆ Current state
GDPuc converts GDP figures between currencies, base years and price bases, using World Bank conversion factors, and is used as a dependency inside the madrat/magclass modelling stack. The 1.6.x line introduced xCU as a unit — local currency of any country x — added arguments for non-default iso3c and year columns, and made the package work with madrat caching and region mappings. The most recent release fixes a bug in iso3c column selection.
◆ Where it's heading
The direction is toward accepting messier inputs from more callers. Successive releases have relaxed assumptions the package originally made — that a year column exists, that column names follow a convention, that PPP data is available for every country — and each relaxation is driven by an integration rather than by an economics question. The one genuinely methodological addition is the CPI as an alternative deflator, which arrived in 1.0.0.
◆ Prediction
Conversion factors are versioned World Bank data and were last refreshed in 1.0.0, so a data update is the most likely content of the next substantive release, alongside continued fixes to the column-detection logic that has now produced bugs twice.
Lightdash
7.5ANALYTICS
Lightdash keeps handing authoring to outside agents and keeping the governed layer for itself.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to GDPuc and Lightdash
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 GDPuc or Lightdash.
Delta Lake
A 4.4.0 tag appears, but the feed carries only its release plumbing
distributions3
distributions3 0.3.0 adds sample-based distributions and likelihood derivatives
Basedash
Basedash keeps pushing its data out of the workspace — now to people without accounts
RStudio
RStudio ships through release branches, and the notes are commit messages
dbt Core
dbt Fusion's second beta is adapter work: ClickHouse gets materializations, indexes, and catalogs
See all GDPuc alternatives → · See all Lightdash alternatives →
Recent activity from GDPuc and Lightdash
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 23h agoLightdash📝 Rename chart slugs safely
- 7d agoLightdashDeep research ⚡
- 16d agoLightdash🤖 Build data apps locally with your favorite agent ⚡
- 20d agoLightdash📦 More content as code
- 20d agoLightdashSQL Runner: Big Number
- 24d agoLightdash🎯 Ask for one filter, not every filter
- 8mo agoGDPucFix iso3c column selection
- 9mo agoGDPucxCU unit introduced; madrat caching and region mappings supported
- 1y agoGDPucBetter column detection; magclass objects without years accepted
- 2y agoGDPucCPI added as an alternative deflator; constant euro conversion
- 3y agoGDPucSuggests field cleaned for CRAN compliance
- 3y agoGDPucCorrect conversion factors returned by return_cfs
Frequently asked questions
What is the difference between GDPuc and Lightdash?
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.
Is GDPuc better than Lightdash?
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.
What are the best alternatives to GDPuc?
Top GDPuc alternatives in Analytics are ranked by recent ship velocity. Browse the "GDPuc alternatives" section above for the current picks, or visit /alternatives/gdpuc-r for the full list with editorial commentary on each.
What are the best alternatives to Lightdash?
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.