Build your health product on a wearable data layer you own.
Open Wearables is self-hosted wearable data infrastructure for commercial health products. It connects the devices your users already own and keeps the data, the schema and the scoring inside a cloud account you control.
Built on Open Wearables
What you get
What Open Wearables gives your product team.
Providers authorise differently and each returns its own shape. Open Wearables handles that inside infrastructure you own, so a quarter of integration work becomes a deployment.
One standard schema
Query a user, not a provider. Activity, sleep, heart rate and body data in one shape, joinable with the rest of your product.
- Raw payloads kept
- Time series
- Webhooks
Your database, your credentials
The data lands in infrastructure you fully control, with retention you set. No copy sits in a vendor tenant.
- Your account
- Your region
Custom health scores
Scores designed and validated by our science team, computed inside your deployment. Custom scores for your population are built with the same team.
- Health scores
- Science team
Data off the device
Native SDKs for iOS, Android, Flutter and React Native sync on-device data in the background, inside your own app.
- HealthKit
- Health Connect
Costs you can see
Running it costs your own cloud bill, paid to your provider. Deployment and Integration are one-off services, and health scores and the other licensed modules come with Pro.
- Your cloud bill
- One-off services
A public roadmap and an open community
Issues, releases and what ships next are public. Community support on Discord, and the source does not depend on us continuing to fund it.
- MIT license
- Full source
- GitHub
How it works
From decision to launch
- 01
Deploy it
Production and staging in your own cloud account, in the region you choose, defined as infrastructure code in your repository. Either your team stands it up, or you buy a deployment and we do it.
- 02
Get your own provider credentials
Each source issues developer credentials in your name, and you apply for them directly. Approval timelines vary, so this is the step to start first. Garmin is the slowest: Garmin API integration.
- 03
Wire it into your product
The mobile SDK goes into your app, syncing in the background behind your existing login. The connection and consent flow sits in your own interface, not a vendor's widget.
- 04
Ship, then extend
Standardised data lands in your database, so the next feature is a query rather than a procurement conversation.
See what a deployment covers
The honest comparison
Hosted SaaS API, in-house build, or self-hosted
Where each one actually wins. If a hosted API fits your situation, use one.
| Hosted SaaS API | Build in-house | Open Wearables, self-hosted | |
|---|---|---|---|
| [01] First API call | Hours | Months | Minutes, with Docker Compose |
| [02] Where the data sits | Their cloud, their regions | Yours | Your cloud account, your region |
| [03] 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 |
| [04] The data model | Theirs, you build against their schema | Yours | Yours, in your database |
| [05] Scoring logic | Proprietary, not published | Build and validate it yourself | Designed and validated by our science team, licensed as a module |
| [06] Provider credentials | Theirs, handled for you | Yours to obtain | Yours, in your own name |
| [07] Certifications | Theirs | Yours to earn | Yours, in your certified environment |
| [08] Cost shape | Scales with monthly active users | Salaries and infrastructure | Fixed, flattens as you grow |
What stays yours
The deployment, the data and the algorithms stay in your account, whoever runs it
Sovereignty
Health data does not sit in a third party's cloud.
Residency
Your users' data stays in the region you chose, provable by pointing at an account.
Control
You run it under your own credentials and decide who gets access. What you build on top of Open Wearables is yours.
Your own reasons
Before a regulator or customer asks, the schema and the data are in your account.
Who is it for
The product types this fits
The argument for owning the layer lands differently depending on who is asking. These are the situations where it lands hardest.
Consumer health and fitness apps
Direct to consumer, where the scoring is part of the product and GDPR sets the floor for every health score you compute.
Longevity and biomarker platforms
Where due diligence asks what a number measures, how it was validated and where the data behind it sits.
B2B digital health platforms with enterprise clients
Where your customer's procurement runs a vendor assessment and asks for compliance documentation you have to produce yourself.
Employer wellness vendors
Where you are a processor for the employer and need standard metrics somebody can audit across a member population.
What teams build on it
Coaching, scoring and analytics on the devices your users already wear, built inside your own deployment.
A scoring model
A health score computed inside your deployment from your users' own data, designed and validated by our science team.
Health analytics
Months of sleep and resting heart rate in one timeline, held in your database rather than a vendor's retention window.
A coaching engine
Today's session comes from that user's own history, generated by your model. What makes the coaching good stays yours.
Whatever your users wear, one schema
Cloud providers and on-device sources arrive in the same shape, so supporting another device later does not change your code.
Deploy Open Wearables in your own cloud
The repository is public and the deployment is yours from the first commit. Start from the source, or bring us in to stand it up in your account with the providers connected and validated on real accounts.
FAQ
Do you have more questions?
We have a launch date. How fast can this be live?
First API call in five minutes with Docker Compose. The long pole is provider credentials, which are issued in your name and take from a day to several weeks depending on the source. A deployment starts that work on day one and runs the rest in parallel.
Is it really free?
The core is. It is MIT licensed, with the full source and no trial window. We charge for Pro, Enterprise, the Deployment and Integration services and custom development.
What does it cost compared with a hosted API?
A hosted API prices per monthly active user, so the bill grows with your success. This is a one-off deployment cost plus your own cloud bill, paid directly to your provider and never marked up by us. Pricing has the figures.
Can we use this for a HIPAA workload?
The deployment runs on your infrastructure, so access, encryption, retention and audit logging are yours to control and to evidence. A BAA depends on your cloud provider and your scope.
Who can reach our users' data?
Your team. It runs in your cloud account, under your credentials. When we work on your system, we do it under a DPA you sign. What we sign sets out when the DPA applies.
Do you hold SOC 2 or ISO 27001?
No. The deployment runs inside your certified environment, which is how most teams answer this in their own audit.
Our enterprise customer wants a DPA. Will you sign one?
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.
We already use a hosted aggregator. How hard is moving?
Usually a re-integration rather than a data migration. Your historical data stays where it is, and what changes is where new data lands from the switch onwards, which is your own database. Most teams run both in parallel while they validate, then cut over.
Is it running in production anywhere?
Yes. Heart Monitor runs Open Wearables in production at around 90,000 monthly active users. They adopted the open-source project and shipped it with their own team.
What about the scores? Can we build our own?
Yes. Health scores are part of Pro, designed and validated by our science team and computed inside your deployment. Custom scores for your population are built with the same team, and your own logic can run on the same data.
Who maintains Open Wearables?
Momentum, a healthcare software development company. The project is MIT licensed and developed in the open, with a public roadmap and public issues, so the source does not depend on us continuing to fund it.