An open platform for wearable data, built by a healthcare company.
Open Wearables runs in your own cloud account and is maintained by Momentum, a company whose whole business is health software.
Where this came from
We wrote it for our own client work.
Every health product we built that touched a wearable needed the same integration layer underneath. A hosted aggregator stopped being an option when a client could not send patient data to a third party.
So we built the layer to run inside the client's own account. It is the same code we deploy for clients today.
How the project is run
Maintained on a release cadence, in public.
The question worth asking about any open source infrastructure is whether anyone is still working on it. Here is what that looks like for this one.
- GitHub stars
- 2,606
- Forks
- 450+
- Contributors
- 60+
- Releases
- 20+
A release every few weeks, not every few quarters.
Provider coverage, data integrity and platform work ship on a steady rhythm rather than in occasional bursts. Every release has public notes, so you can see what changed before you upgrade.
Release notesBuilt in the open, including the awkward parts.
Issues are public, breaking changes are announced in the release that carries them, and the roadmap is a document anyone can read. Nothing is discussed in a private tracker and announced later.
View the roadmapContributions from outside the company.
Engineers who do not work at Momentum have shipped code into this repository. That is the difference between a repository the public can read and a project the public can join.
Read the quickstart
Working with Momentum
Three ways teams bring us in.
The code is public, so none of this is about access. It is about who does the work and who is accountable when a provider changes something.
[01] Deployment
Deployment
Your engineers get a working API instead of a sprint spent on infrastructure. The credentials part is the slow one, because some providers take weeks to approve an application, so we start it on day one.
- Production and staging in your cloud, in your region
- Provider credentials issued in your name, validated on real accounts
[02] Integration
Integration
Your users link their devices without leaving your product and without a second account to manage. Everything in Deployment is part of it, so this is the option when the deadline is a release date rather than a working endpoint.
- Mobile SDK live in your app, syncing in the background
- Connection and consent flow inside your own interface
[03] Custom development
Custom development
Our engineers and health science team work on your side of the API. This is where a score gets adapted to the people who actually use your product, rather than shipped as a general-purpose number.
- Health scores built and tuned for your population
- Provider integrations and product features on top of the platform
Ongoing maintenance
Available alongside all three, with somebody accountable for provider drift and tested upgrades. Scope and starting figures are on the pricing page, based on your infrastructure and sources rather than a seat count.
Who builds it
Engineers and scientists, not a community team.
The people who commit to the repository are the people who deploy it for clients and answer questions on Discord. There is no separate open source team, no community manager and no partner network in between.
Bartosz Michalak
Director of Engineering
Leads the platform architecture. From unified data model to production deployment.
Sebastian Kalisz
Software Engineer
Backend engineer building the FastAPI services and multi-provider OAuth integrations.
Filip Begiełło
ML Lead
Architecting the health scoring layer: the sleep, recovery and activity scores.
Anna Zych
Neuroscience PhD
Building health scores and science-backed algorithms behind the platform.
- JC
Jakub Czajka
Software Engineer
Infrastructure and security. HIPAA-ready architecture, encryption, audit logging.
Grzegorz Sztuczyński
Frontend Engineer
Building the developer portal. Dashboards, user management, API key generation.
Kacper Gąsior
Frontend Engineer
Developer portal interface. OAuth connection flows and sync status across devices.
Kamil Piekarz
Mobile Engineer
Flutter SDK for Apple Health. Background sync, incremental data fetching, iOS Keychain auth.
The company behind it
A healthcare software company, not a startup with one product.
Momentum has been building health data software since 2016. Health is the whole business rather than one vertical among several: clinical applications, AI in healthcare, EHR and FHIR integration, and infrastructure that has to pass an audit.
Wearable data is something we do repeatedly, not once.
Every provider names its data differently, rate limits differently and breaks differently. Knowing which ones backfill, which ones need a pull rather than a webhook, and what a value actually means before you compare it across devices is the work. Open Wearables is where that knowledge lives.
Certified for medical device software.
Momentum holds ISO 13485, the quality management standard for medical device development, and delivers under HIPAA and GDPR. When a review asks who wrote the code and under what process, that is the answer.
Enough history to check.
Over 220 projects. Financial Times FT 1000, Forbes Diamonds, and Deloitte Technology Fast 50 in Central Europe three years running. Clutch rating 4.9 out of 5. Based in Wrocław, Poland.
Start wherever makes sense.
The quickstart gets you a running instance today. If you would rather talk first, a person reads every message and routes it to sales or to an engineer depending on what you ask.
FAQ
About the project.
Who owns Open Wearables?
The code is MIT licensed, so in every practical sense you do once you deploy it. The project is maintained by Momentum, a healthcare software company that built it for client work and continues to use it that way.
Why would a services company give away the platform?
Because the integration layer was never the part clients paid us to invent, and maintaining it privately for each of them cost more than maintaining it once in public. The work we sell sits around the platform rather than inside it.
What happens to my deployment if Momentum stops working on this?
It keeps running. The platform sits in your cloud account, built from infrastructure code in your repository, under a licence nobody can revoke. That is the case whether we are involved for a month or for five years.
Do I have to pay you to use it?
No. Clone it, deploy it, ship it, and never contact us. The documentation is written for that path rather than as a teaser. See pricing
Who is actually using it?
Teams building health products on their own infrastructure, from remote monitoring to fitness and wellbeing. Several have agreed to be named, and the customers page has the detail.
Is Momentum certified?
Momentum holds ISO 13485 for medical device software development, and delivers under HIPAA and GDPR. Those certifications cover how the software is built. Where it runs is your own certified environment, which is the part the security page covers. For regulated buyers
Where are you based?
Wrocław, Poland. The team works with clients across Europe and North America, and support hours beyond European business hours are part of what an ongoing engagement can cover.