Whatagraph
Whatagraph keeps fixing what breaks when one account runs a thousand sources.
Comparison · Analytics
gtsummary vs Lightdash
A side-by-side editorial comparison of gtsummary and Lightdash — release velocity, themes, recent moves, and the top alternatives to consider.
gtsummary vs Lightdash: at a glance
| Feature | gtsummary | Lightdash |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 0.0 | 7.5 |
| Sparks · 30d | 0 | 2 |
| Top themes | clinical-tables, analysis-results-data, regression-summaries, reproducible-reporting | business-intelligence, ai-agents, content-as-code, developer-experience |
| Last editorial update | 4d ago | 4h ago |
| Website | Visit → | — |
What is gtsummary?
gtsummary is quietly rebuilding itself around analysis results data, one table verb at a time.
gtsummary builds publication-ready summary, regression and survival tables for clinical and epidemiological work. Across this window it has grown in two directions at once: table composition primitives — splitting tables by rows and columns, stacking with labeled IDs, nested strata stacks, flexible merge columns — and a steadily deepening ARD layer, where tbl_ard_* functions, gather_ard() and the hierarchical table family expose the underlying analysis results data as a first-class object.
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.
gtsummary vs Lightdash: editorial side-by-side
gtsummary
0.0ANALYTICS
gtsummary is quietly rebuilding itself around analysis results data, one table verb at a time.
◆ Current state
gtsummary builds publication-ready summary, regression and survival tables for clinical and epidemiological work. Across this window it has grown in two directions at once: table composition primitives — splitting tables by rows and columns, stacking with labeled IDs, nested strata stacks, flexible merge columns — and a steadily deepening ARD layer, where tbl_ard_* functions, gather_ard() and the hierarchical table family expose the underlying analysis results data as a first-class object.
◆ Where it's heading
The ARD work is the through-line. Table IDs exist so gather_ard() can return a named list; hierarchical tables gained per-level sorting and targeted filtering; ARD inputs are pre-processed so sorting applies to non-standard shapes. The package is becoming a structured-results engine that happens to render tables, rather than a renderer alone. Alongside that, 2.2.0 restored data pre-processing that 2.0 had removed after the reduced functionality hurt users — a maintainer willing to reverse a major-version decision.
◆ Prediction
Expect the hierarchical and ARD functions, introduced as a preview without a full deprecation cycle, to keep stabilizing toward a settled API rather than new table types appearing.
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 gtsummary 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 gtsummary 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 gtsummary alternatives → · See all Lightdash alternatives →
Recent activity from gtsummary and Lightdash
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d 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
- 2mo agogtsummaryTheme elements no longer evaluated by default
- 8mo agogtsummaryARD strata functions and finer theme control
- 11mo agogtsummaryPer-level hierarchical sorting and labeled stacking
- 1y agogtsummaryTable splitting, ID labeling, and add_difference_row
- 1y agogtsummaryData pre-processing restored after the 2.0 removal
- 1y agogtsummarytbl_merge gains explicit merge columns
Frequently asked questions
What is the difference between gtsummary 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 gtsummary 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 gtsummary?
Top gtsummary alternatives in Analytics are ranked by recent ship velocity. Browse the "gtsummary alternatives" section above for the current picks, or visit /alternatives/gtsummary-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.