June vs Lightdash
Side-by-side trajectory, velocity, and editorial themes.
June's last visible push was a tight May 2025 B2B sprint — Custom Objects, SQL traits, PostHog integration.
June is product analytics for B2B SaaS, and the only visible release activity in the input is a concentrated four-week sprint in May 2025: SQL computed traits, PostHog as a data source, increased computed-trait limits, and the GA of Custom Objects after a two-month rollout. Each release is paired with small fixes (Slack alerts, HubSpot reverse sync) suggesting a stable maintenance cadence around the headline launches.
The May 2025 batch is internally consistent: every release widens what June can model (Custom Objects), how flexibly customers can compute on it (SQL traits), or how easily it slots into existing data plumbing (PostHog source). All three target the B2B-SaaS persona that wants more than user/account analytics. After this burst the changelog goes quiet in the input — it's not clear from the entries alone whether the product moved to a slower cadence, switched publishing channels, or paused.
The entries don't support a confident prediction about what comes next. If publishing resumes from the same direction, the obvious extensions are deeper integrations with reverse-ETL or warehouse-native sources and richer pre-built health-score templates on top of SQL computed traits.
Lightdash widens its surface with admin tooling, governance, and intent-driven formulas.
Lightdash is shipping in three directions at once: operator tools (user impersonation with audit + 15-min cap, auto-expiring preview projects), authoring polish (row/column limits, color palette hierarchy, saved metric trees), and a step into AI-assisted authoring with spreadsheet-style formulas where the editor infers intent. The pace is fast — multiple releases per week — and the changes are mostly visible to working analysts.
The throughline is reducing how much SQL and YAML an analyst needs to touch: formulas in plain English, filters that read user attributes from the UI, rollback that includes chart configs, color governance that doesn't require code. Lightdash is pushing the surface area an analyst manages out of files and into the product, then layering controls (audit-logged impersonation, palette precedence) for the orgs that need governance.
Expect intent-driven authoring to widen beyond table calculations — likely metric definitions and dbt model suggestions next — and for the metric-tree canvas to become a planning surface, not just a visualization. Governance features (impersonation, audit) will likely consolidate into an enterprise tier.
See more alternatives to June →
See more alternatives to Lightdash →