Open-source workout planning, honestly reviewed. No marketing copy, just what you get when you self-host it.

TL;DR

What it is: Open-source (MIT) fitness coaching platform — a 3-step workout builder with exercise database, progress tracking, and video demonstrations, running on your own server [README].
Who it’s for: Self-hosters and privacy-conscious fitness enthusiasts who want a clean workout planner without handing data to a SaaS subscription. Also trainers or gym operators who want to deploy a branded instance [README][1].
Cost savings: Most fitness SaaS apps (Trainerize, TrueCoach, Wodify) charge $10–$100+/mo per trainer or per seat. Workout.cool self-hosted runs on a VPS you already have, with no per-user cost.
Key strength: Origin story matters here — this is a genuine community rescue of a beloved project, built by the person who contributed most to the original. The exercise database includes free video demonstrations thanks to a real partnership [website].
Key weakness: Still an early-stage project (v1.3.2 at time of writing). The feature set covers the basics well but lacks the depth of mature commercial apps like Wodify or TrueCoach. Third-party coverage is thin, and premium pricing details aren’t published.

What is Workout.cool

Workout.cool is a self-hosted fitness coaching platform. In practice, it’s a three-step workout builder: choose your equipment (bodyweight, dumbbells, barbell, kettlebell, band, plates, pull-up bar, bench), select which muscle groups you’re targeting, then build a session from a filtered exercise database. Each exercise comes with detailed instructions and video demonstrations [website].

Beyond the builder, there’s a profile system, session history, progress statistics, a leaderboard, a programs section, and a tools area. The app is multilingual out of the box — English, French, Spanish, Chinese, Russian, and Portuguese [website].

The project is written in TypeScript, built on Next.js, backed by PostgreSQL, and runs on Docker. It’s sponsored by Vercel’s OSS program and funded voluntarily through Ko-fi. Community coordination happens on Discord [README].

The origin story is worth understanding because it explains both the project’s motivation and its current state. Workout.cool was built by Snouzy — the primary open-source contributor to an earlier project called workout.lol. That project was sold, the new owner couldn’t resolve the exercise video licensing costs, got sick, and abandoned it entirely. After 15 unanswered contact attempts over nine months, Snouzy rebuilt from scratch rather than watch the community’s work disappear [README][website]. The exercise video problem that killed the predecessor was solved through a partnership with Fit’Distance, which provides the video content for free [website].

As of this review, the GitHub repository sits at 7,131 stars with 570 forks and 37 open issues [1]. That’s meaningful traction for a project in the health-and-fitness category, where most self-hosted alternatives are either abandoned or extremely niche.

Why people choose it

The reviews available at this stage are sparse — Workout.cool doesn’t yet have the coverage of a Nextcloud or an n8n. AlternativeTo lists it with 20 likes and 55 alternatives [1], which puts it in the “discovered but not yet well-documented” tier. What the community activity does tell us:

The predecessor trauma is real. The reason Workout.cool has 7K+ stars despite being relatively new is that workout.lol had built a loyal user base, and those users were left without a maintained alternative when the project was sold. People are here partly for the tool and partly because the creator showed up when no one else would.

“No registration required” and “no tracking” matter. AlternativeTo users explicitly flagged these as important features [1]. In the fitness app world, this is significant — apps like MyFitnessPal have a documented history of selling user health data to insurers. A self-hosted platform where your workout history never leaves your server is a different risk profile entirely.

The free video database. The original workout.lol project died partly because video licensing was unaffordable. Workout.cool solved this structurally through a nonprofit-style partnership rather than by deferring the cost. That’s not a minor detail — it’s the same problem that killed the predecessor [README].

Features

Based on the README, website, and what’s visible from the deployed application:

Workout builder:

Three-step flow: equipment → muscle groups → exercises [website]
Supports bodyweight, dumbbells, barbell, kettlebell, resistance bands, weight plates, pull-up bar, and bench [website]
Exercise database with detailed instructions and video demonstrations (via Fit’Distance partnership) [README][website]
Custom workout creation [1]

Tracking and progress:

