Calibre
Calibre MCP lets your coding agent read RUM and Lighthouse data, then fix the slow code
A side-by-side editorial comparison of Fulcrum and OpenReplay — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Fulcrum | OpenReplay |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 6.3 | 5.0 |
| Sparks · 30d | 0 | 0 |
| Top themes | field data collection, ai assistant, mcp, gps | session replay, self-hosted, helm, backports |
| Last editorial update | 17h ago | 7h ago |
| Website | — | Visit → |
Fulcrum lets AI assistants sign in to its MCP server with a normal account.
Fulcrum, a field data collection platform, opened its Insights AI assistant to all customers in October. Its weekly web release now adds OAuth sign-in for the Fulcrum MCP server in alpha, so outside AI assistants connect with a user account and see only what that role allows. The rest is GPS Device Capture support on repeatables and fixes across the web, iOS and Android apps.
OpenReplay's feed is Helm chart bumps behind its asset-cacher deny list.
OpenReplay's entries since November 4 are automated backup tags on the 1.26 and 1.27 lines that only increment Helm chart versions for chalice, assist-api and assist-stats. The last functional change remains the November 3 ASSETS_DENY_HOSTS option, which lets self-hosters block hosts the asset cacher may fetch, alongside a fix for EE 1.26 images that crashed on start.
Fulcrum, a field data collection platform, opened its Insights AI assistant to all customers in October. Its weekly web release now adds OAuth sign-in for the Fulcrum MCP server in alpha, so outside AI assistants connect with a user account and see only what that role allows. The rest is GPS Device Capture support on repeatables and fixes across the web, iOS and Android apps.
Fulcrum is opening its data to AI from both sides: Insights inside the product and MCP for assistants outside it. Role-scoped OAuth is the piece that makes the outside route usable without sharing API tokens.
The MCP sign-in is likely to move from alpha to beta in the weekly web notes, following how Insights and GPS Integration were labeled as they matured.
OpenReplay's entries since November 4 are automated backup tags on the 1.26 and 1.27 lines that only increment Helm chart versions for chalice, assist-api and assist-stats. The last functional change remains the November 3 ASSETS_DENY_HOSTS option, which lets self-hosters block hosts the asset cacher may fetch, alongside a fix for EE 1.26 images that crashed on start.
The project is in a maintenance stretch, backporting fixes across 1.25 to 1.27 and repackaging charts. Nothing in recent entries points to new user-facing features.
Unclear from these entries; more chart-bump backup tags are likely until a 1.27.x release with notes appears.
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 OpenReplay.
Calibre MCP lets your coding agent read RUM and Lighthouse data, then fix the slow code
Dovetail opens its docs to Claude and ChatGPT as co-authors.
SkyWalking 11.1 builds service maps from OpenTelemetry traces, no SkyWalking agent required.
Tinybird shrinks its Local image by a third after a run of observability updates.
OpenHouse tightens view authorization and moves its optimizer schema to Flyway.
Delta Lake's public stream is Databricks builds and code cleanup on the way to 4.5.
See all Fulcrum alternatives → · See all OpenReplay 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 5.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 5.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 OpenReplay alternatives in Analytics are ranked by recent ship velocity. Browse the "OpenReplay alternatives" section above for the current picks, or visit /alternatives/openreplay for the full list with editorial commentary on each.