← Back to home
Comparison · Analytics

aniread vs Matomo

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

aniread vs Matomo: at a glance

FeatureanireadMatomo
SectorAnalyticsAnalytics
Velocity score3.82.5
Sparks · 30d10
Top themesanimal tracking, file formats, auto-detection, data importprivacy-first analytics, ai-traffic, ui modernization, compliance
Last editorial update10h ago3mo 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 Matomo?

Matomo bets on AI-traffic measurement as its differentiator while modernizing the UI for upmarket buyers.

Matomo is on a near-monthly minor-release cadence threading three concurrent themes: AI-traffic instrumentation, visual modernization (dark mode and theme refresh in 5.10.0), and privacy-compliance shortcuts aimed at EU operators. Patch releases land between minors with security and archiving fixes, and the team still ships occasional Matomo 4 backports for legacy customers.

Read the full Matomo trajectory →

aniread vs Matomo: 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.

Matomo logo
Matomo
ANALYTICS
2.5

Matomo bets on AI-traffic measurement as its differentiator while modernizing the UI for upmarket buyers.

◆ Current state

Matomo is on a near-monthly minor-release cadence threading three concurrent themes: AI-traffic instrumentation, visual modernization (dark mode and theme refresh in 5.10.0), and privacy-compliance shortcuts aimed at EU operators. Patch releases land between minors with security and archiving fixes, and the team still ships occasional Matomo 4 backports for legacy customers.

◆ Where it's heading

After introducing AI-agent detection in 5.6.0 and dedicated AI chatbot traffic reports in 5.8.0, Matomo is positioning itself as the analytics tool that explicitly accounts for non-human traffic — a stance neither GA4 nor Plausible has taken head-on. The 5.9.0 one-click CNIL preset and 5.10.0 UI overhaul read as moves to broaden the buyer pool beyond technical self-hosters.

◆ Prediction

Expect deeper AI-traffic features — segmentation, attribution, and per-agent breakdowns — plus the one-click compliance pattern extended from CNIL to other regulators.

Alternatives to aniread and Matomo

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

See all aniread alternatives → · See all Matomo alternatives →

Recent activity from aniread and Matomo

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

  1. 20h 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. 3mo agoMatomoMatomo 5.10.0
  7. 3mo agoMatomoMatomo 5.9.0
  8. 5mo agoMatomoMatomo 5.8.0
  9. 6mo agoMatomoMatomo 5.7.1
  10. 6mo agoMatomoMatomo 5.7.0
  11. 8mo agoMatomoMatomo 5.6.2

Frequently asked questions

What is the difference between aniread and Matomo?

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

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

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