Dovetail
Dovetail lets admins choose which connectors members can plug into the workspace.
Comparison · Analytics
June vs OpenMetadata
A side-by-side editorial comparison of June and OpenMetadata — release velocity, themes, recent moves, and the top alternatives to consider.
June vs OpenMetadata: at a glance
| Feature | June | OpenMetadata |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 7.5 | 5.0 |
| Sparks · 30d | 0 | 0 |
| Top themes | product analytics, b2b saas, computed traits, custom objects | data-catalog, lineage, connectors, data-quality |
| Last editorial update | 6mo ago | 4h 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 OpenMetadata?
OpenMetadata 2.0.8 widens Hex, Sigma and BigQuery coverage while 2.1 waits in release candidates.
OpenMetadata is still in 2.0.x maintenance mode, shipping a release every one to two weeks. 2.0.8 on November 13 is the broadest yet: Hex and Sigma ingestion now build data models and column lineage, BigQuery date-sharded tables can be grouped into one logical table, Power BI and Snowflake ingestion stop leaving stale or runaway jobs, and MCP authentication and access controls were tightened. The 2.1.0 line sits at rc2, whose only published change is a tag-resolution fix.
June vs OpenMetadata: 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.
OpenMetadata
5.0ANALYTICS
OpenMetadata 2.0.8 widens Hex, Sigma and BigQuery coverage while 2.1 waits in release candidates.
◆ Current state
OpenMetadata is still in 2.0.x maintenance mode, shipping a release every one to two weeks. 2.0.8 on November 13 is the broadest yet: Hex and Sigma ingestion now build data models and column lineage, BigQuery date-sharded tables can be grouped into one logical table, Power BI and Snowflake ingestion stop leaving stale or runaway jobs, and MCP authentication and access controls were tightened. The 2.1.0 line sits at rc2, whose only published change is a tag-resolution fix.
◆ Where it's heading
Each 2.0.x release repairs connectors and lineage that 2.0 left incomplete, and the fixes increasingly touch accuracy (correct table identity, lineage that ends at the right model) rather than crashes. MCP keeps appearing in the security sections, which suggests OpenMetadata expects AI tools to read the catalog and is locking that path down before 2.1.
◆ Prediction
A 2.1.0 final is the next visible step, since two release candidates are out; the entries do not yet say what features 2.1 adds beyond the fixes backported to 2.0.x.
Alternatives to June and OpenMetadata
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 OpenMetadata.
Dagster
Dagster drops Python 3.10 and lets agents run schedules and sensors through MCP.
OpenHouse
OpenHouse adds time-zone-aware retention and per-database table caps.
Countly
Countly 25.03.59 defaults to Node 26, supports MongoDB 9 and tightens app scoping.
Kubecost
Kubecost cuts three 3.3.2 release candidates in two days, still without notes.
RStudio
RStudio opens the 2026.11 train with another NOTICE file update.
See all June alternatives → · See all OpenMetadata alternatives →
Recent activity from June and OpenMetadata
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 21h agoOpenMetadata2.0.8: Hex and Sigma lineage, BigQuery shard grouping, MCP auth
- 23h agoOpenMetadata2.1.0 rc2: fix for tags removed when resolving tag tasks
- 14d agoOpenMetadata2.1.0 rc1 appears, with notes covering only a UI fix
- 17d agoOpenMetadata2.0.7: Pub/Sub, SQL Server and Unity Catalog connector fixes
- 23d agoOpenMetadata2.0.6: ingestion accuracy, safer upgrades, multi-pod fixes
- 1mo agoOpenMetadata2.0.5 restores metadata lost to 2.0 ingestion regressions
- 6mo agoJuneCustom objects available for all ⚡
- 6mo agoJuneSQL computed traits ⚡
- 6mo agoJuneIncreased computed traits limits
- 6mo agoJuneUse PostHog as a data source
- 1y agoJuneCustom objects GA (duplicate feed entry)
- 1y agoJuneCustom objects GA (duplicate feed entry)
Frequently asked questions
What is the difference between June and OpenMetadata?
They serve adjacent needs but don't currently overlap on shipped themes. June is currently shipping more aggressively (velocity 7.5 vs 5.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is June better than OpenMetadata?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. June is currently shipping more aggressively (velocity 7.5 vs 5.0), with 0 editorial sparks in the last 30 days against 0. 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 OpenMetadata?
Top OpenMetadata alternatives in Analytics are ranked by recent ship velocity. Browse the "OpenMetadata alternatives" section above for the current picks, or visit /alternatives/openmetadata for the full list with editorial commentary on each.