ROOT
ROOT 6.42 rebuilds its Python interface on cppjit and moves Cling to LLVM 22.
A side-by-side editorial comparison of Datawrapper and NetObserv — release velocity, themes, recent moves, and the top alternatives to consider.
Datawrapper's October is touch tooltips, keyboard focus and small chart repairs.
Datawrapper's recent changelog is a run of small, single-line changes. Touch devices get reliable tooltips on multiple-line and multiple-column charts and close buttons on symbol maps and scatter plots, keyboard focus outlines are now consistent and themeable, and range highlights can be hidden per device. The largest items are still minor refinements to existing chart types.
NetObserv hit 2.0 without breaking changes, then started renaming its metrics.
NetObserv's operator reached 2.0.0 in September, labelled entirely non-breaking: BGP ASN enrichment through FRRConfiguration CRDs, DNS names in metrics, DNS port configuration in the FlowCollector API, stricter RBAC and network policies for the operator itself, and TLS settings taken from the OpenShift API server. 2.0.1 was fixes and dependency bumps. 2.0.2 fixes ASN labels and IPSec metrics, captures OpenSSL socket tuples at event time in the eBPF agent, and renames filtered_flows_total to filtered_packets_total.
Datawrapper's recent changelog is a run of small, single-line changes. Touch devices get reliable tooltips on multiple-line and multiple-column charts and close buttons on symbol maps and scatter plots, keyboard focus outlines are now consistent and themeable, and range highlights can be hidden per device. The largest items are still minor refinements to existing chart types.
The current thread is reader-side interaction, with mobile touch and keyboard access getting the most attention. Range highlights have now had two additions in three months, after patterns in August, so annotation remains the one area accumulating options. No new chart type appears in the visible window.
Expect more touch and accessibility fixes as tooltip behavior is brought in line across chart types, since the notes already compare newer behavior with choropleth maps.
NetObserv's operator reached 2.0.0 in September, labelled entirely non-breaking: BGP ASN enrichment through FRRConfiguration CRDs, DNS names in metrics, DNS port configuration in the FlowCollector API, stricter RBAC and network policies for the operator itself, and TLS settings taken from the OpenShift API server. 2.0.1 was fixes and dependency bumps. 2.0.2 fixes ASN labels and IPSec metrics, captures OpenSSL socket tuples at event time in the eBPF agent, and renames filtered_flows_total to filtered_packets_total.
The 2.0 line adds routing context (BGP ASNs) and DNS identity to flows, which moves the tool from 'which pod talked to which' toward 'which network and service.' The operator's own security posture, with RBAC, network policies and TLS profiles, is getting as much attention as the data. The TLS thread continues inside the eBPF agent, with OpenSSL tracking narrowed to packet mode in 2.0.2.
Expect 2.0.x fixes around the new ASN and TLS enrichment, which both needed corrections in 2.0.2. The metric rename is a signal that dashboards built on older names may need updating in later releases too.
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 Datawrapper or NetObserv.
ROOT 6.42 rebuilds its Python interface on cppjit and moves Cling to LLVM 22.
Rho's feed jumped from 0.4.0 to 0.5.2, and the only note is about its release pipeline.
Cortex 1.22 is on its fourth candidate, with sharded Parquet and years of deprecated flags removed.
Countly's two LTS lines now get the same security fixes within a week of each other.
OpenMetadata reaches 2.1 rc1 after a month of repairing 2.0's connectors.
Stitch keeps patching connectors one replication bug at a time.
See all Datawrapper alternatives → · See all NetObserv alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Datawrapper is currently shipping more aggressively (velocity 5.0 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.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. Datawrapper is currently shipping more aggressively (velocity 5.0 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.
Top Datawrapper alternatives in Analytics are ranked by recent ship velocity. Browse the "Datawrapper alternatives" section above for the current picks, or visit /alternatives/datawrapper for the full list with editorial commentary on each.
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.