OpenHouse
OpenHouse is hardening the seams where table policies and jobs quietly fail.
Comparison · Analytics
dbt Core vs shiny
A side-by-side editorial comparison of dbt Core and shiny — release velocity, themes, recent moves, and the top alternatives to consider.
dbt Core vs shiny: at a glance
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 shiny?
Shiny made reactive apps observable, then gave them a way to tear themselves down
Version 1.12.0 added OpenTelemetry support through the {otel} package, emitting spans for session start and end, reactive updates and individual reactive expressions, with collection depth set by an option or environment variable. The releases since have refined it - scoped collection controls in 1.12.1, cleaner stack traces in 1.13.0 - while 1.14.0 turned to lifecycle, adding session$destroy() on module proxies and a non-blocking startApp() for driving apps programmatically.
dbt Core vs shiny: 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.
shiny
0.0ANALYTICS
Shiny made reactive apps observable, then gave them a way to tear themselves down
◆ Current state
Version 1.12.0 added OpenTelemetry support through the {otel} package, emitting spans for session start and end, reactive updates and individual reactive expressions, with collection depth set by an option or environment variable. The releases since have refined it - scoped collection controls in 1.12.1, cleaner stack traces in 1.13.0 - while 1.14.0 turned to lifecycle, adding session$destroy() on module proxies and a non-blocking startApp() for driving apps programmatically.
◆ Where it's heading
The framework is addressing the two things that make Shiny apps hard to run in production: you could not see inside the reactive graph, and you could not reliably dispose of parts of it. Tracing answers the first; scoped destruction of module session proxies answers the second. Both are aimed at long-lived, dynamically composed apps rather than at the single-file demo.
◆ Prediction
Expect the OpenTelemetry attribute names to settle once the deprecated spellings are dropped, and more of the reactive lifecycle to gain explicit teardown hooks now that session$destroy() has established the pattern. Editor integration is a likely area for follow-up after the Ark breakpoint support.
Alternatives to dbt Core and shiny
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 shiny.
silx
silx 3.0 moved its default Qt binding to PySide6 — a migration for everyone embedding it.
statsmodels
statsmodels ships only what the ecosystem breaks — six releases, no new statistics.
StatsBase.jl
StatsBase.jl is in caretaker mode — correctness fixes in, dependency bumps out.
iris
Iris ships steadily on a two-a-year cadence, but its feed publishes only pointers.
ggplot2
ggplot2 swapped its object system out from under a decade of downstream code
See all dbt Core alternatives → · See all shiny alternatives →
Recent activity from dbt Core and shiny
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agodbt Coredbt Fusion 2.0 reaches first beta with catalog-free SQL binding ⚡
- 23d 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
- 1mo agoshinyModule scopes gain session$destroy() for reactive teardown
- 5mo agoshinyInteractive breakpoints under Ark; cleaner render stack traces
- 8mo agoshinyScoped OpenTelemetry collection controls
- 8mo agoshinyShiny adds OpenTelemetry tracing of the reactive graph ⚡
- 1y agoshinyRegression fixes for input bindings and label updates
- 1y agoshinyAuto-reload covers modules and support files
Frequently asked questions
What is the difference between dbt Core and shiny?
They serve adjacent needs but don't currently overlap on shipped themes. dbt Core is currently shipping more aggressively (velocity 7.5 vs 0.0), with 2 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 shiny?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. dbt Core is currently shipping more aggressively (velocity 7.5 vs 0.0), with 2 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 shiny?
Top shiny alternatives in Analytics are ranked by recent ship velocity. Browse the "shiny alternatives" section above for the current picks, or visit /alternatives/r-shiny for the full list with editorial commentary on each.