broom.helpers
After eleven quiet months, the tidier under gtsummary is back to absorbing model classes.
A side-by-side editorial comparison of AgencyAnalytics and Lightdash — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | AgencyAnalytics | Lightdash |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 6.3 | 7.5 |
| Sparks · 30d | 1 | 2 |
| Top themes | agency-reporting, ai-assistant, skills, integrations | business-intelligence, ai-agents, content-as-code, developer-experience |
| Last editorial update | 4d ago | 3d ago |
| Website | Visit → | — |
AgencyAI got skills three weeks ago; everything since has been making them routine.
The cadence is weekly and heavily weighted toward AgencyAI. Skills landed in early August as named, runnable agency tasks; scheduling followed, so those tasks now run on their own. Around the assistant, the reporting surface keeps widening: advanced filtering on custom metrics and KPIs, client tags, a report shares view, and a MailerLite data source that brings email campaign metrics alongside every other channel.
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.
The cadence is weekly and heavily weighted toward AgencyAI. Skills landed in early August as named, runnable agency tasks; scheduling followed, so those tasks now run on their own. Around the assistant, the reporting surface keeps widening: advanced filtering on custom metrics and KPIs, client tags, a report shares view, and a MailerLite data source that brings email campaign metrics alongside every other channel.
The assistant is being moved from something an operator invokes to something that runs on a schedule against connected client data, which changes it from a feature into part of the reporting pipeline. The integration work continues at its usual pace and serves the same end — the more channels are connected, the more a scheduled skill has to reason over. Filtering and tagging are the plumbing that lets those tasks be scoped to the right accounts.
Expect scheduled skills to gain delivery — results pushed into reports or sent to clients — rather than staying inside the assistant panel.
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 AgencyAnalytics or Lightdash.
After eleven quiet months, the tidier under gtsummary is back to absorbing model classes.
OpenHouse starts adding per-column defaults while still closing silent-failure holes.
Julia's distribution library keeps filing down the edges where sampling meets array types
Power BI's monthly grind: authoring defaults, DAX documentation, and mobile finally catching up.
ggquiver is awake again, fixing arrow scaling that quietly misread irregular data.
A lazy vector container keeps closing the gaps where it quietly materialised anyway.
See all AgencyAnalytics 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 6.3), with 2 editorial sparks in the last 30 days against 1. 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 6.3), with 2 editorial sparks in the last 30 days against 1. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top AgencyAnalytics alternatives in Analytics are ranked by recent ship velocity. Browse the "AgencyAnalytics alternatives" section above for the current picks, or visit /alternatives/agencyanalytics 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.