Statistics for Strava vs Umami
| Tagline | Self-hosted statistics dashboard for your personal Strava activity data | Simple, fast, privacy-focused web analytics in a single lightweight dashboard |
| Category | Product & Web Analytics | Product & Web Analytics |
| Replaces | Google Analytics, Hotjar | Google Analytics |
| GitHub stars | 1.8k | 37k |
| Language | Docker | TypeScript |
| License | AGPL-3.0 | MIT |
| Self-host difficulty | 3/5 Moderate | 3/5 Moderate |
| Deploy options | Docker Docker Compose | One-Click Docker Docker Compose Manual |
| Managed hosting | ||
| Last updated | yesterday | yesterday |
| View repo | View repo |
Where each falls short
The honest trade-offs — what you give up with each, versus the proprietary tools they replace.
Statistics for Strava
- Limited to Strava as a data source; no support for Garmin, Wahoo, or other fitness platforms
- Read-only analytics — no goal setting, training plans, or social features
- No mobile app; dashboard is web-only
- Requires a valid Strava API OAuth application to be configured before first run
Umami
- Deliberately minimal: no heatmaps, session replay, or deep product-analytics like funnels/retention found in Mixpanel/Amplitude.
- Event/custom-property analytics are basic compared to dedicated product-analytics tools.
- No built-in alerting or anomaly detection.
Bottom line
Both are a similar lift to self-host; choose Umami for the larger community and ecosystem. Open each guide below for deploy steps and the full feature gap.
Statistics for Strava
Self-hosted statistics dashboard for your personal Strava activity data
Umami
Simple, fast, privacy-focused web analytics in a single lightweight dashboard