openGym: A Self-Hosted Fitness Tracker That Puts You in Control of Your Data

An Open-Source Fitness App That Returns Data Ownership to Users

At a time when mainstream fitness tracking apps largely rely on subscription models and cloud storage, an open-source project called openGym is rapidly gaining traction on GitHub. Published by developer DuarteSantos8, the project has a clear core mission: a self-hosted fitness and weight tracking tool built around the principle of "your data, your server."

The project's recent growth has been impressive — it has accumulated 3,409 GitHub Stars and 585 Forks, with 570 new stars added in a single day. That kind of single-day growth typically signals that a project has tapped into a genuine, unmet need. Built with JavaScript, openGym keeps the bar relatively low for both deployment and further development.

Feature Coverage: A Complete Loop from Planning to Training Feedback

Based on the project description, openGym is far more than a simple workout log — it aims to cover the full training lifecycle.

Workout Planning and Logging

Users can plan routines in advance and log specific exercises during each session. Notably, it supports recording supersets, warm-ups, and cardio. These are scenarios that many lightweight logging tools overlook — most apps only handle the standard "sets × reps × weight" format and fall short when it comes to distinguishing supersets from warm-up sets. In this regard, openGym feels much more attuned to the needs of serious lifters.

Muscle State Visualization

One of the standout features is muscle state feedback: the system can display which muscles are currently being trained, which are fatigued, and which are detrained. This kind of muscle-group load estimation — derived directly from your training history — is genuinely useful for planning split training, avoiding overtraining, and identifying neglected muscle groups. It takes what would otherwise require mental tracking and planning and turns it into intuitive visual feedback.

The functionality behind this relies on exercise science models of training adaptation and recovery. A common implementation approach tracks the last training time and volume for each muscle group, combined with empirical recovery parameters (e.g., large muscle groups typically need 48–72 hours), to estimate current state. The "detrained" dimension is particularly noteworthy — it alerts users when a muscle group has gone past its normal recovery window without stimulation, which over time can lead to muscle loss or strength imbalances. This three-state visualization is uncommon even among commercial products. While Garmin's Body Battery and some professional sports apps offer fatigue indices, tracking status at the individual muscle-group level usually requires a paid subscription.

Data Migration and Login Experience

For users looking to switch from existing tools, migration costs are often the biggest obstacle. openGym directly supports importing data from three popular fitness apps: FitNotes, Strong, and Hevy. All three are well-known in the fitness community, and supporting their export formats significantly reduces the friction for existing users — a clear sign that the project author has a sharp understanding of their target audience.

For authentication, openGym uses passkeys. Compared to traditional username-and-password logins, passkeys are based on public-key cryptography — no passwords to remember, and strong resistance to phishing attacks. In a self-hosted context, this both improves security and simplifies the user experience.

Passkeys are a next-generation authentication standard developed by the FIDO Alliance and W3C, with full platform rollouts from Apple, Google, and Microsoft between 2022 and 2023. Here's how they work: during registration, the device locally generates a public-private key pair; the private key never leaves the device (typically protected by the system's secure enclave), while only the public key is stored on the server. At login, the user authenticates locally via biometrics (Face ID, fingerprint, etc.) or a device PIN, and the private key signs a random challenge issued by the server. Since there's no password to steal and no login page to spoof, passkeys fundamentally eliminate the threats of credential stuffing and phishing. In a self-hosted scenario, this means that even if the server database is compromised, attackers gain no credentials that could be used to log in.

The Case for Self-Hosting — and Its Trade-offs

"Self-hosted" is the defining characteristic that sets openGym apart from commercial apps. It means all training data is stored on your own server, never passing through a third-party cloud — eliminating the risk of data being used for analytics or advertising, or disappearing if the service shuts down. For privacy-conscious users or those who already run a home server (NAS, homelab), this is a compelling selling point.

Of course, self-hosting comes with trade-offs. It requires some level of deployment and maintenance knowledge, and it can't match the plug-and-play convenience of a commercial app. This means openGym's early adopters will primarily be technically inclined fitness enthusiasts. That said, with a JavaScript stack and an active open-source community, the barrier to entry should drop steadily as documentation and one-click deployment options mature.

Conclusion

openGym represents the spread of "data sovereignty" thinking into niche tool categories — a trend that has gained real momentum in recent years. With a fairly complete feature set — workout planning, supersets and cardio logging, muscle state visualization, multi-source data import, and passkey authentication — it demonstrates that open-source, self-hosted solutions can come close to or even surpass the experience of commercial products. For fitness enthusiasts tired of subscription fees and cloud lock-in, this is a project worth watching. Its near-term growth curve and community feedback will be key indicators of whether it can develop into a sustained, long-term project.