Runs on Android TV and pay-TV set-top boxes
All industries
Telco & pay-TV
The fitness layer your set-top box was waiting for.
The only SDK with native set-top box and Smart TV support. Runs on the hardware AI already in the box.
Uses hardware AI acceleration where present
Paired-camera flow via smartphone where not
Branded experiences ship in weeks
The challenge
The set-top box is the most under-used screen in the home.
It is the biggest. It is the most expensive. It is the only one already paid for by the operator. And yet the entire fitness category routed itself to the phone, leaving the TV as a passive backdrop. The reason is technical: nobody shipped a body-tracking runtime that runs natively on STB hardware.
The TV is shut out of the category
Pay-TV operators watched connected-fitness become a category on phones. The biggest screen in the house had nothing to compete with because no SDK targeted the platform.
Browser fallbacks do not cut it
A WebGL pose model in a Smart TV browser misses frames, drops accuracy and tanks the experience. Subscribers churn after one bad session.
Subscribers want it, operators cannot ship it
Fitness is the most-requested missing category in operator subscriber research. The reason it stays missing is the technical floor under it.
How PoseFlow fits
A native runtime for the screen your subscribers already own.
PoseFlow targets Android TV, pay-TV set-top boxes and Smart TV platforms with a native runtime that uses the hardware AI already in the box. The fitness category finally has a TV story.
Native on Android TV + STB
PoseFlow ships as a native runtime on Android TV. We have shipped on operator-grade STBs running custom Android forks. It is not a browser fallback.
Uses the silicon already in the box
Where the platform has hardware AI acceleration (Amlogic AI camera, dedicated NPU), PoseFlow targets it natively. Where it does not, the CPU path is fast enough on operator-spec STBs to ship a credible experience.
Paired-camera flow when the TV has no camera
Most living-room TVs do not have a camera. PoseFlow supports a paired-camera flow: the subscriber points their phone at themselves, the TV renders the class and the score. One operator app spans both screens.
White-label, brand-coherent
PoseFlow ships as a runtime and an authoring studio. The operator brands the experience end-to-end. Content partners author their own movements. The subscriber sees the operator brand, not ours.
Use cases
Where PoseFlow lights up the operator subscription.
Three deployment patterns we see across Tier-1 European pay-TV operators and smart-TV platforms.
01
Branded fitness channel on the operator EPG
A dedicated branded fitness destination on the set-top box. PoseFlow scores the subscriber's reps live. Classes ship from partner content studios. The operator sells the destination as a premium subscription bundle.
+12pp Add-on bundle attach rate vs single-tier baseline
02
Connected-fitness OEM partnership
A connected-fitness brand uses the operator's STB as a distribution channel for its at-home programme. PoseFlow is the technical bridge: the OEM brand on the screen, the operator hardware underneath.
−68% Cost-per-acquisition vs paid-acquisition baseline
03
Subscriber-engagement loop for the existing tier
Existing subscribers get free access to a movement programme inside their current tier. PoseFlow turns the STB into an engagement surface. Churn moves on the cohorts that engage.
−18% Quarterly churn lift on engaged subscriber cohort
Integration
How PoseFlow lands on operator STBs.
PoseFlow ships as a Flutter SDK with a native plugin layer for each platform. The integration shape on an operator STB is concrete.
Read the technical docs- 01 PoseFlow runtime ships in the operator app as a native plugin (Android TV / Amlogic STB).
- 02 Hardware AI capabilities (where present) are auto-detected; the runtime targets them without app-side configuration.
- 03 Content partners author movements in PoseFlow Studio and publish `.pose` files to the operator content pipeline.
- 04 The paired-camera flow ships as part of the operator companion app on iOS and Android.
- 05 Branding, EPG placement, billing and entitlement run through the operator's existing stack.
Common questions
Telco & pay-TV FAQ
Does it work on our specific STB?
PoseFlow targets Android-TV-based STB platforms by default. For non-Android STBs we have a porting path that takes a few weeks. Get in touch with your platform spec and we will give you a yes/no within 48 hours.
What about TVs without a camera?
The paired-camera flow handles this. The subscriber's phone is the camera, the TV renders the class and the rep counter. One operator account spans both surfaces. We have shipped this pattern in production.
How is content authored?
PoseFlow Studio is a no-code authoring tool that runs in the browser. Content partners stand in front of a camera, define the movement, save a `.pose` file. That file plays back unchanged on every platform PoseFlow supports.
How is the experience branded?
The operator owns the brand front-to-back. PoseFlow ships as a runtime SDK plus an authoring studio. No PoseFlow brand surfaces to the subscriber. The experience reads as a first-party operator product.
Talk to us
Ready to explore PoseFlow for telco & pay-tv?
We will prep a technical walkthrough tailored to your stack and your deployment timeline.
Ready to integrate
See how PoseFlow integrates into your product.
Each engagement starts with a technical walkthrough, tailored to your use case.