Fulcrum
Fulcrum is consolidating on Esri, with Google Maps gone September 1
Comparison · Analytics
dbt Core vs June
A side-by-side editorial comparison of dbt Core and June — release velocity, themes, recent moves, and the top alternatives to consider.
dbt Core vs June: at a glance
| Feature | dbt Core | June |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 7.5 | 7.5 |
| Sparks · 30d | 2 | 0 |
| Top themes | dbt-fusion, rust-rewrite, static-analysis, semantic-layer | product analytics, b2b saas, computed traits, custom objects |
| Last editorial update | 1d ago | 3mo ago |
| Website | Visit → | — |
What is dbt Core?
The Rust rewrite crosses from alpha to beta, and it can now bind SQL without touching the warehouse.
dbt is running two release lines at once. The 1.x Python line reached 1.12.0 in July, a GA that removed the experimental dbt login command and the bundled dbt-state plugin outright while adding the v2 semantic layer YAML parsing. The 2.0 Fusion line — the Rust engine — moved through five alphas and reached its first beta on August 10, carrying catalog-free binding, dbt state explain, redundant-test skipping, and a lint rule system that understands node selection.
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.
dbt Core vs June: editorial side-by-side
dbt Core
7.5ANALYTICS
The Rust rewrite crosses from alpha to beta, and it can now bind SQL without touching the warehouse.
◆ Current state
dbt is running two release lines at once. The 1.x Python line reached 1.12.0 in July, a GA that removed the experimental dbt login command and the bundled dbt-state plugin outright while adding the v2 semantic layer YAML parsing. The 2.0 Fusion line — the Rust engine — moved through five alphas and reached its first beta on August 10, carrying catalog-free binding, dbt state explain, redundant-test skipping, and a lint rule system that understands node selection.
◆ Where it's heading
Fusion is being built to do statically what dbt-core did by asking the warehouse. Catalog-free binding lets SQL bind without introspection, tests get skipped when they are provably redundant, and dbt State speculatively submits nodes while the dependency prefetch is still in flight — all of it trading round-trips for compile-time analysis. Meanwhile 1.x is absorbing the v2 semantic layer YAML piece by piece, which puts metrics and entities into the model graph itself. Adapter breadth keeps widening in parallel, with Databricks service principal auth, Redshift group grants, and ClickHouse materialization configs.
◆ Prediction
With beta.1 out, the next milestones are further betas hardening the Fusion feature set toward parity, and continued v2 semantic YAML work landing in the 1.x line.
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.
Alternatives to dbt Core and June
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 dbt Core or June.
Omni
Omni ships weekly, and almost every week the headline item is an AI feature
OpenDataDiscovery
Four ODD Platform releases in two weeks, and not one of them changes the product
Apache Baremaps
Baremaps got geoparquet and hillshading, then went quiet for eighteen months in incubation
Deequ
Deequ ships GitHub tags whose release notes are one commit message long
Marquez
Marquez spent 2024 turning a lineage store into a UI, then stopped releasing
See all dbt Core alternatives → · See all June alternatives →
Recent activity from dbt Core and June
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agodbt Coredbt Fusion 2.0 reaches first beta with catalog-free SQL binding ⚡
- 22d agodbt Corev2.0.0-alpha.5
- 26d agodbt Coredbt-core v1.12.0 ⚡
- 28d agodbt Coredbt-core v1.12.0rc3
- 1mo agodbt Coredbt-core v1.12.0rc2
- 1mo agodbt Coredbt-core v1.12.0rc1
- 3mo agoJuneCustom objects available for all ⚡
- 3mo agoJuneSQL computed traits ⚡
- 3mo agoJuneIncreased computed traits limits
- 3mo 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 dbt Core and June?
They serve adjacent needs but don't currently overlap on shipped themes. dbt Core and June are shipping at a similar cadence (velocity 7.5 vs 7.5, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is dbt Core better than June?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. dbt Core and June are shipping at a similar cadence (velocity 7.5 vs 7.5, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
What are the best alternatives to dbt Core?
Top dbt Core alternatives in Analytics are ranked by recent ship velocity. Browse the "dbt Core alternatives" section above for the current picks, or visit /alternatives/dbt-core for the full list with editorial commentary on each.
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.