← Back to home
Comparison · Analytics

Hex vs June

Side-by-side trajectory, velocity, and editorial themes.

H
Hex
ANALYTICS
6.3

Hex bets the product on prompt-as-authoring: data apps are now one sentence away.

◆ Current state

Hex is in the most aggressive AI-agent build-out of any analytics tool we track. The last month has stacked: repo connections as agent context, Generative Data Apps, prompt-to-dashboard, context suggestions, user memory, projects-as-context, and a CLI for programmatic context control. Around it, the surface has been extended with Hex-in-Claude, Hex-in-Cursor, a ClickHouse partnership, and Google Sheets export.

◆ Where it's heading

Hex is reorganizing itself around an agent that the user steers with prompts and grounds with context. Each release adds either more context channels (repos, projects, semantic models, memory, guides) or more places the agent can act (apps, dashboards, third-party clients). The product surface is being recast: notebooks remain, but the primary entry point is becoming the prompt. Expect Hex to keep stacking context sources and to start moving from authoring assist into autonomous, scheduled, agent-driven workflows.

◆ Prediction

Next plausible moves: agent-authored scheduled jobs or alerts, deeper integrations with semantic layer tools (dbt-style metric stores) as context sources, and more co-pilot embeddings in third-party editors. A pricing tier tied to agent usage is increasingly hard to delay.

J
June
ANALYTICS
7.5

June's last visible push was a tight May 2025 B2B sprint — Custom Objects, SQL traits, PostHog integration.

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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 Hex
See more alternatives to June