Basedash
Basedash keeps pushing its data out of the workspace — now to people without accounts
A side-by-side editorial comparison of Fulcrum and PostHog — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Fulcrum | PostHog |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 6.3 | 0.0 |
| Sparks · 30d | 0 | 0 |
| Top themes | gis, esri-migration, offline-maps, field-data-capture | logs, mobile-sdks, support-conversations, session-replay |
| Last editorial update | 7h ago | 14d ago |
| Website | — | Visit → |
Fulcrum is betting its whole map stack on Esri, with a hard Google Maps cutoff on September 1.
Fulcrum is a field data collection platform, and nearly every entry in the last month touches mapping. The web app ships weekly fix batches for layer rendering (KML/KMZ, MBTiles, ArcGIS Feature Services), while iOS and Android push near-weekly builds against the ArcGIS SDK. The newest iOS build turns to app-level responsiveness - database queries moved off the main path and the record editor kept interactive while Photo FastFill works in the background.
PostHog is filling in Logs and the mobile SDKs while quietly growing a support product.
PostHog ships weekly, and this week's batch is spread across four teams rather than concentrated in one product. Logs gets attribute filtering and a React Native capture path; the iOS SDK gains rage-click detection and a session-replay duration floor; Conversations picks up GitHub issues as an inbound support channel. Individually these are small, and the weekly digest bundles them into a single roundup entry.
Fulcrum is a field data collection platform, and nearly every entry in the last month touches mapping. The web app ships weekly fix batches for layer rendering (KML/KMZ, MBTiles, ArcGIS Feature Services), while iOS and Android push near-weekly builds against the ArcGIS SDK. The newest iOS build turns to app-level responsiveness - database queries moved off the main path and the record editor kept interactive while Photo FastFill works in the background.
The direction is a full consolidation onto Esri. The legacy Google Maps engine retires on September 1 with automatic migration for anyone who has not switched, and Esri now carries Google's satellite and street basemaps so the imagery argument is neutralized. Underneath, the mobile SDK moved to ArcGIS 300.0.0 and ONNX on-device inference gave way to a new INFERENCE format. Two capabilities are visibly staged behind early access rather than shipped: Photo FastFill, and a GPS integration still described as Alpha.
Expect the weeks before September 1 to stay dominated by migration-shaped fixes and Esri parity work, with Photo FastFill the nearer of the two early-access programs to general availability given it is already running in shipped builds.
PostHog ships weekly, and this week's batch is spread across four teams rather than concentrated in one product. Logs gets attribute filtering and a React Native capture path; the iOS SDK gains rage-click detection and a session-replay duration floor; Conversations picks up GitHub issues as an inbound support channel. Individually these are small, and the weekly digest bundles them into a single roundup entry.
Two build-outs are running in parallel. The observability side — Logs plus the mobile SDKs — is being brought up to parity with what PostHog already offers on web, which is what makes the platform credible for mobile teams rather than web analytics with an SDK attached. The Conversations work is the more interesting thread: adding support channels moves PostHog past measuring users toward handling them, and it is being built out in the same incremental weekly rhythm as everything else.
Expect Logs and the mobile SDKs to keep receiving parity features on the weekly cadence, and expect Conversations to add further inbound channels beyond GitHub issues. The entries do not show whether Conversations is being positioned as a standalone product or a feature of the existing suite.
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 Fulcrum or PostHog.
Basedash keeps pushing its data out of the workspace — now to people without accounts
RStudio ships through release branches, and the notes are commit messages
dbt Fusion's second beta is adapter work: ClickHouse gets materializations, indexes, and catalogs
Holistics keeps fencing in the AI layer it spent the summer building.
Dovetail spent July opening doors to other tools and August making its own rooms easier to enter.
The 0.0.x train stops at CRAN: tulpa's engine ships to the ecosystem it already anchors.
See all Fulcrum alternatives → · See all PostHog alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Fulcrum is currently shipping more aggressively (velocity 6.3 vs 0.0), with 0 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Fulcrum is currently shipping more aggressively (velocity 6.3 vs 0.0), with 0 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.
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.
Top PostHog alternatives in Analytics are ranked by recent ship velocity. Browse the "PostHog alternatives" section above for the current picks, or visit /alternatives/posthog for the full list with editorial commentary on each.