Omni
Omni ships weekly, and almost every week the headline item is an AI feature.
A side-by-side editorial comparison of aniread and Whatagraph — release velocity, themes, recent moves, and the top alternatives to consider.
| Feature | aniread | Whatagraph |
|---|---|---|
| Sector | Analytics | Analytics |
| Velocity score | 3.8 | 5.0 |
| Sparks · 30d | 1 | 0 |
| Top themes | animal tracking, file formats, auto-detection, data import | agency reporting, client portals, integrations, data storage |
| Last editorial update | 9h ago | 4d ago |
| Website | Visit → | — |
aniread stops asking you to know which tracker wrote the file
aniread is the reader package of the animovement suite, importing output from pose-estimation, centroid and behavioural-scoring tools into aniframe objects. Through 0.5.x the work was per-reader: get_supported_sources() exposed the format list programmatically, read_boris() added behavioural events, and Octron and BORIS each got targeted fixes. 0.6.0 changes the shape of the interface itself — read_dataset() takes any supported file through one entry point and detect_source() works out which software wrote it by inspecting contents, not just the suffix.
Whatagraph is turning a report from a document you send into a place clients come back to.
Whatagraph has been working on the parts of agency reporting that break under volume rather than on new analysis capability. Stored data removes live API calls from render time, connection failover keeps widgets alive when one teammate's token expires, and the Basis rebuild traded live loading for stored data to fix slow widgets and mismatched spend figures. Alongside that runs a steady stream of presentation control — automatic conditional formatting, per-metric decimal places, chosen comparison colors, consolidated theme settings.
aniread is the reader package of the animovement suite, importing output from pose-estimation, centroid and behavioural-scoring tools into aniframe objects. Through 0.5.x the work was per-reader: get_supported_sources() exposed the format list programmatically, read_boris() added behavioural events, and Octron and BORIS each got targeted fixes. 0.6.0 changes the shape of the interface itself — read_dataset() takes any supported file through one entry point and detect_source() works out which software wrote it by inspecting contents, not just the suffix.
The package is moving from a set of named readers to a dispatcher with the readers behind it, and the hard part is being handled rather than hidden: twelve sources emit .csv, so detection narrows by suffix then inspects content, and DeepLabCut and LightningPose files are structurally identical so it returns the combined 'deeplabcut/lightningpose' rather than guessing wrong. The honesty extends to gaps — optional-dependency detectors are skipped when the package is absent and the error names what was skipped, and SLEAP's csv suffix was withdrawn because auto-detection would have routed files into a reader that cannot read them. Alongside this, read_trackball() was substantially repaired for real two-sensor Bonsai captures, where alignment, clocks, corrupt rows and gap filling were each independently wrong.
Expect the withdrawn SLEAP csv suffix to return once read_sleap() gains support, since the changelog explicitly parks it against issue #87. Further detectors are the natural next increment, and the sensor-local-clock warning class suggests trackball alignment is not finished.
Whatagraph has been working on the parts of agency reporting that break under volume rather than on new analysis capability. Stored data removes live API calls from render time, connection failover keeps widgets alive when one teammate's token expires, and the Basis rebuild traded live loading for stored data to fix slow widgets and mismatched spend figures. Alongside that runs a steady stream of presentation control — automatic conditional formatting, per-metric decimal places, chosen comparison colors, consolidated theme settings.
The through-line is reliability and reader experience at agency scale, where one account runs hundreds or thousands of sources across several people. Report shortcuts extend that from inside a single report to the relationships between reports, letting a heavy report be split into a hub and supporting detail rather than one long scroll or five unlabeled links. Integration work continues to be additive and specific — Ahrefs Rank Tracker, WhatConverts, Snowflake, bol. — chosen to fill named reporting gaps rather than to broaden a catalog.
Expect the portal framing to get more structure — navigation, landing behavior or access controls on the entry-point report — since a hub built from a link widget will run into the limits of being just another report.
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 aniread or Whatagraph.
Omni ships weekly, and almost every week the headline item is an AI feature.
silx settles into maintenance a release after its PySide6 migration
Plotly is turning its cloud into a metered compute platform with an enterprise on-ramp.
Rho's release machinery finally produced a stable build — and it shipped no new product.
Usermaven closed the loop: data comes in from anywhere, and now it goes back out.
OpenCTI spends a release unblocking queues and hardening upserts
See all aniread alternatives → · See all Whatagraph alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Whatagraph is currently shipping more aggressively (velocity 5.0 vs 3.8), with 0 editorial sparks in the last 30 days against 1. 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. Whatagraph is currently shipping more aggressively (velocity 5.0 vs 3.8), with 0 editorial sparks in the last 30 days against 1. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top aniread alternatives in Analytics are ranked by recent ship velocity. Browse the "aniread alternatives" section above for the current picks, or visit /alternatives/aniread for the full list with editorial commentary on each.
Top Whatagraph alternatives in Analytics are ranked by recent ship velocity. Browse the "Whatagraph alternatives" section above for the current picks, or visit /alternatives/whatagraph for the full list with editorial commentary on each.