Tautulli
Plex's analytics companion has spent a year shipping CVE fixes faster than features.
Comparison · Analytics
OpenCTI vs Fulcrum
A side-by-side editorial comparison of OpenCTI and Fulcrum — release velocity, themes, recent moves, and the top alternatives to consider.
OpenCTI vs Fulcrum: at a glance
| Feature | OpenCTI | Fulcrum |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 5.0 | 6.3 |
| Sparks · 30d | 0 | 1 |
| Top themes | threat-intelligence, connector-marketplace, workflow-approval, sbom | field-data-collection, gis, esri-integration, mobile-apps |
| Last editorial update | 1h ago | 4d ago |
| Website | Visit → | — |
What is OpenCTI?
OpenCTI ships weekly and is rebuilding its connector catalog into a marketplace.
OpenCTI runs a weekly CalVer release train on the current line plus a separate LTS branch that takes backported security work. The recurring theme across recent releases is the integrations surface: the connector catalog was redesigned into a faceted marketplace, connector status labels were renamed to Supported by Filigran and Supported by Community, and the new integrations experience closed its functional gaps around config import, works, sorting and next-run visibility. Workflow gained draft approval, full reset and protection against publishing a workflow that deletes an in-use status, and the legacy HTML editor was removed outright.
What is Fulcrum?
Fulcrum is retiring Google Maps and betting its field app entirely on Esri.
Fulcrum's field data collection platform is mid-consolidation onto a single mapping engine. The legacy Google Maps engine retires on September 1, 2026, and any organization still defaulting to it on web or mobile will be switched to Esri Maps automatically; Google's satellite, hybrid, and street basemaps survive as options in the Esri layer picker. Everything else this cycle is routine — weekly web release notes covering map layer and billing fixes, and phased mobile releases addressing stability, offline symbology, and KML display.
OpenCTI vs Fulcrum: editorial side-by-side
OpenCTI
5.0ANALYTICS
OpenCTI ships weekly and is rebuilding its connector catalog into a marketplace.
◆ Current state
OpenCTI runs a weekly CalVer release train on the current line plus a separate LTS branch that takes backported security work. The recurring theme across recent releases is the integrations surface: the connector catalog was redesigned into a faceted marketplace, connector status labels were renamed to Supported by Filigran and Supported by Community, and the new integrations experience closed its functional gaps around config import, works, sorting and next-run visibility. Workflow gained draft approval, full reset and protection against publishing a workflow that deletes an in-use status, and the legacy HTML editor was removed outright.
◆ Where it's heading
Two directions are visible. One is commercial packaging — XTM Hub connection points, hero-style Enterprise Edition cards in settings, and the supported-by labelling all draw a line between vendor-backed and community connectors inside the product. The other is supply-chain and governance hygiene: SBOM generation with syft, documented SBOM format, admin-forced password changes, session IDs recorded in audit logs, and a configurable webhook deny list. The LTS branch confirms the split audience — enterprises on a slow line getting CVE backports while the weekly line moves.
◆ Prediction
Expect the marketplace framing to keep hardening the commercial boundary — paid or vendor-supported connectors surfaced distinctly from community ones — and workflow approval to extend from drafts into other publishing paths.
Fulcrum
6.3ANALYTICS
Fulcrum is retiring Google Maps and betting its field app entirely on Esri.
◆ Current state
Fulcrum's field data collection platform is mid-consolidation onto a single mapping engine. The legacy Google Maps engine retires on September 1, 2026, and any organization still defaulting to it on web or mobile will be switched to Esri Maps automatically; Google's satellite, hybrid, and street basemaps survive as options in the Esri layer picker. Everything else this cycle is routine — weekly web release notes covering map layer and billing fixes, and phased mobile releases addressing stability, offline symbology, and KML display.
◆ Where it's heading
The Esri consolidation buys capabilities the Google engine could not offer: line and polygon snapping, GPS tracks with background tracking, offline basemaps, a redesigned mobile Location Editor, and direct connectivity to ArcGIS Online and Enterprise feature service layers. That positions Fulcrum as an ArcGIS-adjacent field client rather than a general mobile forms tool. The release cadence is high but the substance is thin between the engine migration and a steady drip of fixes.
◆ Prediction
Expect migration prompts and default-switch warnings to escalate through August as the deadline approaches, and MMPK layer support to leave early access once Esri is the only engine to support it on.
Alternatives to OpenCTI and Fulcrum
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 OpenCTI or Fulcrum.
Delta Lake
Delta Lake is handing table authority to Unity Catalog — under a feed buried in Databricks build tags.
Grafana Mimir
Mimir's feed is mostly bot-authored Helm bumps; the real release is 3.2, and it is query-engine work.
Fluent Bit
Fluent Bit runs a 4.2 and a 5.0 train side by side, both fed by the same backport pipeline.
Omni
Omni ships weekly, and this quarter every week added something to the AI layer.
Countly
Countly's core is in maintenance while every real feature lands in the enterprise journey engine.
See all OpenCTI alternatives → · See all Fulcrum alternatives →
Recent activity from OpenCTI and Fulcrum
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 21h agoOpenCTIWeekly release: data sanity stop, SBOM docs, merge performance
- 4d agoFulcrumReplace map layer files in place; storage bar fix
- 4d agoFulcrumGoogle Maps engine retires Sept 1; orgs auto-switch to Esri ⚡
- 5d agoOpenCTIWeekly release: integrations experience and draft approval workflow
- 6d agoFulcrumAndroid 2607.3.0: map responsiveness and KML fixes
- 11d agoFulcrumMBTiles upload and lasso tool selection fixes
- 12d agoFulcrumOffline ArcGIS layers keep custom symbols; INFERENCE labels
- 13d agoOpenCTIWeekly release: connector catalog becomes a faceted marketplace
- 14d agoFulcrumiOS 2607.1.0: stability and performance fixes
- 18d agoOpenCTIWeekly release: live stream, groups and widget fixes
- 19d agoOpenCTIWeekly release: SBOM generation, custom views, ESM frontend
- 25d agoOpenCTILTS 6: security backports and dependency updates
Frequently asked questions
What is the difference between OpenCTI and Fulcrum?
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 1 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.
Is OpenCTI better than Fulcrum?
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 1 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.
What are the best alternatives to OpenCTI?
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.
What are the best alternatives to Fulcrum?
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.