Product
One loop. Every role. The whole box.
Program → book → train → log → share → return. Owners, coaches and members aren't three products duct-taped together — they're three views of the same system.
Product design preview · fictional gym data
The system
Five arguments, one platform.
Programming
A workout is not a calendar event. Structure is what makes everything downstream computable.
Go deeper →The floor
A class is a promise about capacity. Waitlists act, check-in is five configurable factors, coaches are visible capacity.
Go deeper →The loop
Members who see progress don't cancel. Logging costs one thumb; the room sees it live.
Go deeper →Community
Stop renting your community from Instagram. Inside: owned. Outside: branded.
Go deeper →The business
Seven payment channels, self-service with real math, waivers that are documents.
Go deeper →One system, four screens
Web, phone, TV, done.
Most gym software ships a web app, bolts on a "member app" as an afterthought, and treats the TV on the wall as a demo you'll get to later. RxWOD doesn't have four products pretending to sync — it has one system with four surfaces. The owner's browser, the coach's browser, the member's phone, and any TV bolted to the wall of the box all read the same programming, the same roster, the same scores. Change a WOD in the browser and it's already on the TV before the chalk comes out.
Product design preview · fictional gym data
Under the hood
Multi-tenancy enforced by the database, not by hope.
Every SaaS claims to be multi-tenant. Most of it means a
tenant_id column and a promise
that every query remembers to filter on it — a promise that holds
until, someday, one query doesn't, and Box A sees Box B's roster.
RxWOD enforces isolation at the database layer with row-level
security: a query that forgets to scope by tenant doesn't leak data,
it returns zero rows.
White-label subdomain per gym
Custom domains with SSL
7 staff-to-member roles
Row-level tenant isolation
6 languages incl. RTL Arabic
EU + US hosting
Export everything, always
Running the box is half the job — the growth layer is the roadmap. See where it's going on the owners page.
See it on your box