What it is
Source: My own description of Olympian Protocol OS; WHOOP’s developer documentation for context. Date: 15 October 2026. Scope: What the app is, what it is built with and around, and which WHOOP data it uses. It claims no training results and no health outcomes.
Olympian Protocol OS is a personal fitness coaching app built around a 28-week performance plan. It is built with Next.js 15 and Supabase, and it uses recovery data from WHOOP. Built
WHOOP is a wearable that monitors physiological signals continuously. Its developer platform lets an app read a member’s data on Strain, Recovery, Sleep and Workouts, with the member’s permission.
What it does
- Fitness coaching. The coaching is organised around the performance plan.
- WHOOP recovery data. The app uses data from WHOOP’s Recovery, which WHOOP describes as a daily measure of how prepared the body is to perform (WHOOP 101).
How it is built
The app is built with Next.js 15, a React framework for building full-stack web applications, and Supabase, which describes itself as the Postgres development platform providing the backend features a product needs. Built It connects to WHOOP through OAuth, the standard WHOOP uses to ask a member’s consent before an app can access their data (WHOOP).
Stack. Next.js 15, Supabase, WHOOP OAuth
Where it stands
Its stage is not stated here yet. Nothing on this page claims training results or health outcomes.
My part
I designed and built Olympian Protocol OS. Built
