Tautulli
Plex's analytics companion has spent a year shipping CVE fixes faster than features.
Comparison · Analytics
dbt Core vs Countly
A side-by-side editorial comparison of dbt Core and Countly — release velocity, themes, recent moves, and the top alternatives to consider.
dbt Core vs Countly: at a glance
What is dbt Core?
Two engines in one repo: the Python 1.x line tightens while Fusion 2.0 goes lakehouse-catalog native
dbt-core is releasing on two tracks at once. The Python line reached 1.12.0 on 16 July after three release candidates, and it is a tightening release: the experimental `dbt login` command and the bundled dbt-state plugin were removed outright, and flags introduced in 1.9 and 1.10 now default to true. The 2.0.0 alpha track is the Fusion engine, and its work is almost entirely about catalogs — read-write Horizon and Unity access over Iceberg REST via DuckDB, a catalogs.yml v2 covering DuckLake, Iceberg REST and local filesystem, plus catalog_database overrides and Redshift catalog generation through SHOW TABLES and SVV_REDSHIFT_COLUMNS.
What is Countly?
Countly's core is in maintenance while every real feature lands in the enterprise journey engine.
Countly runs two parallel release trains — the 24.05 LTS line and the current 25.03 line — and ships the same fixes into both, often on the same day. Almost every entry in the last two months is a bugfix list; the exceptions are enterprise-only additions to the journey engine, data manager, and block plugin. A security-hardening release in May cleaned up query injection, path traversal, and mass-assignment across app_users, alerts, and apps.
dbt Core vs Countly: editorial side-by-side
dbt Core
7.5ANALYTICS
Two engines in one repo: the Python 1.x line tightens while Fusion 2.0 goes lakehouse-catalog native
◆ Current state
dbt-core is releasing on two tracks at once. The Python line reached 1.12.0 on 16 July after three release candidates, and it is a tightening release: the experimental `dbt login` command and the bundled dbt-state plugin were removed outright, and flags introduced in 1.9 and 1.10 now default to true. The 2.0.0 alpha track is the Fusion engine, and its work is almost entirely about catalogs — read-write Horizon and Unity access over Iceberg REST via DuckDB, a catalogs.yml v2 covering DuckLake, Iceberg REST and local filesystem, plus catalog_database overrides and Redshift catalog generation through SHOW TABLES and SVV_REDSHIFT_COLUMNS.
◆ Where it's heading
The division of labour between the two tracks is clear from the entries: 1.x is consolidating and removing experiments, while 2.0 is where the new surface area lands. The 2.0 surface is specifically the lakehouse catalog layer — dbt is moving from a tool that writes to a warehouse toward one that binds to open table catalogs directly, with materialization made catalog-aware. Notably 1.12.0rc1 also teaches the Python engine to tolerate Fusion-specific warn_error_options rather than erroring, so the two engines are being made to coexist in the same projects rather than fork.
◆ Prediction
The alphas are still expanding catalog coverage adapter by adapter, so expect further catalog integrations and continued catalogs.yml v2 work before 2.0 leaves alpha. On the Python side, with the deprecated flags now defaulted and the experimental commands removed, 1.12 looks like a stabilization point rather than a base for new features.
Countly
5.0ANALYTICS
Countly's core is in maintenance while every real feature lands in the enterprise journey engine.
◆ Current state
Countly runs two parallel release trains — the 24.05 LTS line and the current 25.03 line — and ships the same fixes into both, often on the same day. Almost every entry in the last two months is a bugfix list; the exceptions are enterprise-only additions to the journey engine, data manager, and block plugin. A security-hardening release in May cleaned up query injection, path traversal, and mass-assignment across app_users, alerts, and apps.
◆ Where it's heading
The open analytics core is being kept stable rather than extended, and the product's forward motion has moved into the enterprise marketing-automation layer. Journey engine work in particular reads like a system being taken seriously in production: user-merge remapping so running journeys survive identity resolution, approver groups wired into LDAP and Active Directory, dynamic parameters in deeplinks. Data manager transformations and event-key edge cases keep resurfacing, which suggests the ingestion-side data model is where the operational pain is.
◆ Prediction
Expect the next releases to continue the same split — fixes backported across both trains, with new capability confined to journey engine and data manager on the enterprise tier.
Alternatives to dbt Core and Countly
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 Countly.
Delta Lake
Delta Lake is handing table authority to Unity Catalog — under a feed buried in Databricks build tags.
OpenCTI
OpenCTI ships weekly and is rebuilding its connector catalog into a marketplace.
Grafana Mimir
Mimir's feed is mostly bot-authored Helm bumps; the real release is 3.2, and it is query-engine work.
Fluent Bit
Fluent Bit runs a 4.2 and a 5.0 train side by side, both fed by the same backport pipeline.
Omni
Omni ships weekly, and this quarter every week added something to the AI layer.
See all dbt Core alternatives → · See all Countly alternatives →
Recent activity from dbt Core and Countly
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 1d agoCountlyFixes for event keys containing special characters
- 1d agoCountlyJourney deeplinks take dynamic parameters; hooks validated on save
- 11d agoCountlyStar-rating logo path and data-manager transformation fixes
- 12d agoCountlyLTS backport: data-manager transformation fix
- 15d agodbt CoreFusion alpha 5: Redshift datasharing catalogs and job-specific deferral
- 18d agodbt Coredbt-core 1.12.0 drops `dbt login` and the dbt-state plugin ⚡
- 20d agodbt Core1.12.0 release candidate 3
- 25d agoCountlyJourneys survive user merges; SDK-provided asset paths
- 25d agodbt Core1.12.0 release candidate 2
- 28d agodbt Core1.12.0 release candidate 1
- 29d agodbt CoreFusion gains read-write Iceberg REST catalogs and catalogs.yml v2 ⚡
- 1mo agoCountlyRegex event filters in block plugin; access-page redirect fix
Frequently asked questions
What is the difference between dbt Core and Countly?
They serve adjacent needs but don't currently overlap on shipped themes. dbt Core is currently shipping more aggressively (velocity 7.5 vs 5.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 Countly?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. dbt Core is currently shipping more aggressively (velocity 7.5 vs 5.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 Countly?
Top Countly alternatives in Analytics are ranked by recent ship velocity. Browse the "Countly alternatives" section above for the current picks, or visit /alternatives/countly for the full list with editorial commentary on each.