Cortex
Cortex 1.22 is on its fourth candidate, with sharded Parquet and years of deprecated flags removed.
A side-by-side editorial comparison of Datawrapper and Fluent Bit — 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.
Fluent Bit spends October bounding what its inputs will accept.
Fluent Bit's last three 5.1 releases are mostly hardening. 5.1.3 validates OTLP log protobuf depth and fixes out_s3 heap corruption; 5.1.4 limits OTLP gRPC decompression and budgets msgpack objects on forward input; 5.1.5 bounds MessagePack reads into Lua and mitigates CRLF injection in HTTP headers. Features still land between them, including protobuf for the Kafka schema registry, a CRL file option for TLS and Chronicle API support. 5.0.x is taking backports only.
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.
Fluent Bit's last three 5.1 releases are mostly hardening. 5.1.3 validates OTLP log protobuf depth and fixes out_s3 heap corruption; 5.1.4 limits OTLP gRPC decompression and budgets msgpack objects on forward input; 5.1.5 bounds MessagePack reads into Lua and mitigates CRLF injection in HTTP headers. Features still land between them, including protobuf for the Kafka schema registry, a CRL file option for TLS and Chronicle API support. 5.0.x is taking backports only.
The pattern has shifted from the depth-first feature work on GCS and eBPF in August and September to input safety across the agent. The mitigations cover many separate plugins rather than one bad component, which reads as a systematic audit of untrusted data paths. Fluent Bit sits on the path of data it does not control, which is where a collector's risk lies.
Expect further releases on the same pattern, mixing mitigations with connector additions. The eBPF trace expansion noted earlier does not appear in these notes, so its next step is unclear.
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 Fluent Bit.
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.
Axiom makes agent work checkable, and points alerts straight at coding agents
Pinot 1.6 adds SQL DDL and vector backends, and now needs Java 25 to run its services.
See all Datawrapper alternatives → · See all Fluent Bit alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Datawrapper and Fluent Bit are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). 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 and Fluent Bit are shipping at a similar cadence (velocity 5.0 vs 5.0, both within Sparkpulse's "active" band). 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 Fluent Bit alternatives in Analytics are ranked by recent ship velocity. Browse the "Fluent Bit alternatives" section above for the current picks, or visit /alternatives/fluent-bit for the full list with editorial commentary on each.