Find the page written for what you are building.
The same self-hosted deployment in every case: your cloud account, your region, your credentials, MIT licensed. What changes is why owning it matters. Find the page written for your situation.
Built on Open Wearables
Who it is for · 1
Digital health products
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.
Digital health products
Commercial health products where the data model and what you build on it are part of what you sell.
Learn moreHealth data platforms
EHR, telemedicine and aggregator platforms that are already somebody's processor.
Learn moreCorporate and employer wellness
One set of metrics across a member population, with the processor obligations that follow.
Learn moreSports and nutrition brands
Training load, fuelling and recovery behind a coaching product.
Learn more
Who it is for · 2
Care programmes
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.
Care providers
Run a monitored programme without building the software.
Learn moreRemote patient monitoring
Readings from the patient's own device, in the record their clinician reads.
Learn more
Who it is for · 3
Hospitals and telemedicine
Wearable data in the record your clinicians already open: readings written into your EHR, with a source on every value.
Hospitals and telemedicine
Wearable data in the EHR your clinicians already open.
Learn moreClinical and research builders
Teams heading for review, who need auditable inputs and documented validation.
Learn more
The common part
The deployment does not change between them.
One architecture, whichever page you came from. Whatever your situation, this is what the layer underneath is.
One schema across the devices your users own.
Query a user, not a provider. Activity, sleep, heart rate and body measurements in one shape, in your own database.
Your cloud account, your region.
You choose where it runs when it is deployed, so residency stops being a clause and becomes a fact you can point at.
Raw payloads kept underneath.
Original provider responses are retained under the standard schema, so anything you need later can be re-derived.
Open source, MIT licensed.
Full source, a public roadmap and public issues. The deployment stays yours, whoever runs it.
Connect the devices your users already own.
Every provider arrives in the same schema, so a user who switches watch or adds a ring changes nothing in 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 tell us what you are building and we will say honestly what it takes.
FAQ
Do you have more questions?
Which page should I read?
Pick by the constraint rather than by the industry label. If somebody outside your company reviews where the data goes, start with health data platforms. If a rule keeps data inside a jurisdiction, start with remote patient monitoring. If a number has to survive review, start with clinical and research builders. If nobody is forcing it and you want the data and what you build on it to be yours, start with digital health products.
Is the product different for each segment?
No. It is one deployment, one schema and one repository in every case. The pages differ in which part of it answers the question you are being asked, and in the worked examples. Nothing is gated or priced by segment.
What if we are in two of these at once?
Common, and it changes nothing technically. Read the page that matches whoever is asking the hardest question, because that is the one written in their language. A company selling a consumer app to employers is both a digital health product and an employer wellness vendor, and it deploys exactly the same thing.
None of these describe us. Is it still for us?
Possibly. The product fits wherever wearable data cannot sit in somebody else's cloud. These pages are the situations where that comes up most, not a list of permitted uses. Retail, FMCG and consumer sports brands without a data product are usually a poor fit, and a hosted API serves them better.
Where is the data stored in all of these?
In your own cloud account, in the region you choose at deployment, under your credentials. That does not vary by segment. No copy sits in a Momentum tenant in either operating model.
Can we run it ourselves?
Yes. Clone the repository and run it under an MIT licence, with the full source. The alternative is buying a deployment, where we stand the same thing up inside your account. Pricing has what that covers.
Is it open source?
Yes, MIT licensed, with the full source, a public roadmap and public issues. Health scores come with Pro. The deployment stays in your account, whoever runs it.
Who maintains it?
Momentum, a healthcare software development company. The project is developed in the open, so the source does not depend on us continuing to fund it.