Countly vs Fulcrum
Side-by-side trajectory, velocity, and editorial themes.
Countly runs a sustained security-hardening pass across its 24.05 and 25.03 lines
Countly's recent releases are dominated by security and stability work: a bug-bounty-style hardening pass closing cross-app metric exfiltration, MongoDB operator injection, path traversal, SSRF, and session-fixation vectors (24.05.50, 25.03.44), alongside routine core and enterprise bug fixes. Enterprise additions are narrow, such as AD/LDAP journey approver groups.
The concentration of coordinated security fixes across both the 24.05 line and the current 25.03 line signals a deliberate hardening cycle, likely following an audit. Feature work is incremental; correctness and security are the current priority.
Expect continued security and stability fixes backported across both lines, with incremental enterprise additions in journeys and data-manager.
Fulcrum hardens its field-collection core with cross-platform tracking and map fixes
Fulcrum is in a hardening phase across its iOS, Android, and web field-data clients. After shipping background GPS tracking and offline KML/KMZ layers earlier in the cycle, the recent run is dominated by point releases fixing tracking geometry, map rendering, and URL-action behavior, alongside a capacity bump that raised the web video-upload limit to 5GB.
The throughline is reliability of the core field-collection loop — GPS tracking, geometry capture, and map interaction — rather than new surface area. Cross-platform parity is a clear priority: tracking and media improvements land on iOS, Android, and web in step. The cadence is steady weekly releases skewed toward stability over feature launches.
Expect continued stabilization of background tracking and geometry handling, with the next notable feature likely extending offline or media capabilities now that the 5GB upload ceiling and offline layer downloads are in place.
See more alternatives to Countly →
See more alternatives to Fulcrum →