June vs Hex
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.
Hex is reframing the notebook as a prompt-driven app builder and an agent that reaches into your stack.
Hex started as a collaborative data notebook and is now rebuilding around its AI agent. The recent stream is dominated by generative capabilities: building data apps from a prompt, agent context drawn from repos and connected systems, and agentic visualization. The classic notebook is still there, but the headline surface is increasingly 'describe what you want' rather than 'write the cells.'
Two reinforcing moves define the direction. Hex is turning analytics artifacts into things you generate from natural language, and it is wiring its agent into the surrounding toolchain as an MCP client and through external surfaces. The bet is that the unit of work shifts from notebooks people author to apps and answers the agent assembles, with humans steering context and review.
Expect Hex to keep expanding what the agent can build and where it can pull context from, pushing generative data apps from a feature toward the default way work starts.
See more alternatives to June →
See more alternatives to Hex →