Progress tracking across sessions [README][1]
Session history via user profiles [website]
Statistics dashboard (/en/statistics) [website]
Leaderboard (/en/leaderboard) [website]

Programs:

Programs section (/programs) — structured training plans rather than one-off sessions [website]

Tools and accessibility:

Tools section (/en/tools) — exact contents not detailed in available data
No registration required for basic use [1]
Dark mode [1]
Multilingual: English, French, Spanish, Chinese, Russian, Portuguese [website]
Ad-free tier (premium removes ads) [website]

Technical stack:

Next.js frontend [website, inferred from URL paths]
PostgreSQL database [merged profile]
Docker and Docker Compose deployment [merged profile]
npm-based local dev [merged profile]

What’s missing from the picture: The README doesn’t expose an API, and there’s no mention of webhook integrations, third-party app sync (Garmin, Apple Health, Strava), or export formats. Data portability details are not documented in available sources.

Pricing: SaaS vs self-hosted math

Workout.cool has a premium tier — the “Remove Ads” button is visible on the live site — but the pricing page content was not captured in the available scrape data, so specific numbers aren’t available to cite honestly.

What we know:

The base app is usable without registration and without payment [1]
A premium tier exists, likely to remove ads and possibly unlock additional features [website]
The project accepts voluntary support via Ko-fi [README]

For comparison, the commercial fitness SaaS landscape:

Trainerize (trainer-facing): $10–$35/mo for solo trainers, climbs steeply with clients
TrueCoach: $19–$89/mo depending on client count
Wodify (gym management): $150–$300+/mo
MyFitnessPal Premium: $19.99/mo or $79.99/yr per user

If you’re a solo trainer managing your own workout plans, or a gym operator who wants a custom-branded planning tool, self-hosting Workout.cool on a $6–10/mo VPS gives you zero per-user cost, full data ownership, and MIT freedom to modify. The math favors self-hosting heavily compared to per-seat SaaS — the question is whether the feature set matches your requirements.

Deployment reality check

The deployment path is Docker Compose with PostgreSQL. The README covers quick start, exercise database import, and project architecture as dedicated sections — which suggests the maintainer has put real thought into making self-hosting accessible.

What you need:

A Linux VPS with Docker installed (2–4GB RAM should suffice for personal or small-group use)
Docker Compose
PostgreSQL (bundled in the compose setup or external)
A reverse proxy (Caddy or nginx) for HTTPS if you want a proper domain
The exercise database import step is explicitly called out in the README as a separate process — don’t skip it

What can go sideways:

The exercise database import is a non-obvious step. If you stand up the app without running it, you’ll get a working shell with an empty exercise library. The README flags this explicitly, which means it’s caught people off guard before.
One-click deploy is listed as a supported feature in the profile, but specific providers aren’t detailed in available data.
With 37 open issues as of this writing and a version number of 1.3.2, this is an actively developed but not fully mature project. Expect occasional rough edges.
No SSO or LDAP support is mentioned anywhere — each deployment is standalone, which is fine for personal use but limits multi-tenant or organizational deployments.

Realistic setup time for a technical user: 45–90 minutes to a working instance with exercises loaded. For someone following a guide without prior Docker experience: a half day, including domain setup.

Pros and Cons

Pros

MIT licensed, genuinely open source. Fork it, modify it, embed it in your own product — no commercial agreement needed [README][1].
Real exercise video library, free. The partnership with Fit’Distance solved the exact problem that killed the predecessor project. This is a structural fix, not a temporary workaround [README][website].
No registration required for basic use. Most fitness apps force an account before showing anything. Workout.cool lets you build a session immediately [1].
No tracking, no data broker risk. Self-hosted means your workout history doesn’t leave your infrastructure [1].
Active maintainer with skin in the game. This is someone who rebuilt rather than gave up. The 15 ignored emails and 9-month wait before forking is a signal about commitment [README][website].
Multilingual from v1. Six languages supported. Useful for deployers serving non-English communities [website].
Clean 3-step workflow. Equipment → muscles → exercises is exactly the decision tree a non-technical user would draw on paper. The UX reflects real understanding of how people plan workouts [website].

