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.
Forum Threads
How much can a wearable actually tell you about your sleep? webinar
Hi makers,
Most wearables are good at telling when you're asleep. They're much worse at telling when you're awake: if you lie still, many devices count it as sleep. Sleep stages land somewhere in between. And Apple, Oura, Garmin, Whoop and Fitbit all build their scores differently, so the same night can get very different numbers.
Anna D. Zych, PhD, a neuroscientist and Health Science Lead at Momentum, goes through all of this in a webinar that premieres Wednesday, 7 October at 16:00 CET. It covers what good sleep actually looks like, how wearables compare to a sleep lab across ten devices, and how to approach building sleep scoring models.
If you're building anything with sleep or recovery data, it should be a useful hour. Everyone who signs up gets the recording too.
The Wearables Integration Playbook 2.0 is out
Quick update for anyone who followed the Open Wearables launch.
We just published the second edition of our Wearables Integration Playbook. It's the written version of what we learned building the platform and seeing it run in production.
Why does your recovery score say 58% today?
I wear a WHOOP. I've coached people on movement and sleep for many years and I still can't answer that question for myself. The algorithm is locked. You get a number, you trust it, you stop there.
When we built Open Wearables, we decided the scoring layer should work differently. Sleep Score and Resilience Score shipped in v0.5 - every coefficient, every threshold, every weighting is in the repo and you can fork them, tune for endurance athletes or elder care or clinical populations. Moreover, you run them on your own infrastructure and the same algorithms feed the MCP layer so AI coaching can cite the actual data behind a recommendation instead of approximating.
Another trivia - original name of the project was Healthion ;) I'm curious. Which one do you guys like more?
@kaliszs Open Wearables all day long.
This is the kind of infra that quietly unlocks entire categories.
Everyone talks about AI in health.
Almost nobody fixes the data layer first.
Unifying wearable data + adding a reasoning layer (not just dashboards) is the real game.
Feels like “Stripe for health signals”... but open!
@tomik99 nobody fixes the data layer first because it's unglamorous. but you can't reason over garbage -sequence matters
the reasoning layer is honestly what we're most excited about. raw numbers mean nothing without context, that's the whole point of building this
and "but open" is what changes the Stripe analogy - you can audit, fork, run it yourself. that's a different relationship with infrastructure entirely
"Stripe for health signals but open" - we love that, might steal it
@tomik99 Thanks Tomasz, the "AI in health without fixing the data layer first" frustration is exactly what pushed us to ship this. Most health AI demos break the second you put real, multi-device, multi-format data behind them.
@tomik99 Tomasz - "quietly unlocks entire categories" is exactly the read. From the ops side I kept seeing portfolio teams burn 3-6 months on the same Oura/Garmin/Whoop plumbing before they could even start the actual product. That's the tax we got tired of paying. Open part isn't a marketing flourish - it's the only way infra like this actually compounds across companies.
@tomik99 Exactly. The most interesting part is - after 6 months of work we are just starting with implementing AI. So much of old school software work has been done before.
I share screenshots of my Whoop app with claude currently and ask it to analyse it based on the screenshot. Let me try using the MCP and ask it, feels like that could be a much smoother experience
@ajaykumar1018 You can run the repo locally and setup the MCP server. Let us know your thoughts!
@ajaykumar1018 Feel free to use our MCP, but remember - it's still not 100% production ready.
open infrastructure in health is a brave bet. the value is obvious but the regulatory complexity is brutal. curious whether you're seeing builders use this for consumer products more
@piotr_ratkowski Congrats on the launch! Such nice work. I have a question, though. How do you handle data privacy and consent when pulling health data from multiple wearable providers, especially for teams that need to stay compliant?
Amazing project team! I think it was the missing puzzle - the standarization of the data bus for health/wearables and you're jsut filling the gap. Fingers crossed!
@piotr_karwatka Thanks Piotr, "data bus for health/wearables" is a sharp framing, the standardization gap is exactly what kept biting us across client projects until we decided to just open-source the fix. Appreciate the support 🙏
@piotr_karwatka FInger crossed, thanks!
Awesome! Great idea, congrats for the launch 💪
@gregrog Thank you so much :)