Maze vs June
Side-by-side trajectory, velocity, and editorial themes.
UX research platform is reshaping itself around AI moderation and AI-driven analysis.
Maze is shipping aggressively across two adjacent fronts: AI-driven research execution (AI Moderator with adaptive conversation styles, visual stimulus support) and AI-driven analysis (thematic analysis now generated automatically across every study type). Around the AI core, recent releases also tighten panel recruitment with Fresh Eyes participant-freshness controls, expand Global Search to blocks and interview sessions, and improve Variant Comparison reliability for A/B prototype tests.
The product is moving from 'research tool researchers operate' to 'research platform that runs and interprets studies on the researcher's behalf'. AI Moderator handles unmoderated conversation; AI thematic analysis turns transcripts into highlights without a researcher manually coding. The core wager is that the analysis bottleneck — not study design — is what limits the volume of research a team can do, and Maze is going after that bottleneck directly.
Expect AI Moderator to keep absorbing more interview style options and stimulus types, and the analysis side to push from theme-extraction toward auto-generated synthesis or report drafts. Panel-quality controls like Fresh Eyes are likely to expand into broader participant-cohort management.
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 Maze →
See more alternatives to June →