← Back to home
Comparison · Analytics

aniread vs Umami

A side-by-side editorial comparison of aniread and Umami — release velocity, themes, recent moves, and the top alternatives to consider.

aniread vs Umami: at a glance

FeatureanireadUmami
SectorAnalyticsAnalytics
Velocity score3.80.0
Sparks · 30d10
Top themesanimal tracking, file formats, auto-detection, data importweb analytics, session replay, dashboards, security patches
Last editorial update13h ago19d ago
WebsiteVisit →Visit →

What is aniread?

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.

Read the full aniread trajectory →

What is Umami?

Umami spent late 2025 patching Next.js CVEs, then shipped Boards and Session Replay in v3.1.0.

The window splits sharply. Four of six releases are December 2025 patches across the v2 and v3 lines, all responding to the same Next.js and React security advisories plus Docker build breakage — several shipped within days of each other because the first fix updated Next.js without the affected React versions. Then v3.1.0 in April 2026 delivered custom dashboards as Boards, Session Replay, Web Vitals performance tracking, a redesigned share page, and a large batch of fixes.

Read the full Umami trajectory →

aniread vs Umami: editorial side-by-side

A
aniread
ANALYTICS
3.8

aniread stops asking you to know which tracker wrote the file

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

Umami logo
Umami
ANALYTICS
0.0

Umami spent late 2025 patching Next.js CVEs, then shipped Boards and Session Replay in v3.1.0.

◆ Current state

The window splits sharply. Four of six releases are December 2025 patches across the v2 and v3 lines, all responding to the same Next.js and React security advisories plus Docker build breakage — several shipped within days of each other because the first fix updated Next.js without the affected React versions. Then v3.1.0 in April 2026 delivered custom dashboards as Boards, Session Replay, Web Vitals performance tracking, a redesigned share page, and a large batch of fixes.

◆ Where it's heading

The security cluster is a framework dependency showing its cost — an analytics tool inheriting its release schedule from Next.js advisories. v3.1.0 is where product work resumes, and its content is telling: Session Replay and Web Vitals move Umami past pageview counting into behaviour and performance, which is the territory occupied by heavier commercial analytics rather than the lightweight privacy-first tools it grew up alongside.

◆ Prediction

Expect the next releases to build on Boards and Session Replay rather than return to the counting core, since both are new surfaces that arrived with a single release and no follow-up yet.

Alternatives to aniread and Umami

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 Umami.

See all aniread alternatives → · See all Umami alternatives →

Recent activity from aniread and Umami

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 23h agoanireadv0.6.0 — one entry point for every format
  2. 1mo agoanireadget_supported_sources(); Octron gap and BORIS index fixes
  3. 1mo agoanireadread_boris() imports behavioural events as anievent objects
  4. 3mo agoanireadread_octron() property selection, speed and a silent-recycling fix
  5. 3mo agoaniready-origin standardised to bottom-left across eleven readers
  6. 4mo agoUmamiv3.1.0: Boards, Session Replay and Web Vitals
  7. 8mo agoUmamiv3.0.3: Next.js security patch
  8. 8mo agoUmamiv2.20.2: Next.js security patch for the v2 line
  9. 8mo agoUmamiv2.20.1: React version fix and Docker build repairs
  10. 8mo agoUmamiv2.20.0: Next.js CVE fix for the v2 line
  11. 8mo agoUmamiv3.0.2: Next.js RSC vulnerability patch and UI fixes

Frequently asked questions

What is the difference between aniread and Umami?

They serve adjacent needs but don't currently overlap on shipped themes. aniread is currently shipping more aggressively (velocity 3.8 vs 0.0), with 1 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 aniread better than Umami?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. aniread is currently shipping more aggressively (velocity 3.8 vs 0.0), with 1 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 aniread?

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.

What are the best alternatives to Umami?

Top Umami alternatives in Analytics are ranked by recent ship velocity. Browse the "Umami alternatives" section above for the current picks, or visit /alternatives/umami for the full list with editorial commentary on each.