RStudio
RStudio's first October patch is a branch merge, extending a long run of release-train upkeep.
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 | 6.3 | 7.5 |
| Sparks · 30d | 0 | 0 |
| Top themes | fusion-migration, v2-transition, semantic-layer, adapters | product analytics, b2b saas, computed traits, custom objects |
| Last editorial update | 14d ago | 5mo ago |
| Website | Visit → | — |
What is dbt Core?
dbt's 1.x releases now point users at v2 straight from the command line.
dbt 2.0 GA split the project into a proprietary 'dbt' binary and dbt-oss, and the 2.0 dev channel has since added read-only Databricks Unity Catalog access through Lake Compute. The 1.x line is still shipping: 1.13.0b1 adds an opt-in --use-v2-parser that hands parsing to the Fusion parser, and today's 1.12.6 prints a v2 availability notice on dbt --version and relays Fusion parser logs through the otel log format.
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
6.3ANALYTICS
dbt's 1.x releases now point users at v2 straight from the command line.
◆ Current state
dbt 2.0 GA split the project into a proprietary 'dbt' binary and dbt-oss, and the 2.0 dev channel has since added read-only Databricks Unity Catalog access through Lake Compute. The 1.x line is still shipping: 1.13.0b1 adds an opt-in --use-v2-parser that hands parsing to the Fusion parser, and today's 1.12.6 prints a v2 availability notice on dbt --version and relays Fusion parser logs through the otel log format.
◆ Where it's heading
The 1.x branch is being turned into an on-ramp for v2: a PyPI banner in 1.12.5, a CLI notice in 1.12.6, deprecated-version warnings and the Fusion parser opt-in in 1.13. Meanwhile 2.0 work concentrates on adapter parity (ClickHouse, Databricks) and Lake Compute.
◆ Prediction
Expect 1.13 to reach GA with the v2 parser opt-in and more migration prompts, and 2.0.x to extend Lake Compute past read-only Unity access. The entries don't show an end-of-life date for 1.x.
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.
OpenReplay
OpenReplay moves its Go backend to pgx v5 and patches vulnerable deps across 1.25–1.27.
Basedash
Basedash automations can now attach scheduled CSV exports to Slack and email.
OpenPanel
OpenPanel tags three more note-free builds in one evening, reaching 3.16.4.
Fulcrum
Fulcrum turns on Insights, its AI assistant for field data, for every customer.
Holistics
Holistics lets admins put a key dashboard on everyone's Home page.
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.
- 15d agodbt Coredbt 1.12.6 points users to v2 and fixes Fusion parser logging
- 15d agodbt Coredbt 1.11.16 fixes nested wildcard selectors, adds tarball path check
- 15d agodbt Coredbt-core 1.13 beta adds opt-in Fusion parser and dbt login
- 1mo agodbt CoreLake Compute gains Databricks Unity Catalog read access
- 1mo agodbt Coredbt v2.0.0 ⚡
- 1mo agodbt Coredbt v1.12.5
- 5mo agoJuneCustom objects available for all ⚡
- 5mo agoJuneSQL computed traits ⚡
- 5mo agoJuneIncreased computed traits limits
- 5mo 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. June is currently shipping more aggressively (velocity 7.5 vs 6.3), 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 dbt Core better than June?
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 0. 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.