Repohistory vs Replayowl
A side-by-side comparison built from both listings. Blank cells mean the company has not given that detail; we never guess.
| Detail | Repohistory | |
|---|---|---|
| What it does | GitHub repository analytics tool that tracks traffic history beyond GitHub's 14-day limit | Session replay that shows what your visitors saw |
| Stage | Not given | Not given |
| Founded | Not given | Not given |
| Based in | Not given | Not given |
| Pricing model | Freemium | Not given |
| Pricing | Free: $0 per month (1 repository, traffic history beyond 14 days, advanced analytics & insights, data export); Pro: $7.5 per month billed yearly (unlimited repositories, all Free features, user/org traffic overview, priority support) | Free: $0/month with 1,000 sessions/month, kept 30 days, 1 project, 3 team members. Pro: $29/month with 10,000 sessions/month, 90 days retention, 5 projects, 10 team members. Business: $149/month with 100,000 sessions/month, 365 days retention, 50 projects, 100 team members. Self-hosted: $0 with no s |
| Key features |
|
|
| What makes it different |
|
|
| Community votes | 0 | 0 |
| DR (Domain Rating by Ahrefs) | 37 no change since last check | 1 +1 (up) since last check |
| Trust Flow (Majestic) | 6 | 2 |
| Citation Flow (Majestic) | 20 | 20 |
| Referring domains (Majestic) | 59 | 8 |
4 details filled in for both companies.
More alternatives to Repohistory More alternatives to Replayowl