Apache Superset
Superset's 6.1.0 release vote grinds on while Helm packaging ships on its own cadence
Comparison · Analytics
June vs Count
A side-by-side editorial comparison of June and Count — release velocity, themes, recent moves, and the top alternatives to consider.
June vs Count: at a glance
| Feature | June | Count |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 7.5 | 6.3 |
| Sparks · 30d | 0 | 1 |
| Top themes | product analytics, b2b saas, computed traits, custom objects | agentic-analytics, mcp, public-api, warehouse-connectors |
| Last editorial update | 1mo ago | 1d ago |
| Website | — | Visit → |
What is June?
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.
What is Count?
Count is turning its BI canvas into a governed, agent-operated analytics platform.
Count is a data-canvas analytics tool reorganizing itself around an AI agent. In two months it shipped a full public REST API and hosted MCP server (governed agent access via OAuth and service accounts), a major agent upgrade that lets the agent read and edit the entire canvas and answer from Slack, and the ability to plug external MCP servers (Linear, HubSpot, Stripe, Slack, Drive) into the agent. Around the agent it keeps broadening warehouse support—ClickHouse, Snowflake semantic models, OSI—alongside chart and UX polish.
June vs Count: editorial side-by-side
June
7.5ANALYTICS
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.
Count
6.3ANALYTICS
Count is turning its BI canvas into a governed, agent-operated analytics platform.
◆ Current state
Count is a data-canvas analytics tool reorganizing itself around an AI agent. In two months it shipped a full public REST API and hosted MCP server (governed agent access via OAuth and service accounts), a major agent upgrade that lets the agent read and edit the entire canvas and answer from Slack, and the ability to plug external MCP servers (Linear, HubSpot, Stripe, Slack, Drive) into the agent. Around the agent it keeps broadening warehouse support—ClickHouse, Snowflake semantic models, OSI—alongside chart and UX polish.
◆ Where it's heading
Count is building toward analytics where agents are first-class operators: a governed API/MCP layer for access, an agent that drives the canvas end to end, external tool reach via MCP, and connection-level context so guidance is captured once and inherited. Governance—permissions, scopes, service accounts—is the enabling layer that makes agent access acceptable in real data stacks rather than a bolt-on.
◆ Prediction
Expect more connection- and warehouse-level context controls, a widening catalog of supported external MCP integrations, and deeper Slack-native agent workflows.
Alternatives to June and Count
Other Analytics products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either June or Count.
Usermaven
Usermaven consolidates its scattered analyses into one Analytics Hub workspace
Zoho Analytics
A mature BI platform positioning itself as the data-and-semantic foundation for AI agents across the Zoho suite.
Holistics
Holistics leans into analytics-as-code with agentic dev workflows and a Power BI migration path
Axiom
Axiom completes the logs-traces-metrics triad and bets the product on AI engineering.
NocoDB
NocoDB keeps converging the database, the document, and the project plan into one workspace.
Recent activity from June and Count
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 5d agoCountConnect external MCP servers to the Count agent ⚡
- 19d agoCountDashed lines
- 1mo agoCountNew workspace home
- 1mo agoJuneCustom objects available for all ⚡
- 1mo agoJuneSQL computed traits ⚡
- 1mo agoJuneIncreased computed traits limits
- 1mo agoJuneUse PostHog as a data source
- 1mo agoCountClickHouse support
- 2mo agoCountMajor Count agent upgrade: edits any cell, runs in Slack ⚡
- 2mo agoCountPublic API and MCP server ⚡
- 1y agoJuneCustom objects GA (duplicate feed entry)
- 1y agoJuneCustom objects GA (duplicate feed entry)
Frequently asked questions
What is the difference between June and Count?
They serve adjacent needs but don't currently overlap on shipped themes. June is currently shipping more aggressively (velocity 7.5 vs 6.3), with 0 editorial sparks in the last 30 days against 1. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is June better than Count?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. June is currently shipping more aggressively (velocity 7.5 vs 6.3), with 0 editorial sparks in the last 30 days against 1. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
What are the best alternatives to June?
Top June alternatives in Analytics are ranked by recent ship velocity. Browse the "June alternatives" section above for the current picks, or visit /alternatives/june for the full list with editorial commentary on each.
What are the best alternatives to Count?
Top Count alternatives in Analytics are ranked by recent ship velocity. Browse the "Count alternatives" section above for the current picks, or visit /alternatives/count for the full list with editorial commentary on each.