Sigma Computing vs June
Side-by-side trajectory, velocity, and editorial themes.
Sigma builds out the agentic analytics stack: workflow automation, Snowflake Cortex bindings, and a push beyond read-only dashboards.
Sigma is leaning hard into agentic analytics positioning. Recent shipments — Automated Actions for scheduled workflows, Sigma Skills accessible inside Snowflake Cortex Code, and bidirectional JavaScript events for embedded analytics — combine into a story about analytics that act and integrate, not just visualize. Concurrent thought-leadership pieces reinforce the messaging that read-only dashboards are insufficient for modern enterprise AI.
The platform is converging analytics, AI agents, and Snowflake-native tooling into a single operating layer. Investments are flowing toward workflows that trigger actions on schedule (and likely on events next), tighter Cortex integration so data engineers stay inside Snowflake, and embedded analytics primitives that let host apps surface and react to in-Sigma activity. The Gartner agentic AI mention is being amplified to support sales positioning into 2026 enterprise budgets.
Expect Sigma to add event-driven triggers and broader agent tool-calling to Automated Actions, and to deepen the Cortex bridge so a Snowflake developer can author and govern Sigma workbooks/data models without leaving the warehouse environment.
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 Sigma Computing →
See more alternatives to June →