Fulcrum
Fulcrum is consolidating on Esri, with Google Maps gone September 1
A side-by-side editorial comparison of Appfigures and OpenCTI — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | Appfigures | OpenCTI |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 3.8 | 6.3 |
| Sparks · 30d | 1 | 1 |
| Top themes | app-analytics, agentic, aso, competitive-intelligence | threat-intelligence, connector-marketplace, xtm-hub, workflow-governance |
| Last editorial update | 1d ago | 1h ago |
| Website | — | Visit → |
Appfigures just made its app-market data something an AI agent can query, not something you screenshot.
Appfigures has spent the last year widening what its estimates cover — iPad data folded into every download and revenue figure, state-level financials in the API, a 15-report App Intelligence suite for competitor research, and Leaderboards that rank apps by explicit metrics instead of opaque store charts. The August release changes who consumes all of that: a CLI built specifically for AI agents, with a hinting system to keep them from misreading the data. The product is no longer only a dashboard.
OpenCTI is rebuilding its connector layer into a marketplace and wiring the platform to XTM Hub
OpenCTI ships on a roughly weekly date-stamped cadence, and the last six releases divide cleanly: the connector catalog was redesigned into a faceted marketplace, then the surrounding integrations experience was reworked around it, then the platform gained two-way connection with Filigran's XTM Hub. Alongside that, saved searches and saved filters became shareable and reusable across dashboards. The most recent releases are weighted toward fixes rather than new surface.
Appfigures has spent the last year widening what its estimates cover — iPad data folded into every download and revenue figure, state-level financials in the API, a 15-report App Intelligence suite for competitor research, and Leaderboards that rank apps by explicit metrics instead of opaque store charts. The August release changes who consumes all of that: a CLI built specifically for AI agents, with a hinting system to keep them from misreading the data. The product is no longer only a dashboard.
The arc runs from data completeness to data access. First they closed gaps in the underlying estimates, then they built more ways to slice them, and now they are exposing the whole surface to agents that can investigate, compare, monitor, and act — including replying to reviews and adjusting Apple Ads campaigns. Each layer assumes the one below it is trustworthy, which is why the accuracy fixes (iPad coverage, keyword popularity, Google Play delay removal) came first.
Expect the agent surface to deepen before it widens — more write actions exposed through the CLI, and Leaderboards and App Intelligence reports made directly queryable by agents rather than only through the web reports.
OpenCTI ships on a roughly weekly date-stamped cadence, and the last six releases divide cleanly: the connector catalog was redesigned into a faceted marketplace, then the surrounding integrations experience was reworked around it, then the platform gained two-way connection with Filigran's XTM Hub. Alongside that, saved searches and saved filters became shareable and reusable across dashboards. The most recent releases are weighted toward fixes rather than new surface.
The centre of gravity is moving from OpenCTI as a self-contained platform to OpenCTI as a client of Filigran's wider ecosystem — connectors sourced from a catalog with support tiers, custom views deployed from XTM Hub, an MCP server exposed through XTM One. The workflow engine is maturing in parallel, picking up draft approval, transition restrictions and full reset. Telemetry coverage expanded significantly in the same period, which is what makes the catalog's adoption measurable.
Expect more of the platform's configuration surface — dashboards, playbooks, mappers — to become distributable through XTM Hub the way custom views and connectors already are. The workflow approval features suggest governance controls are the next area to fill in.
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 Appfigures or OpenCTI.
Fulcrum is consolidating on Esri, with Google Maps gone September 1
Omni ships weekly, and almost every week the headline item is an AI feature
Four ODD Platform releases in two weeks, and not one of them changes the product
Baremaps got geoparquet and hillshading, then went quiet for eighteen months in incubation
Deequ ships GitHub tags whose release notes are one commit message long
Marquez spent 2024 turning a lineage store into a UI, then stopped releasing
See all Appfigures alternatives → · See all OpenCTI alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. OpenCTI is currently shipping more aggressively (velocity 6.3 vs 3.8), with 1 editorial sparks in the last 30 days against 1. 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. OpenCTI is currently shipping more aggressively (velocity 6.3 vs 3.8), with 1 editorial sparks in the last 30 days against 1. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top Appfigures alternatives in Analytics are ranked by recent ship velocity. Browse the "Appfigures alternatives" section above for the current picks, or visit /alternatives/appfigures for the full list with editorial commentary on each.
Top OpenCTI alternatives in Analytics are ranked by recent ship velocity. Browse the "OpenCTI alternatives" section above for the current picks, or visit /alternatives/opencti for the full list with editorial commentary on each.