Fulcrum
Fulcrum ships MCP server and AI Toolkit to let AI assistants build and query field data forms
A side-by-side editorial comparison of Countly and dbt Core — release velocity, themes, recent moves, and the top alternatives to consider.
Countly ripped out its custom-code sandbox and rebuilt its Docker stack from scratch in a single LTS drop.
Countly is in an extended security hardening cycle, maintaining two parallel LTS lines — 25.03.x and 24.05.x — with coordinated patch releases. The 25.03.52-LTS was structurally significant: Docker images rebuilt as multi-stage on Debian 13 and Node.js 24 to strip compilers and build tooling from production images, the legacy v8-sandbox replaced by isolated-vm eliminating network, filesystem, and process access from custom hooks, and the A/B testing backend migrated from end-of-life Python 3.8 and pystan to Python 3.12 and cmdstanpy. The 25.03.53 and 24.05.53 patches that followed addressed XSS, OIDC session handling, and embedded widget cross-origin policies.
dbt 2.0 enters final RC with beta Snowflake interactive_table materialization and full ClickHouse MV support.
dbt Core is in the final stretch of the v2.0 release cycle, running RC builds while the 1.x stable branch continues receiving targeted fixes. RC.2 added beta support for Snowflake's interactive_table materialization — covering static and dynamic variants with config-change detection for target_lag, warehouse, and cluster_by — and completed ClickHouse materialized view support via the new ADBC driver. The 1.12.5 and 1.11.15 patch releases address a MetricFlow protocol compliance issue and a package path traversal security fix respectively.
Countly is in an extended security hardening cycle, maintaining two parallel LTS lines — 25.03.x and 24.05.x — with coordinated patch releases. The 25.03.52-LTS was structurally significant: Docker images rebuilt as multi-stage on Debian 13 and Node.js 24 to strip compilers and build tooling from production images, the legacy v8-sandbox replaced by isolated-vm eliminating network, filesystem, and process access from custom hooks, and the A/B testing backend migrated from end-of-life Python 3.8 and pystan to Python 3.12 and cmdstanpy. The 25.03.53 and 24.05.53 patches that followed addressed XSS, OIDC session handling, and embedded widget cross-origin policies.
Countly is hardening its self-hosted security posture — the isolated-vm switch and Docker rebuild reduce attack surface without changing the product surface for end users. Running two LTS tracks simultaneously signals a maturing enterprise customer base that cannot upgrade on a quarterly cadence. Feature development in journey_engine and content continues on a separate lane from the security work, suggesting the two concerns are intentionally decoupled.
The Node.js 22/24 migration will propagate to additional components. The isolated-vm change will likely prompt tighter documentation of what custom code can and cannot access. Dual LTS maintenance continues as long as significant deployments remain on 24.05.x.
dbt Core is in the final stretch of the v2.0 release cycle, running RC builds while the 1.x stable branch continues receiving targeted fixes. RC.2 added beta support for Snowflake's interactive_table materialization — covering static and dynamic variants with config-change detection for target_lag, warehouse, and cluster_by — and completed ClickHouse materialized view support via the new ADBC driver. The 1.12.5 and 1.11.15 patch releases address a MetricFlow protocol compliance issue and a package path traversal security fix respectively.
dbt 2.0's final stabilization phase is expanding adapter coverage depth rather than adding new DAG primitives. ClickHouse now has full MV and unit-test support; Snowflake gets interactive table handling with edge-case-level cluster_by comparison fixes that only come from deep validation work. The pattern: make dbt reliably correct on what modern warehouses already ship, rather than shipping new features.
The v2.0 stable tag is imminent — RC.2's fixes are narrow and precision-targeted, not broad. Post-2.0 expect a Fusion manifest integration stabilization push, given that 1.12.4 shipped two fixes specifically for Fusion-generated manifests.
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 Countly or dbt Core.
Fulcrum ships MCP server and AI Toolkit to let AI assistants build and query field data forms
Holistics builds AI governance and docs-as-analytics in parallel, shipping both weekly
OpenHouse breaks ground on Iceberg views while tightening storage lifecycle and authorization
Lightdash is cutting its dbt dependency and building AI-powered authoring into every layer of its BI stack.
Keboola's Kai AI assistant hits GA, completing the pivot from data platform to AI-native pipeline orchestration layer.
Omni's Apps reach general availability, completing its embedded analytics platform pitch.
See all Countly alternatives → · See all dbt Core alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Countly and dbt Core are shipping at a similar cadence (velocity 6.3 vs 6.3, 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Countly and dbt Core are shipping at a similar cadence (velocity 6.3 vs 6.3, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
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.
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.