Perform is a coaching platform for fitness studios. A studio’s coaches work in a web dashboard. Their trainees use a mobile app that carries the studio’s own logo and colours. One backend serves both. The product is built for the Israeli market first. Hebrew is the default locale and the interface is right to left by default. The web translations cover he, en, ar, de, es and fr.

The three surfaces

Older notes in the repositories say that authentication and billing live in the web repository. That changed with the server consolidation. The better-auth server, the payments package, the mail package and the storage package now run inside the core API process. The web app keeps only the better-auth client and a proxy route. See System architecture.

What coaches and trainees do

Coaches manage trainees, sell plans, build training and nutrition programs from templates, maintain exercise and food libraries, send forms and check-ins, review technique videos, publish content, and run automations that create tasks and send WhatsApp messages. Trainees sign in with a phone number and a one-time code sent over WhatsApp. They follow workouts, log meals, water, weight and steps, fill in forms, and read the content their studio publishes.

How these docs are organised

Overview

Architecture, repositories, tech stack, local setup, environment variables, conventions and a glossary. Start here.

Operations

Deployments, database migrations, health checks, logging, mobile builds, over-the-air updates and troubleshooting.

API reference

Every route group of the core API with parameters, responses and errors.

Coach guide

The non-technical guide for studio owners and coaches. Useful for learning the product vocabulary.
Other sections of the developer docs cover backend internals, the data model, integrations, and the internals of the web and mobile apps. The pages in this section stay at the cross-repository level.

Suggested reading order

1

Understand the shape of the system

2

Get it running

Follow Local setup. Keep Backend environment variables and Web and mobile environment variables open while you fill in the env files.
3

Learn the rules before your first commit

4

Learn the vocabulary

The Glossary maps product words such as studio, trainee, plan and check-in to the models and modules that implement them.

Public URLs