A · leads
amplify-js
93.6
9,556 stars · Apache-2.0
Analytics
amplify-js leads by 5.2 · narrow
A · leads
93.6
9,556 stars · Apache-2.0
B
88.4
13,157 stars · license n/a
amplify-js versus openreplay is a Analytics comparison assembled from public repository metrics, the license on file, and whether each product can be self-hosted. Both projects are written mainly in TypeScript. The composite score is 93.6 for amplify-js and 88.4 for openreplay.
openreplay has 13,157 GitHub stars to amplify-js's 9,556, a gap of 3,601 (1.38×). Forks are 2,171 for amplify-js and 891 for openreplay. On the log scale used inside this pair, adoption is 97 versus 100, and the fork community is 100 versus 88.
Push history: amplify-js was last pushed on 16 November 2026 (0 days ago), and openreplay was last pushed on 17 November 2026 (0 days ago). Open issues stand at 518 for amplify-js (0.054 per star) and 193 for openreplay (0.015 per star). Issue-health scores are 52 and 84; 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. openreplay is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. License scores in this pair are 96 for amplify-js and 30 for openreplay. This is a procurement signal, not legal advice.
In Analytics, both amplify-js (9,556 stars) and openreplay (13,157 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, openreplay is unpriced in this catalog.
The lead is split. amplify-js is furthest ahead on license flexibility (96 to 30), while openreplay is furthest ahead on issue health (84 to 52). Choose the dimension a rollout cannot compromise on.
amplify-js finishes ahead at 93.6 against openreplay at 88.4, a 5.2 point narrow margin under the published weights.
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 | openreplay |
|---|---|---|
| GitHub stars | 9,556 | 13,157 |
| Forks | 2,171 | 891 |
| Open issues | 518 | 193 |
| Adoption | 97 | 100 |
| Activity | 100 | 100 |
| Community | 100 | 88 |
| Issue health | 52 | 84 |
| License | 96 | 30 |
| Self-hosting | 100 | 100 |
| Composite | 93.6 | 88.4 |
A declarative JavaScript library for application development using cloud services.
Session replay, cobrowsing and product analytics you can self-host. Best for reproducing issues and iterating on your product.
openreplay has more GitHub stars: 13,157 versus 9,556 for amplify-js. The gap is 3,601 stars.
Both were last pushed on 16 November 2026.
Yes. This catalog marks both amplify-js and openreplay 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. openreplay is listed as no SPDX license on file, which this catalog treats as no clear license grant in the data stored here. Public code without a license is not free to use. Read both grants before you embed either codebase in a hosted product. This is not legal advice.
amplify-js scores 93.6 and openreplay scores 88.4. This page calls that a narrow lead for amplify-js.