Cons

Young project, feature depth is limited. Programs, tools, and leaderboard exist but aren’t well-documented externally. Third-party integrations (Apple Health, Garmin, Strava, calendar export) are absent from any available description.
No public pricing for premium tier. If you’re evaluating the hosted version of Workout.cool, you can’t do the math without creating an account first.
No documented REST API. Programmatic access to workout data — for building custom dashboards, exporting to spreadsheets, or integrating with other tools — isn’t mentioned anywhere in available sources.
Data portability unclear. What happens to your history if you want to migrate to a different tool? Export formats and migration paths aren’t documented in available data.
Small community by comparison. 7K stars is good, but projects like n8n (100K+) or Nextcloud have orders-of-magnitude larger communities, which means more third-party guides, more integrations, and faster bug response.
Solo maintainer risk. Workout.lol was abandoned. Workout.cool exists because Snouzy stepped up once. If Snouzy steps back, the same risk applies. The project has Vercel OSS sponsorship and community contributors, but it’s not backed by a company [README].
Exercise database import is a manual step. Easy enough for a technical user, but a potential confusion point for a first-time self-hoster.

Who should use this / who shouldn’t

Use Workout.cool if:

You want a clean, self-hosted workout planner with a real exercise database and you don’t want to pay per month for the privilege.
You’re a personal trainer who wants to run your own planning tool without client data touching a third-party server.
You’re building something on top of it — a gym management tool, a fitness community platform, or a branded client app. MIT license means you can.
You have basic Docker fluency or are willing to spend an afternoon learning it.

Skip it for now if:

You need deep integrations with wearables (Garmin, Apple Watch, Fitbit) or health platforms (Apple Health, Google Fit). These aren’t present in available feature descriptions.
You’re running a commercial gym that needs member management, billing, class scheduling, or POS. That’s a different product category.
You need a stable, well-documented REST API for programmatic access.
You want multi-tenant support with SSO and centralized user management.

Stay on commercial SaaS if:

Your compliance requirements prohibit self-hosted infrastructure.
You need phone support and guaranteed uptime SLAs — Workout.cool is maintained by a community, not an enterprise vendor.
You want something a non-technical founder can set up in 10 minutes through a web wizard. This requires a terminal.

Alternatives worth considering

workout.lol — The direct predecessor. Mostly abandoned by its current owner, which is why Workout.cool exists [README]. Probably not a viable choice for new deployments.
LibreFit — Listed as an alternative on AlternativeTo [1]. Less documented, smaller community.
Liftlog — Popular alternatives listed by AlternativeTo [1]. More mobile-focused.
Jefit — Commercial fitness tracking app with a large exercise database. Not open-source, not self-hostable, but polished.
Hevy — Clean mobile workout tracker, closed-source, subscription-based. Better mobile UX, no self-hosting.
Strong — iOS-focused barbell training tracker. Not self-hostable, not open-source, but the best-in-class UI for pure strength tracking.
OpenBarbell / openlifter — For powerlifting-specific use, these cover more specialized ground.

For a non-technical founder who just wants something that works: the commercial options (Hevy, Strong, Jefit) are simpler to set up. For someone who prioritizes data ownership, cost control, or the ability to modify the software: Workout.cool is the only MIT-licensed, actively maintained option in this specific niche right now.

Bottom line

Workout.cool is a genuine community project solving a real problem: the fitness self-hosting space had a vacuum after workout.lol’s abandonment, and the person most qualified to fill it stepped up and did. The 7K stars it’s accumulated in less than a year of existence suggest the demand was real. What you get is a clean workout builder with a free video exercise database, Docker deployment, MIT license, and an active maintainer. What you don’t get (yet) is a mature feature set, wearable integrations, a public API, or the institutional backing that makes commercial tools feel “safe” to bet on long-term. For personal use or small-scale trainer deployments, the trade-off is clearly worth it. For anything requiring integrations, multi-tenant administration, or compliance, the feature gaps are real and not likely to close quickly. Worth watching — and worth contributing to if fitness tooling is in your domain.