dbt Core
dbt 2.0 ships stable with an official OSS/proprietary split and agentic skill loading
A side-by-side editorial comparison of Countly and Fulcrum — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Countly | Fulcrum |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 6.3 | 6.3 |
| Sparks · 30d | 0 | 1 |
| Top themes | analytics, security, self-hosted, lts | field-data, mobile, gis, ai-toolkit |
| Last editorial update | 12d ago | 4h ago |
| Website | Visit → | — |
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.
Fulcrum ships MCP server and AI Toolkit to let AI assistants build and query field data forms
Fulcrum is running two parallel tracks: foundational mobile stability (GPS accuracy, offline PDF, Photo FastFill across iOS and Android) and a new AI integration layer via MCP. The mobile side is a steady improvement cadence; the MCP launch is the first genuinely new capability surface the product has added in this window. Photo FastFill (AI-assisted data extraction from photos) continues to mature through early access.
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.
Fulcrum is running two parallel tracks: foundational mobile stability (GPS accuracy, offline PDF, Photo FastFill across iOS and Android) and a new AI integration layer via MCP. The mobile side is a steady improvement cadence; the MCP launch is the first genuinely new capability surface the product has added in this window. Photo FastFill (AI-assisted data extraction from photos) continues to mature through early access.
The MCP + AI Toolkit launch signals that Fulcrum sees AI-assisted configuration as a primary growth vector — letting field operations teams describe a form in plain language and have an AI build it correctly. Photo FastFill and offline PDF generation via App Extensions are part of the same arc: AI-augmented data capture for field workers who may not be technically proficient. The product is incrementally offloading form-building complexity to AI.
Fulcrum will extend the MCP toolset toward reading and writing records directly, not just building forms and schema. Photo FastFill will likely exit early access with more field types supported as the extraction model improves.
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 Fulcrum.
dbt 2.0 ships stable with an official OSS/proprietary split and agentic skill loading
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 Fulcrum 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 Fulcrum 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 Fulcrum 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 Fulcrum alternatives in Analytics are ranked by recent ship velocity. Browse the "Fulcrum alternatives" section above for the current picks, or visit /alternatives/fulcrum for the full list with editorial commentary on each.