Open Wearables - Open infrastructure for wearable-powered health products.
by•
Build personalized health products with one API for every wearable. Access wearable data, open health scoring algorithms, and structured context your AI can reason with. Self-hosted, open-source, MIT licensed.
Replies
Lancepilot
Open Wearables
@istiakahmad Thanks Istiak, appreciate it. The healthtech space especially needs more open infra: too much critical patient data sitting behind closed APIs and per-user fees.
@istiakahmad Yeah, open source with the great care for software quality is what we really need in the age of AI.
The gallery screenshot showing the API response for sleep stages actually made me stop scrolling. I've been pulling this data manually from Apple Health exports for two years. Why does this not exist as a consumer product yet?
Open Wearables
@paulina_kowalczyk Two years of manual Apple Health exports is exactly the pain that shouldn't exist in 2026. Open Wearables is the infrastructure layer for that consumer product, if anyone (you?) feels like building it, we'd happily help.
@paulina_kowalczyk It's because most of the providers don't want the products like this to be available for consumer. Sadly, but this is the truth. Just look at the Garmin for example - there is no way to get API access if you are not a company.
Another trivia - original name of the project was Healthion ;) I'm curious. Which one do you guys like more?
Open Wearables
@kaliszs Open Wearables all day long.
so cool! MCP is a huge unlock for the millions of people also using chatgpt/claude
Open Wearables
@kohnigel Thanks Nigel! That's the bet, the moment "ask Claude about my sleep last week" becomes one click instead of a CSV export, the whole consumer health workflow shifts. MCP is the entry point, but the real unlock is agentic: long-running assistants that watch your trends, flag anomalies, and reason across weeks of data without you prompting. Still early days, but the direction feels right.
@piotr_ratkowski makes sense - great example: personalized recipes drafted based on blood glucose levels
@kohnigel Indeed, but rememember - at the moment our MCP is still not 100% production ready.
From a user POV - that's the thing I've been looking for! How did you put on top the domain knowledge? It is so interesting!
Open Wearables
@matt_kopiec We kept rebuilding the same wearable integrations from scratch for every client. After enough of that, you develop strong opinions about what the scoring should actually look like. We codified those into the algorithms and opened them up.
@matt_kopiec We have started with MCP servers, then we moved to the project called "healthion", which was baically jus ta simple FastAPI with frontend with an access to the MCP.
Open Wearables
@matt_kopiec Glad it resonates! It's a mix of things, but definitely deep work with wearables and health data over the years helped a lot. We also have a PhD in Neuroscience on the team 🙌
OpenAI
This removes a huge dependency on multiple SDK integrations, yes??
Open Wearables
@divya_kothari1 Yes, basically you have the integration part covered by Open Wearables. Data fetched from different providers is aggregated and normalized, and you only need to consume APIs provided by Open Wearables instead of integrating with many providers. For some integrations like Apple Health you can only get the data from mobile device as they don't expose any APIs, but we also have SDKs for that to make these integrations easier 😎
@divya_kothari1 You still need a separate SDKs for Apple and Android, that's it.
Does this require running your own server infrastructure to be useful, or is there a path for someone who just wants to connect their Garmin and start pulling data without a DevOps background?
Open Wearables
@gosia_boryn The easiest option would be to use one-click Railway deployment to set up your own instance in the cloud. Then you can start pulling your data from there via API 🙂
@piotr_sobusiak Let's do it togather and record it :) to show if it as easy as said.
Open Wearables
@gosia_boryn In the documentation link I've sent there is actually a walk through on YT of the whole process of one-click deployment to Railway. There is an official template for that you can find on Railway marketplace. If you run into any problems during the setup, please reach out to us and will do our best to help 🙂
@gosia_boryn But it's important to be aware of - you can't use Garmin API as a private person. It's restriction of most API based providers. But if you want to use cloud based, like Apple, Google and Samsung - you are free to go! :)
Free, self-hosted, MIT license. Those three together in a health data tool is rare enough that I had to double-check the page. What's the long-term monetization plan, just curious?
Open Wearables
@dawid_stajszczyk Ha, fair reaction. The model is intentionally boring: Open Wearables stays free and MIT, Momentum sells services on top (enterprise deployment, custom scoring algorithms, AI/coaching layers, HIPAA support, SLA-backed maintenance).
@dawid_stajszczyk This campaing is one of the monetization plans ;)
@dawid_stajszczyk The "AI/coaching layers" part caught my eye as a running coach. The infrastructure being free and open is what makes it trustworthy and trustworthy infrastructure is exactly what premium coaching tools need to be built on.
Interesting concept. Curious how it handles the cases where the same underlying metric (say, HRV) gets measured differently by different devices. Does it normalize across them or leave that to the developer?
Open Wearables
@michal_grela We normalize what's normalizable: units (ms), timestamps, structure. Same API call regardless of source. What we can't paper over is measurement methodology. Garmin and Oura measure HRV overnight, Apple during breathing exercises, Whoop computes its own daily baseline. Same name, different signal. We surface the source and context in the response so you decide whether to treat them as comparable or filter to one provider. Faking consistency would hide a real semantic difference.
@michal_grela
That's how ;)
Open Wearables
@michal_grela as Sebastian mentioned - you can set different priorities for all providers we already support and in the future we are planning to make it even more granular and set priorities for particular devices.
Open Wearables
@sarrah Already shipped! Oura landed in v0.4 (community contributed, full granularity including sleep stages via Oura's cloud API). Docs at openwearables.io/docs if you want to plug it in.
@sarrah We already do :D