integrations

one system, on purpose.

Trainbase ships no third-party integrations today. We say that plainly because the reason is the product itself: most integrations exist to stitch four separate apps into one picture, and Trainbase was built so the picture is never separate in the first place.

what the platform owns end to end

The four things a coaching practice runs on are native here, over one shared data model. When an athlete logs a set, the coach sees the program itself change, not a synced report about it.

training

Programs composed as day, workout, exercise, and set, with loads as a percentage of one-rep-max that resolve to real weights per client.

see how it works

nutrition

Versioned diets built from a 1,300+ food library, with compliance reported by the client against the plan the coach actually wrote.

see how it works

body

Check-ins as a time series: weight, body fat, lean and fat mass, and versioned goals, all on one honest scale.

see how it works

performance

Per-set logging on the gym floor, with estimated one-rep-max calculated by each exercise's own formula and always marked as an estimate.

see how it works

every integration is a seam

Two systems that exchange data always disagree eventually: about units, about timing, about which copy is the truth. The typical coaching stack lives with that, because the alternative was building everything. We built everything. That choice is why the roster, the program, the diet, and the body data can never drift out of sync with each other, and it is why the integrations list is short instead of long.

It is not a closed door. It is a bar: an integration earns its place when it brings in data we cannot capture ourselves, and when it can keep the same honesty the rest of the system holds.

the honesty contract any integration must keep

These rules hold everywhere in Trainbase today. Data arriving from outside would have to keep them too, which is a real constraint and the reason we would rather ship few integrations than break it.

4/4/9calories derived from macrosnever stored as a separate number that can disagree
estestimates are markeda calculated one-rep-max never poses as a tested one
1shared scale per charta plateau reads flat; the interface never flatters the data
0silent transformationsevery number can say where it came from

ask for the integration you need.

Tell us the device or app and what you would want it to do in your coaching. Real requests from working coaches decide what gets built.

request an integrationsee the platform

the honest answers

Which apps and devices does Trainbase integrate with today?

None yet, and we will not publish a logo wall to suggest otherwise. Training, diet, body, and performance already live in one system, so the usual reason to integrate, stitching four apps together, does not apply. Integrations we do ship will be chosen from what coaches actually ask for.

Can I get my data out?

Your data is yours, and portability is part of the plan rather than a shipped export button today. If you need your data before then, write to us and we will get it to you.

Why would an integration ever be rejected?

If it cannot keep the honesty contract. Every number in Trainbase is either measured or clearly marked as an estimate, and calories are always derived from macros. An integration that imports numbers we cannot account for would quietly break that promise, and the promise matters more than the logo.

How do I request one?

Email hello@trainbase.io with the device or app and what you want it to do in your coaching. Real requests from working coaches are exactly how the integration list gets decided.