Comparison · Camera SDKs

CoachLayer vs camera motion SDKs: these are different jobs.

The honest answer

If your product moment happens during the rep, buy a camera SDK. CoachLayer does not do that job. Live rep counting, form cues while the athlete moves, a skeleton overlay: that is on-device computer vision, it is a crowded and competent market, and a language model is the wrong tool for it.

CoachLayer works on the other side of the workout: what the session meant, whether the athlete should push or back off tomorrow, how the week went, what the program should become. Most apps that think they are choosing between the two are actually choosing both, or neither.

Side by side

During the rep vs around the session.

DimensionCamera SDK (Sency, Kemtai class)CoachLayer
The moment it servesDuring the movement: counting, form scoring, live cuesBefore and after: readiness, session analysis, weekly reports, program adaptation
InputCamera stream, on deviceTraining and recovery data your app already has (sessions, sets, sleep, HRV)
OutputCounts, angles, scores, real-time eventsStructured coaching text and decisions: briefs, analyses, next steps, adapted sessions
Core techOn-device pose estimationLLM endpoints behind engineered contracts and validators, benchmarked in production
Privacy surfaceCamera and body imagery, which several jurisdictions treat as biometric data and regulate accordinglyPer-call stateless proxy over training data; nothing stored
Typical pricing$99.99/mo covers up to 100 active users, then pay as you go per unique active user per month, from $0.99 a user and sliding to roughly $0.10 at 10,000+ users.Credit-metered tiers, public, on the pricing table
Full disclosure

Where the surfaces overlap, and where we are behind.

CoachLayer ships a Form Check endpoint: send a recorded clip, get a technique breakdown in text. Three honest things about it.

It is not real-time

It analyzes a recorded clip after the set. If you need cues while the athlete moves, that is the camera SDKs’ job, and they are better at it than any clip-analysis approach will be.

It is our least proven endpoint

Our benchmark covers five of eight endpoints with production data. Form Check is not one of them yet, and we publish that instead of hiding it. Do not pick CoachLayer because of Form Check; pick it for the coaching brain and treat Form Check as a bundled extra.

The categories can stack

The strongest setups we see planned use both: an SDK counts and cues during the session, and the session facts then flow into analysis, briefs and program adaptation. Vendors in both lanes ship webhooks and JSON; the integration is natural.

On Kemtai: you are in the clinical or MSK-rehab lane where validation, compliance and payer conversations matter more than integration speed. That is a different buyer and regulator than consumer fitness, and we deliberately do not compete there.

Straight answers

Camera SDK or coaching API: the questions buyers ask.

Do I need a camera SDK or a coaching API?

It depends on when your product moment happens. If it is during the rep (live counting, form cues while the athlete moves, a skeleton overlay), you need a camera SDK running pose estimation on the device. If it is before or after the session (whether to push or back off today, what the session meant, how the program should change), you need a coaching API working on the training and recovery data you already hold. Many apps need both, and they stack: the session facts the SDK produces become the coaching API’s input.

Can CoachLayer count reps or correct form in real time?

No. CoachLayer has no on-device component and never sees a live camera stream. Its Form Check endpoint analyzes a recorded clip after the set and returns a technique breakdown in text: 25 credits per clip with the first 30 seconds included, then 25 credits per extra 30 seconds, on every tier except Build. If live cues are the feature, buy a camera SDK.

How do camera SDK results get into CoachLayer?

Through your backend, as JSON. The SDK produces session facts on the device (reps, sets, form scores), your app uploads them to your server like any other workout, and your server passes them in the request body of the endpoint that needs them, workout analysis or the readiness brief for example. CoachLayer never talks to the SDK or the device, and the API key stays a server credential.

Is pose or camera data biometric data?

Not automatically, which is why it needs a deliberate answer. GDPR Article 4(14) counts data as biometric when specific technical processing of physical, physiological or behavioural characteristics allows or confirms the unique identification of a person, and the Illinois Biometric Information Privacy Act lists a scan of hand or face geometry as a biometric identifier. Whether a camera feature falls in scope depends on what it extracts and keeps, so settle it with your counsel and your vendor’s DPA before launch. CoachLayer’s coaching endpoints never receive imagery; Form Check, an uploaded clip, is the one exception.

How do camera SDKs price compared with a coaching API?

On different units. Sency: $99.99/mo covers up to 100 active users, then pay as you go per unique active user per month, from $0.99 a user and sliding to roughly $0.10 at 10,000+ users. Kemtai: Sales-led; no public price list. CoachLayer meters each call in credits instead, so the SDK bill grows with monthly active users and the CoachLayer bill with the coaching calls you make. If you run both, budget them separately.

Can we build rep counting ourselves instead of buying a camera SDK?

You can build the first layer, because pose detection now ships with the platforms. Apple’s Vision framework detects 19 body joints in an image on iOS 14 and later, and Google’s ML Kit Pose Detection tracks 33 skeletal landmarks in real time on a modern phone, though Google still offers it in beta with no SLA. Both return points with a confidence score, not reps: Google states that Pose Detection does not attach any meaning to the landmarks in a pose or the pose itself. Recognizing the exercise, counting the rep, judging depth and timing a cue are yours to write, then to test across bodies, clothing, light and camera angles for every exercise you support. That interpretation layer is what camera SDKs such as Sency sell. Either way, the counted session lands in your backend and becomes CoachLayer’s input.

Do camera SDKs work in React Native, Flutter or a web app?

Check the vendor’s platform table before you settle the stack, because coverage is uneven. Sency’s SDK repository lists kits for iOS, Android, React Native and Flutter, and marks JavaScript and Unity as not available, so a workout that runs in the browser needs another route. The platform detectors split the same way: Apple’s Vision body pose request runs on Apple devices only, Google’s ML Kit Pose Detection has guides for Android and iOS, and Google’s MediaPipe Pose Landmarker ships a JavaScript package for the web that estimates 33 body landmarks. All three return points, not reps. CoachLayer is the same from any client: it is an HTTPS API your server calls, so session facts from a native, cross-platform or web app reach it the same way.

Do camera SDKs send workout video to the cloud?

The ones that document it analyze frames on the phone. Sency’s FAQ says its data is processed using edge computing, analyzed directly on the user’s device and never sent to the cloud. Google says ML Kit’s processing happens on-device and also works while offline, and MediaPipe runs live camera streams with on-device execution. On-device describes where frames are analyzed, not everything an SDK sends, so ask the vendor what does leave the phone (session results, usage analytics, crash reports) and write the answer into your DPA and privacy policy. If a vendor’s documentation is silent, ask before launch. CoachLayer never receives a camera stream. Form Check is the one endpoint that touches video: you pass the URL of a clip your app has already stored, and like every request it is processed transiently, not written to a durable store on our side and not used to train models.

Pose detection: Apple’s VNDetectHumanBodyPoseRequest and Google’s ML Kit Pose Detection and MediaPipe Pose Landmarker for web documentation, and the platform table in Sency’s SDK repository, checked November 2026. On-device processing: Sency’s motion tracking FAQ, Google’s ML Kit overview and MediaPipe Tasks guide, checked 18 November 2026. How Form Check takes a clip is in the API docs, and what we keep from a request is in our privacy policy.

Already have the reps counted?

Then the interesting half is what they meant. That is the layer CoachLayer sells.

Get a sandbox key