Holistics vs June
Side-by-side trajectory, velocity, and editorial themes.
Holistics turns the BI dashboard into a conversational AI surface, on customer-owned models.
Holistics is well into a BI-meets-AI productization phase, layering conversational analytics on top of its existing modeling and dashboard core. Recent releases mix consumer-grade dashboard polish (auto-run filters, K/M/B number formatting, percentile calculations) with deeper AI plumbing: bring-your-own Claude and Gemini keys, per-user AI access controls, and now an Ask AI that asks clarifying questions back. The GitHub App integration also signals enterprise-readiness work alongside the AI push.
The product is being repositioned from a self-service BI tool to an AI-mediated analytics workspace where natural-language exploration is the headline interaction. Crucially, the team is pushing AI as an infrastructure layer customers can own — BYO LLM keys, granular access policies — rather than locking customers into a vendor-managed model. The dashboard improvements look incremental, but read as ground prep for AI agents to consume and manipulate dashboards more reliably.
Expect the next quarter to bring agentic dashboard editing — Ask AI not just answering but proposing dashboards and saving them — plus expanded BYO LLM coverage (likely Azure OpenAI or open-weights via OpenRouter) to widen procurement options for enterprise buyers.
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.
See more alternatives to Holistics →
See more alternatives to June →