The Coach
- Sees who needs attention
- Understands each client
- Builds training and nutrition
- Reviews health and AI drafts
- Sends only approved work
Start here
Olyv connects two people
The Coach decides what the client needs. The Client completes the work. Olyv carries information between them safely and keeps the whole journey in one place.
Olyv
- Shows each person the right screens
- Moves requests to the right service
- Runs coaching engines and reminders
- Protects records and private files
- Brings progress back to the Coach
The Client
- Sees the next clear step
- Completes forms and assessments
- Follows the published plan
- Records meals, training and habits
- Messages the Coach and sees progress
Coach gives direction
Creates, checks and publishes.
Client creates real-life feedback
Completes, follows and records.
The full map
Every major part, in one picture
The top row is what people see. The middle row is the hidden Olyv machinery. The bottom row is outside services reached through controlled routes.
Coach
Client
Olyv app
Cloudflare
Engines
Supabase
Outside connections
1. Coach StudioThe Coach understands the client, creates work, and reviews it.
uses
2. Olyv appShows Coach and Client different tools inside one connected product.
routes the action
3. Cloudflare front deskServes the app, checks privileged requests, runs queues, timers and private jobs.
4. Coaching enginesPrepare Bloodwork, DNA, Training, Nutrition, Supplement and Protocol work.
5. Supabase private vaultKeeps login, structured records, private files, messages and live updates.
returns the right result
6. Client HomeThe Client sees the next step, follows the plan and records progress.
Outside connectionsEmail, voice, food lookup, push alerts, optional AI providers and DNA analysis connect through controlled routes.
The most important idea. Coach and Client never use separate databases. They see different, permission-controlled views of the same coaching journey.
Who does what
One app, two role experiences
The real app has many pages. For a human reader, they make more sense as rooms with one clear job.
Coach app
1. Clients
Invite, open a client file, see the journey.
2. Build
Create training, nutrition, supplements and final protocols.
3. Review
Review health reports, view Body Scan results, and check AI drafts and changes.
4. Talk
Messages, email, calendar, community and challenges.
5. Monitor
Check-ins, habits, workouts, progress and attention flags.
Client app
1. Today
See one clear next step and current journey status.
2. My plan
Training, meals, supplements and final protocol.
3. Record
Workouts, meals, habits, sleep, water, check-ins and scans.
4. Talk
Messages, assistant, community and resources.
5. My results
Progress, tests, reports, photos, calendar and profile.
A client’s journey
From invitation to better coaching
This is the main business story. Blue steps belong to the Coach, green steps belong to the Client, and purple steps are Olyv engine work.
Coach invites
Creates the client and selects the right starting pathway.
Client joins
Installs Olyv, creates a password and enters the private journey.
Client explains
Completes onboarding, training and nutrition forms.
Client adds evidence
Uploads tests and records measurements when needed.
Engines prepare
Rules and approved AI turn the information into drafts and findings.
Coach checks work that needs review
Edits, accepts or rejects it before normal client delivery.
Coach publishes plans and reports
Sends the approved program, meal plan, report or protocol.
Client follows
Uses today’s plan and records what actually happened.
Progress returns
Workouts, meals, habits, check-ins and messages flow back.
The loop improves
The Coach sees the new picture and adjusts the next plan.
Body Scan takes a direct route. After the Client completes it, the result appears automatically—without Coach approval—and is also visible in the Client profile for the Coach. Plans and other Coach-produced reports continue through review and publication.
Behind the screen
What happens when someone taps a button
Olyv chooses a protected route for each action. Simple record changes can go directly to the private vault. Privileged, AI, scheduled, health and outside-service work goes through Cloudflare first.
1. A person acts
Opens a screen, saves an answer, uploads a file or asks Olyv to create something.
secure request→
2. Cloudflare checks
Confirms who is asking, routes the request, and runs protected work.
processes with→
3. Engines help
Rules, AI, queues, timers or the private DNA service prepare a result.
stores safely→
4. Supabase keeps it
Login, records, messages and private files are saved with access rules.
The coaching engines
Understand the person
Fitness, lifestyle and body composition.
Understand health
Bloodwork and private DNA analysis.
Build the plan
Training, nutrition and supplements.
Bring it together
Final protocol, sources and progress context.
External routes
Email
Approved messages leave through a signed Gmail gateway.
Voice
Cartesia can turn assistant text into Olivia’s cloned voice.
Food lookup
Open Food Facts answers barcode searches.
Push alerts
Apple, Mozilla and Google web-push routes can notify a device.
AI providers
Cloudflare AI is active; Coach-selected providers are also supported.
DNA service
A private Cloudflare container analyzes capped DNA files.
Simple browser links
Exercise videos and the MyHeritage ordering page open directly. They are not Olyv service integrations.
Privacy and control
Four layers control access
Seeing a screen is not enough. The data layer checks the person and the exact record again before allowing access.
Supabase login proves the signed-in identity.
Coach and Client are sent to different parts of Olyv.
Tenant and client ownership rules restrict access to sensitive records and files.
Consent and publication rules decide whether a Coach or Client may see it.
Private input
Forms, tests, photos, measurements and logs.
Controlled output
Reviewed reports, published plans and client-safe results.