wger
wger is a free, self-hosted fitness and workout tracker built with Django and Python. It offers workout routine creation, nutrition tracking via Open Food Facts, progress galleries, and a REST API—deployable via Docker with multi-user and multilingual support.
Key facts
Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.
| Field | Value |
|---|---|
| Repository | wger-project/wger |
| Owner | wger-project |
| Primary language | Python |
| License | AGPL-3.0 — OSI-approved |
| Stars | 6.4k |
| Forks | 930 |
| Open issues | 257 |
| Latest release | 2.6 (2026-06-17) |
| Last updated | 2026-07-07 |
| Source | https://github.com/wger-project/wger |
What wger is
Django-based Python application providing a REST API for fitness management, with PostgreSQL backend (implied by Docker Compose), support for cross-platform mobile clients (Flutter), and integration with Open Food Facts for nutritional data. Self-hostable via containerized deployment.
Get the wger source
Clone the repository and explore it locally.
git clone https://github.com/wger-project/wger.gitcd wger# follow the project's README for install & configurationNeed it deployed, integrated, or customized instead? DEV.co ships production installs.
Best use cases
Implementation considerations
- AGPL-3.0 copyleft requires review before integrating into proprietary systems or SaaS offerings; network use triggers source disclosure obligations.
- Self-hosting requires operational overhead: database administration, backups, monitoring, security patching, and infrastructure maintenance.
- Data model and API schema should be reviewed against your specific nutrition tracking and workout reporting requirements before commitment.
- Mobile client availability (Android, iOS, Flutter) suggests mature UI/UX, but verify that cross-platform feature parity meets your mobile-first needs.
- Open Food Facts integration depends on third-party data quality and availability; consider caching strategy and fallback nutrition databases.
When to avoid it — and what to weigh
- Require Enterprise SLA & Guaranteed Support — wger is community-maintained without commercial support contracts, incident response SLAs, or vendor accountability guarantees.
- Need High-Volume Multi-Tenant SaaS — While multi-user is supported, the architecture is optimized for self-hosted single or small-group deployments, not hyperscale SaaS operations.
- Complex Medical/Clinical Integration — wger is a fitness tracker, not a medical device or clinical platform. No data on HIPAA compliance, clinical validation, or medical-grade audit trails.
- Proprietary, Closed-Source Requirement — AGPL-3.0 licensing mandates source disclosure if deployed as a service; commercial proprietary modifications are not permitted without separate licensing.
License & commercial use
Licensed under AGPL-3.0-or-later. Exercise and ingredient data use Creative Commons (individual entries); documentation is CC-BY-SA-4.0. AGPL-3.0 is a copyleft license: any modifications or network deployment trigger source disclosure obligations.
AGPL-3.0 permits commercial use of the unmodified application in internal contexts. However, if deployed as a network service (SaaS, hosted offering, or accessible over a network), you must provide source code access to users. Proprietary modifications or closed-source SaaS offerings require explicit license negotiation or dual-licensing; contact maintainers for commercial licensing terms. Internal business use of the unmodified code is permitted.
DEV.co evaluation signals
Editorial assessment — not user reviews. Directional, with an explicit confidence level.
| Signal | Assessment |
|---|---|
| Maintenance | Active |
| Documentation | Strong |
| License clarity | Clear |
| Deployment complexity | Moderate |
| DEV.co fit | Good |
| Assessment confidence | High |
Deployment is self-hosted, placing security responsibility on the operator. Standard practices should include: network isolation, TLS/SSL termination, database access controls, regular dependency updates, and input validation review. Multi-user authentication and authorization mechanisms exist but require security audit in your threat model. No public security advisories or CVE history provided; review GitHub security tab and dependency scanning. User-uploaded photos (progress gallery) require storage security and access control considerations.
Alternatives to consider
MyFitnessPal / Cronometer
Proprietary SaaS with extensive food database and device integrations; no self-hosting option. Simpler UX but vendor lock-in and privacy trade-offs.
Strong Workout Tracker
Lightweight mobile-first application with freemium model. Less comprehensive nutrition tracking; no self-hosting. Minimal operational burden vs. wger's self-hosting complexity.
OpenFit / FitBod
Open-source or semi-open fitness platforms; verify licensing and feature parity. Consider architectural differences and community maturity vs. wger's 13-year history.
Build on wger with DEV.co software developers
Review the deployment guide, test the API, and assess AGPL-3.0 licensing implications for your use case. Contact the maintainers for commercial licensing questions.
Talk to DEV.coRelated on DEV.co
Explore the category and the services that help you build with it.
wger FAQ
Can we use wger in a commercial SaaS product?
What is the learning curve for self-hosting?
Is nutrition data accurate and up-to-date?
What support options are available?
Software developers & web developers for hire
DEV.co helps companies turn open-source tools like wger into production software. Our software development services cover the full lifecycle — architecture, web development, integration, and maintenance — delivered by software developers and web developers who ship. Engage our software development agency to implement or customize it for your open-source devops stack.
Evaluate wger for Your Fitness Platform
Review the deployment guide, test the API, and assess AGPL-3.0 licensing implications for your use case. Contact the maintainers for commercial licensing questions.