Open Wearables is open-source infrastructure for wearable data. Connect the devices your users already own, keep the raw payloads, and build scores, insights and coaching on top, all inside your own cloud account.
Built on Open Wearables
What you get
A product on wearable data needs the same groundwork: integrations, one schema, sync from the phone and the raw data underneath. Open Wearables ships it as one open-source project.
One standard schema across the wearables your users own. Authorisation flows, webhooks, delivery history for debugging, an admin panel for keys and connection status.
Learn moreiOS, Android, Flutter and React Native, plus the Connect App for teams without an app of their own, so you can pull Apple Health and Google Health Connect data before you build one.
Learn moreOriginal provider payloads kept underneath the standard schema, in your own database, for debugging and for whatever the schema does not cover yet.
Learn moreHealth scores built with our science team, computed in your deployment. Part of Pro.
Learn moreTrends across weeks, anomalies worth a second look, and the context an assistant needs to say something useful.
Learn moreWhy it runs in your cloud
A hosted API keeps the data, and every score computed from it, in a vendor's account. Running the layer yourself keeps it where HIPAA, GDPR and your own policy say it belongs.
Your regulator, your board or your own policy says health data does not sit in a third party's cloud.
The data has to stay in a country or region you choose, and you have to prove where it is.
You run the deployment under your own credentials and decide who gets access. What you build on top of Open Wearables is yours.
No regulator forcing it and no security review coming. You want the data in your own account anyway.
The honest comparison
Where each one wins. Self-host for control, for data sovereignty, for a regulator or your own reasons, and Open Wearables saves you the in-house build.
| Hosted SaaS API | Build in-house | Open Wearables, self-hosted | |
|---|---|---|---|
| [01] Where the data sits | Their cloud, their regions | Yours | Yours, your account, your region |
| [02] Who can reach the data | The vendor and its sub-processors | Your team | Your team, and us under a DPA you sign when we work on it |
| [03] Provider credentials | Theirs. Your users connect through the vendor's provider account | Yours to obtain from each provider | Yours to obtain. The relationship is between you and the provider |
| [04] Cost shape | Scales with monthly active users | Salaries and infrastructure | You pay for the infrastructure it runs on, and that is flat as you grow |
| [05] Where your team's time goes | Your product, within the vendor's limits | Keeping each integration working | The intelligence layer on top |
| [06] Choose this when | Speed matters more than control, no regulator, no enterprise security review | Wearable integration is your core differentiator and you have the team | A rule, a contract or a customer review says the data stays with you, or owning it matters to you |
What you build on it
Open Wearables gives you clean wearable data you own. What you build on top of it is yours, and Pro adds scores and insights inside your deployment.
Health scores from our science team, computed inside your deployment and validated before release.
The models and rules you build run on data in your own cloud, under your credentials.
Written from each user's own history, so it says what they could not see alone. A paid module.
The same number reads differently for an athlete and for a patient. Your tone, your rules. A paid module.
Who is it for
Each path runs the same open-source core in your own cloud account. What changes is what sits on top of it, and how you start.
Ship wearable features in your own product: scores your users check every morning, coaching from each user's own history, analytics across the devices they already wear.
Learn more
Run a monitored programme without building the software: a patient app or SDK, a care view your team opens every morning, consent on every reading.
Learn more
Wearable data in the record your clinicians already open: readings written into your EHR, with a source on every value.
Learn more
Case studies
Consumer heart health app
One engineer connected six providers for around 90,000 users, and every reading stays in infrastructure Heart Monitor controls.
Read the case study
Family health app
“It let us start building the family experience instead of rebuilding wearable ingestion.”Razi Syed, Founder, Lifelong
Read the case study
Social fitness app
“It let a small team ship a broad device lineup and keep it current.”Sam Pullen, Founder, MoveTogether
Read the case study
Social workout platform
“We read the code, added it to our fork, and shipped. That is the difference open source makes.”James Greene, Founder & Engineer, JustGains
Read the case studyCloud providers and on-device sources arrive in the same shape, so supporting another device later does not change your code.
Run the open-source core yourself for free. Pro puts our licensed modules and our team behind your production deployment; Enterprise adds the security, scale and SLA a company at scale needs.
For teams building their first wearable features. You run the open-source platform yourself.
$0Forever
For products in production. Licensed modules, with our engineers behind your deployment.
From$999a month, per deployment
Everything in Core, plus
The Pro modules, in your deployment
For health organisations at scale, from digital health to hospital groups. We run and secure it in your cloud, under an SLA.
Custom
Everything in Pro, plus
A care provider, hospital or telemedicine platform? See care providers or hospitals and telemedicine.
Clone the repository and connect your first provider in your own account today. Or book a demo and leave with a scoped plan for your deployment.
FAQ
Yes. The core is MIT licensed, with the full source. We charge for Pro, an Enterprise agreement, the Deployment and Integration services and custom development.
Yes. The data goes into your cloud account and nowhere else, so access, encryption and retention stay under the controls you already run. We do not run a hosted version.
The API, the SDKs, raw data retention, webhooks and the admin panel, all in the free core. Health scores, the health agent and medical-grade integrations come with Pro, and the live versus roadmap page lists which is which.
It runs in production at consumer app scale. Load testing results and the methodology behind the scores are published rather than described on a call.
No. The deployment runs inside your certified environment, which is how most teams answer this in their own audit. The security page states what we do have.
Yes, whenever our people can reach your deployment: under Pro support, during a Deployment or Integration service, and for as long as Enterprise runs. Where you self-host on Core, there is no processing for us to agree to, because we never touch it. A BAA comes with Enterprise, where your cloud provider and your scope support it.
You do, in your name. It is real work and approval is slow with some providers, so we start it on day one of a deployment.
Usually a re-integration rather than a data migration, because you own the raw payloads going forward. It is a scoping conversation, and it is the most common shape of deal we do.
Nothing changes technically. You are already running the thing we would deploy. You add Pro when your users need scores and insights, and an Enterprise agreement when you want somebody accountable.
No. Teams self-host for their IP, for data residency, for a regulator, or because they want the data and the model in their own account. When time to market is what counts, Open Wearables gives you the in-house plumbing ready from day one, and Pro adds what your users see on top, so owning the layer does not slow the launch.
