Graphite
Graphite's answer to its own CVE backlog is a pre-release nobody calls official.
Comparison · Analytics
Fulcrum vs NetObserv
A side-by-side editorial comparison of Fulcrum and NetObserv — release velocity, themes, recent moves, and the top alternatives to consider.
Fulcrum vs NetObserv: at a glance
| Feature | Fulcrum | NetObserv |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 6.3 | 2.5 |
| Sparks · 30d | 0 | 0 |
| Top themes | field-data-collection, gis, esri-migration, offline-reliability | network-observability, ebpf, kubernetes, tls-visibility |
| Last editorial update | 1d ago | 2h ago |
| Website | — | Visit → |
What is Fulcrum?
Fulcrum is consolidating its whole mapping stack on Esri, and retiring Google Maps to finish it.
Fulcrum ships weekly web release notes alongside separate iOS and Android builds, and nearly all of the recent work is mapping. The ArcGIS SDK moved to 300.0.0 on mobile and the map engine picked up current ArcGIS and deck.gl versions on web, while a run of fixes addressed offline layer styling, basemap loading and attachment downloads on poor connections. On-device machine learning inference dropped ONNX for a new format, with labels now read from an uploaded labels.txt file.
What is NetObserv?
NetObserv is layering TLS visibility and health alerting on top of its eBPF flow pipeline.
NetObserv ships roughly monthly as a coordinated bundle — operator, eBPF agent, flowlogs-pipeline and console plugin move together in each release. The functional work over these six releases splits three ways: a TLS visibility feature that arrived as a knob in 1.11.3 and has been extended with metrics and alerts since, a Network Health layer built on Prometheus recording rules rather than alerts alone, and steady hardening of the agent-to-pipeline path (mTLS, hot-reload filters, packet translation and sampling fixes). Prometheus is now on by default.
Fulcrum vs NetObserv: editorial side-by-side
Fulcrum
6.3ANALYTICS
Fulcrum is consolidating its whole mapping stack on Esri, and retiring Google Maps to finish it.
◆ Current state
Fulcrum ships weekly web release notes alongside separate iOS and Android builds, and nearly all of the recent work is mapping. The ArcGIS SDK moved to 300.0.0 on mobile and the map engine picked up current ArcGIS and deck.gl versions on web, while a run of fixes addressed offline layer styling, basemap loading and attachment downloads on poor connections. On-device machine learning inference dropped ONNX for a new format, with labels now read from an uploaded labels.txt file.
◆ Where it's heading
The mapping stack is converging on Esri across every client, and the announced September 1 retirement of the legacy Google Maps engine makes that explicit. Esri Maps has absorbed Google's satellite, hybrid and street basemaps, and the GIS capabilities Fulcrum keeps investing in — snapping, ArcGIS Feature Service connectivity, offline basemaps, GPS tracks, the redesigned location editor — only exist on that engine. Everything else in the feed is stabilization on the same surface, which is what a team does when it is preparing to move every remaining customer onto one path.
◆ Prediction
Expect migration reminders and switching guidance for organizations still defaulting to Google Maps as September 1 approaches, and MMPK layers to leave Early Access once the engine consolidation is complete.
NetObserv
2.5ANALYTICS
NetObserv is layering TLS visibility and health alerting on top of its eBPF flow pipeline.
◆ Current state
NetObserv ships roughly monthly as a coordinated bundle — operator, eBPF agent, flowlogs-pipeline and console plugin move together in each release. The functional work over these six releases splits three ways: a TLS visibility feature that arrived as a knob in 1.11.3 and has been extended with metrics and alerts since, a Network Health layer built on Prometheus recording rules rather than alerts alone, and steady hardening of the agent-to-pipeline path (mTLS, hot-reload filters, packet translation and sampling fixes). Prometheus is now on by default.
◆ Where it's heading
The project is moving from flow collection toward opinionated health signalling — recording rules, runbook links in alerts, ingress 5xx and latency templates, health metadata driving console plugin config. That is the shape of a tool trying to answer 'is the network healthy' rather than only 'what traffic occurred'. In parallel, supply-chain and workflow security is getting real attention: SBOM generation and artifact signing, SHA-pinned GitHub Actions, pwn-request workflow checks and a pprof exposure fix all landed in the last two releases. The operator was also renamed from network-observability-operator to netobserv-operator.
◆ Prediction
Expect the TLS thread to keep extending — the sequence so far is fields, then metrics, then alerts, so dashboards and health rules built on TLS data are the natural next step. Continued investment in the Network Health rule set is the other safe bet, since it is where the last three releases have concentrated their non-dependency commits.
Alternatives to Fulcrum and NetObserv
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 NetObserv.
Cortex
Cortex is betting on Parquet block storage and graduating years of experimental features.
Apache Storm
Storm 3.0 finishes removing the Clojure it was built in, and moves to a Java 21 baseline.
Apache StreamPark
Five release candidates in two years, none of them stable, and none since October 2025.
Apache HertzBeat
A monitoring project whose public release feed skips the release that mattered.
Axiom
Axiom is rebuilding observability so an AI agent, not a human, can be the first user.
See all Fulcrum alternatives → · See all NetObserv alternatives →
Recent activity from Fulcrum and NetObserv
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2d agoFulcrumSSO notification wording and an ArcGIS map engine update
- 4d agoFulcrumAndroid: ArcGIS location and signature field fixes
- 4d agoFulcrumiOS: basemap loading and location button fixes
- 5d agoFulcrumiOS drops ONNX for on-device inference; ArcGIS SDK 300
- 5d agoFulcrumiOS: offline ArcGIS layers keep custom symbols
- 9d agoFulcrumReplace a map layer file without recreating the layer
- 19d agoNetObserv1.12.0 adds TLS alerting, flp-informers and signed releases
- 1mo agoNetObserv1.11.5 adds TLS metrics, Kafka compression and drop events
- 4mo agoNetObservTLS tracking arrives as a feature knob with new TLS fields ⚡
- 5mo agoNetObserv1.11.2 adds a pause control and TLS/mTLS hardening
- 5mo agoNetObserv1.11.1 is documentation, Snyk config and dependency updates
- 6mo agoNetObserv1.11.0 builds out Network Health rules and hot-reload filters
Frequently asked questions
What is the difference between Fulcrum and NetObserv?
They serve adjacent needs but don't currently overlap on shipped themes. Fulcrum is currently shipping more aggressively (velocity 6.3 vs 2.5), 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.
Is Fulcrum better than NetObserv?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Fulcrum is currently shipping more aggressively (velocity 6.3 vs 2.5), 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.
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.
What are the best alternatives to NetObserv?
Top NetObserv alternatives in Analytics are ranked by recent ship velocity. Browse the "NetObserv alternatives" section above for the current picks, or visit /alternatives/netobserv for the full list with editorial commentary on each.