Apify vs Lightdash
Side-by-side trajectory, velocity, and editorial themes.
Web-scraping platform is reshaping itself around AI agents — MCP, permissions, and OpenAPI surfaces.
Apify continues to optimize for AI-agent consumption. Recent shipments include interactive OpenAPI documentation for standby Actors with auto-attached API tokens, an approval modal for full-permission Actors (least-privileged defaults), multiple datasets per Actor for cleaner output structure, and a redesigned MCP configurator covering Claude Desktop, Claude.ai, Claude Code, Antigravity, Cursor, ChatGPT, Codex, and VS Code. The mcpc universal MCP CLI client and Dynamic Actor memory rounded out the prior month.
Apify is converging on a single thesis: be the scraping and Actor execution infrastructure that AI agents call into. Every recent release either improves how agents discover and run Actors (MCP configurator, OpenAPI Endpoints tab, mcpc CLI) or hardens what happens when they do (full-permission approvals, dataset structure, dynamic memory). The product is no longer marketing itself primarily as scraping — it's marketing itself as agent-callable web automation.
Expect tighter cost-attribution and audit trails for agent-initiated runs, more nuanced permission scopes, and continued expansion of supported MCP-aware client editors. Standby Actors as a deployment model are likely to see more first-class support — they're a natural fit for agent-callable APIs.
Lightdash chips away at the SQL barrier with NL-to-formula table calcs and metric-tree visualization.
The release cadence is high and the work spans three areas: lowering the technical barrier (spreadsheet-style formulas in table calculations, plain references to grand totals), enriching what a chart and dashboard can express (color palettes at every scope, row/column limits, rich-text table cells), and self-serve operability (default user spaces, expiring preview projects, dashboard-version rollbacks that include chart configs). The Canvas now hosts persistent metric trees, hinting at a heavier semantic-layer story.
Lightdash is positioning between a dbt-native semantic layer (where SQL-fluent analysts live) and a self-serve BI tool (where business users live). The intent-driven formula editor and reference-total functions chip away at the SQL prerequisite for table calculations, while Saved Trees push the metric model into something visually editable. Underneath, the platform is doing the unglamorous self-serve work — personal spaces, palette hierarchies, preview hygiene — that BI products need to survive in larger orgs.
Expect the formula editor to grow into broader AI-assisted authoring (filters, joins, custom dimensions) and Saved Trees to evolve into a more general semantic-layer view that consumes from dbt and produces governance artifacts. Color and palette work suggests embedded/customer-facing BI ambitions next.
See more alternatives to Apify →
See more alternatives to Lightdash →