A · level
amplify-js
91.3
9,556 stars · Apache-2.0
Analytics
Too close to call · 91.3 to 90.9
A · level
91.3
9,556 stars · Apache-2.0
B · level
90.9
22,032 stars · GPL-3.0
amplify-js versus Matomo is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. amplify-js is written mainly in TypeScript; Matomo is written mainly in PHP. The composite score is 91.3 for amplify-js and 90.9 for Matomo.
Matomo has 22,032 GitHub stars to amplify-js's 9,556, a gap of 12,476 (2.31×). Forks are 2,171 for amplify-js and 2,938 for Matomo. On the log scale used inside this pair, adoption is 92 versus 100, and the fork community is 96 versus 100.
Push history: amplify-js was last pushed on 16 November 2026 (0 days ago), and Matomo was last pushed on 17 November 2026 (0 days ago). Open issues stand at 518 for amplify-js (0.054 per star) and 2,563 for Matomo (0.116 per star). Issue-health scores are 52 and 52; activity scores are 100 and 100.
amplify-js is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Matomo is listed as GPL-3.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. License scores in this pair are 96 for amplify-js and 64 for Matomo. This is a procurement signal, not legal advice.
In Analytics, both amplify-js (9,556 stars) and Matomo (22,032 stars) are marked self-hostable. Deploy scores are 100 and 100. Running either one means you own upgrades, backups, and the license duties that follow a modified copy. Pricing labels on file: amplify-js is open source, Matomo is open source.
The lead is split. amplify-js is furthest ahead on license flexibility (96 to 64), while Matomo is furthest ahead on adoption (100 to 92). Choose the dimension a rollout cannot compromise on.
Composite score: amplify-js 91.3, Matomo 90.9. The margin is under one point, so this page calls a tie. Use the dimension breakdown rather than the headline number.
Scores are computed inside this pair only. Method and weights.
Bars are scaled within the row. Higher is stronger. Open issues are a raw count, so that row has no bar.
| Signal | amplify-js | Matomo |
|---|---|---|
| GitHub stars | 9,556 | 22,032 |
| Forks | 2,171 | 2,938 |
| Open issues | 518 | 2,563 |
| Adoption | 92 | 100 |
| Activity | 100 | 100 |
| Community | 96 | 100 |
| Issue health | 52 | 52 |
| License | 96 | 64 |
| Self-hosting | 100 | 100 |
| Composite | 91.3 | 90.9 |
A declarative JavaScript library for application development using cloud services.
Matomo is a web analytics platform built as a privacy-oriented alternative to Google Analytics. It has a long plugin history and is designed to run on your own server.
Matomo has more GitHub stars: 22,032 versus 9,556 for amplify-js. The gap is 12,476 stars.
Both were last pushed on 16 November 2026.
Yes. This catalog marks both amplify-js and Matomo as self-hostable. Confirm each project's deploy docs before you plan a migration.
amplify-js is listed as Apache-2.0, which this catalog treats as a permissive grant. A company can usually ship it inside a commercial product and keep its own application code private, provided it keeps the copyright notice. Matomo is listed as GPL-3.0, which this catalog treats as a strong copyleft grant. Distributing a modified binary typically means offering the corresponding source of that program. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
Neither tool clears a one-point margin. amplify-js scores 91.3 and Matomo scores 90.9.