openGym — A self-hosted gym & body-weight tracker you actually own, with no subscriptions or ads.
Analyzed by Sai Pavan Gopularam · Fitness · Self-Hosted · View on GitHub
- Stars: 6671
- Forks: 1111
- Commits last 30 days: 0
- Health: Slowing (last push 33d ago)
- Language: JavaScript
- License: AGPL-3.0
What It Is
Imagine a sophisticated fitness tracking app like MyFitnessPal or Strong, but instead of your data living on some company's servers, it runs entirely on your own computer or server. openGym is a self-hosted web application that lets you plan workouts, track sets, monitor body weight, and view progress, all under your control.
This matters because it eliminates subscription fees, protects your privacy from data harvesting, and ensures your fitness history won't disappear if a startup folds. It's a modern, feature-rich alternative for anyone serious about owning their personal health data.
License Verdict
AGPL-3.0 License — Careful with Commercial SaaS — Strong Copyleft • Source Code Must Be Shared for Network Services
The AGPL-3.0 license means you can use, modify, and distribute openGym freely. However, if you run a modified version of openGym as a network service (e.g., a SaaS offering), you *must* make the source code of your modified version available to all users of that service. This makes building a proprietary SaaS directly on openGym very difficult, as all your changes would need to be open-sourced.
How to Use It
Set up openGym on your own server using Docker. Clone the repository, copy the example environment file, and bring up the containers. It handles all dependencies internally, including the frontend build.
Prerequisites:
- Docker with Compose
Estimated setup time: 10 minutes.
git clone https://github.com/DuarteSantos8/openGym
cd openGym
cp .env.example .env
docker compose pull
docker compose up -d
What I'd Build With This
Managed openGym Hosting Service (micro-saas)
Offer a fully managed, hosted version of openGym for individuals or small groups who want the privacy and data ownership without the hassle of self-hosting. You handle the server setup, updates, backups, and domain management. Market this to privacy-conscious fitness enthusiasts or small personal training studios.
Effort: 1 Week Build Time · Target: Privacy-Conscious Individuals, Small Fitness Studios · Pricing: $15-25/mo per user
Custom openGym Deployment & Support for Gyms (saas)
Provide a service to independent gyms and fitness studios: deploy, customize (e.g., branding, specific exercise routines), and maintain openGym on their own infrastructure or a dedicated cloud instance. This allows them to offer a branded, private workout tracker to their members without recurring third-party SaaS fees. You'd charge for setup and ongoing support.
Effort: 2 Weeks Build Time · Target: Independent Gym Owners, Fitness Studios · Pricing: $500 setup + $100/mo support
Corporate Wellness Program with On-Premise Tracker (enterprise)
Sell a fully managed, on-premise deployment of openGym to corporations for their employee wellness programs. Companies get a private, secure fitness tracking solution that can be integrated with internal HR systems for challenges or gamification. This offers a highly customizable and private solution for employee well-being, avoiding external data privacy concerns.
Effort: 1 Month Build Time · Target: Large Corporations, HR Departments · Pricing: $5k setup + $500/mo enterprise support
Sai Pavan Gopularam's Take
openGym is a fantastic example of the 'own your data' movement in fitness. The feature set is richer than many paid apps, and the self-hosted model gives users true control. The AGPL license is a big hurdle for traditional SaaS, but there's a clear opportunity to build a profitable managed hosting service, easily generating $5k/month by serving privacy-conscious fitness enthusiasts.
Watch Out For
- AGPL Licensing: The AGPL-3.0 license is highly restrictive for commercial SaaS. If you modify openGym and offer it as a network service, you are legally required to provide the full source code of your modified version to your users.
- Self-Hosting Barrier: While powerful, self-hosting requires some technical comfort with Docker and server management. This limits the addressable market for direct end-user sales unless a managed service is provided.
- No App Store Distribution: The project deliberately avoids official app stores. iOS users must self-host and use the PWA, or build from source. Android users can sideload an APK, which might deter less technical users.
- Standalone App Limitations: The standalone mobile app (Android APK) does not offer multi-device sync or user profiles; these features are only available when self-hosting the full web application.
I break down trending repos like openGym every week — join the newsletter.