ManageEngine Log360
Log360's September build fixes the migration to the unified console.
A side-by-side editorial comparison of MotherDuck and Apache Storm — release velocity, themes, recent moves, and the top alternatives to consider.
MotherDuck turns Dives from read-only dashboards into apps that write back through Flights.
MotherDuck ships a weekly changelog, and October's entries fill out two layers. Governance: row-level security, column-level security and masking on Shares, table-level security for managed DuckLake, and run grants that let teammates trigger a Flight without seeing its code or credentials. Interaction: Dives gained write-back buttons and forms that run Flights, Agent Chat can create and edit Dives, and AI functions got 50 to 60% cheaper on OpenAI models while prompt_jev() started billing.
Storm 3.1 adds an Iceberg sink and closes a long list of security gaps in Nimbus and the UI.
Storm runs a 3.x line, started in July with 3.0.0's removal of all Clojure and a Java 21 baseline, alongside 2.8.x maintenance. 3.1.0 on September 12 adds a storm-iceberg module with an Apache Iceberg sink bolt and a setting to control JSONP wrapping, and spends most of its notes on hardening: log listings filtered by user permission, jar locations restricted to the Nimbus inbox, blobstore names confined to topology directories, TLS peer verification for worker connections and required Kryo class registration.
MotherDuck ships a weekly changelog, and October's entries fill out two layers. Governance: row-level security, column-level security and masking on Shares, table-level security for managed DuckLake, and run grants that let teammates trigger a Flight without seeing its code or credentials. Interaction: Dives gained write-back buttons and forms that run Flights, Agent Chat can create and edit Dives, and AI functions got 50 to 60% cheaper on OpenAI models while prompt_jev() started billing.
The pieces are converging. Flights (the serverless job layer) now power actions inside Dives, Agent Chat builds the Dives, and fine-grained sharing controls decide who sees which rows. MotherDuck is moving from a cloud DuckDB warehouse toward a place where data apps are built and governed, with SQL-native AI functions as the hook.
Expect write-back and run grants to spread to more surfaces, such as agents running Flights directly, and further prompt_jev() region and modality expansion after images and Europe.
Storm runs a 3.x line, started in July with 3.0.0's removal of all Clojure and a Java 21 baseline, alongside 2.8.x maintenance. 3.1.0 on September 12 adds a storm-iceberg module with an Apache Iceberg sink bolt and a setting to control JSONP wrapping, and spends most of its notes on hardening: log listings filtered by user permission, jar locations restricted to the Nimbus inbox, blobstore names confined to topology directories, TLS peer verification for worker connections and required Kryo class registration.
After the 2.8.6 and 2.8.7 CVE releases, the 3.x line is closing access-control gaps across Nimbus, the logviewer and worker transport. The Iceberg sink adds a direct path into lakehouse storage.
Expect 3.1.x follow-ups, possibly with security advisories for the hardened paths, and continued 2.8.x maintenance; whether more lakehouse connectors follow 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 MotherDuck or Apache Storm.
Log360's September build fixes the migration to the unified console.
Deepnote's agent now runs from first prompt to finished notebook without handoffs.
HertzBeat's 1.9.0 is on its second release candidate, and the feed still skips 1.8.0.
OpenPanel moves from 3.18 to 3.20 in two days, still without a word of release notes.
TsFile 2.5 adds Go to its Java, C++ and Python implementations.
After a year of CVE fixes, Glances 4.5.7 turns to making its alerts tell the truth.
See all MotherDuck alternatives → · See all Apache Storm alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. MotherDuck is currently shipping more aggressively (velocity 5.0 vs 0.0), 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. MotherDuck is currently shipping more aggressively (velocity 5.0 vs 0.0), 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 MotherDuck alternatives in Analytics are ranked by recent ship velocity. Browse the "MotherDuck alternatives" section above for the current picks, or visit /alternatives/motherduck for the full list with editorial commentary on each.
Top Apache Storm alternatives in Analytics are ranked by recent ship velocity. Browse the "Apache Storm alternatives" section above for the current picks, or visit /alternatives/storm for the full list with editorial commentary on each.