Dreeve

Statistics dashboard generated from Strava data.

Thriving · 84
84/100
Thriving

High commit volume, frequent releases and growing activity.

Maintenance 34/40
Releases 25/25
Community 10/20
Momentum 15/15

Commit activity more than 85% of tracked projects; popularity more than 51%. How this is calculated.

Commits, last 11 months

2025-12: 195 commits 2026-01: 139 commits 2026-02: 199 commits 2026-03: 112 commits 2026-04: 42 commits 2026-05: 0 commits 2026-06: 0 commits 2026-07: 1 commits 2026-08: 323 commits 2026-09: 126 commits 2026-10: 540 commits
2025-12 1677 total 2026-10
Stars2.2k
Latest releasev5.9.0 · 15 Nov 2026
Repo updated19 Nov 2026
LicenceAGPL-3.0
Built withDocker, K8S

Is Dreeve actively maintained?

Over the last 11 months the project absorbed 1677 commits, of which 989 arrived in the most recent quarter — roughly 330 commits a month.

Activity is accelerating: the last quarter carried 98800% more commits than the one before it.

The most recent tagged release, v5.9.0, shipped within the last month — a current, installable version exists today.

Note that Dreeve depends on a third-party service to work fully. It is self-hosted, but not self-contained: if that external service changes its terms or disappears, your instance is affected.

Dreeve ranks #10 of 32 in Analytics, placing it mid-table for maintenance activity.

What Dreeve actually does

Dreeve is a self-hosted analytics dashboard designed to process and display fitness data sourced from Strava. It provides a centralised interface for reviewing activity statistics and performance metrics outside of the proprietary platform. The application is distributed under the AGPL-3.0 licence.

Best fit: It suits athletes and developers who want to own their historical Strava data and view aggregated analytics on a private server.

Worth knowing: With a small community and low repository visibility, you may need to troubleshoot issues independently if upstream development slows down or integration endpoints change.

Deployment notes

Because it packages as container images, you will typically run it via Docker or Kubernetes with persistent volumes configured for data storage and a reverse proxy to handle TLS termination.


Dreeve as a replacement for


Alternatives to Dreeve

Projects in the same categories, ordered by health score.