Whatagraph
Whatagraph keeps fixing what breaks when one account runs a thousand sources.
A side-by-side editorial comparison of contentanalysis and Lightdash — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | contentanalysis | Lightdash |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 0.0 | 7.5 |
| Sparks · 30d | 0 | 2 |
| Top themes | text-analysis, bibliometrics, scientific-writing, r-package | business-intelligence, ai-agents, content-as-code, developer-experience |
| Last editorial update | 3d ago | 4h ago |
| Website | Visit → | — |
A scientific-text analysis package moved from counting citations to classifying argument structure.
contentanalysis parses scientific papers from PDF and analyses their content — citation clustering, reference extraction and matching, word distribution, TF-IDF summaries by section. The most recent release adds a different kind of analysis: sentence-level classification of rhetorical moves, built on Swales' CARS model and extended to literature review and discussion sections, using rules by default with an optional Google Gemini path. PDF handling has been reworked in parallel for multi-column layouts and running header removal.
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.
contentanalysis parses scientific papers from PDF and analyses their content — citation clustering, reference extraction and matching, word distribution, TF-IDF summaries by section. The most recent release adds a different kind of analysis: sentence-level classification of rhetorical moves, built on Swales' CARS model and extended to literature review and discussion sections, using rules by default with an optional Google Gemini path. PDF handling has been reworked in parallel for multi-column layouts and running header removal.
The arc runs from surface features toward discourse structure. Early releases were about getting references matched correctly and plots readable; the current one asks what function each sentence performs in the argument, which is a categorically harder question and one the package answers with rules first and a language model second. The optional-LLM design is worth noting for what it avoids — the analysis still runs without an API key, and the package has already had to prune retired Gemini model versions once, which is the maintenance cost of depending on a hosted model. Reference parsing is being made format-aware rather than pattern-guessing, with CrossRef enrichment filling in what the PDF omits.
Expect the rhetorical move classification to widen to more section types and the rule-based path to keep being the default, given the package has already been forced to track model deprecations on the optional one.
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 contentanalysis 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
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 contentanalysis 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 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 contentanalysis alternatives in Analytics are ranked by recent ship velocity. Browse the "contentanalysis alternatives" section above for the current picks, or visit /alternatives/contentanalysis 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.