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.
Open Wearables
@imtiaj_ahmad Very scalable: FastAPI + PostgreSQL + Redis + Celery scales horizontally, and multiple companies run it in production today. The real advantage at scale is the cost model: zero per-user fees, so where SaaS aggregators charge $0.50-2.00 per user per month, you only pay for your own infrastructure. The bigger you get, the better the math works.
Open Wearables
@alireza_abbasi5 Hi Alireza, the self-hosted architecture fits your constraint well (no data leaves your infrastructure), but specifics depend on which wearable APIs are reachable from your network, drop into Discord and we can dig in.
self-hosted + MIT for wearable infra is the real gap — most teams glue oura/whoop/garmin together and end up maintaining a janky data lake nobody owns. on the open scoring side, are the algorithms research-grade (validated hrv, recovery, etc.) or more heuristic baselines? and for LLM context: do you ship structured schemas for sleep/strain/activity so an agent can reason directly, or is shaping the context still on the developer?
The hard part of a wearables product isn't the data, it's the interface contract between messy multi-vendor reality and a coherent user experience. The standardization layer and transparent scoring is what makes it possible to actually build any app on top.
Also, surviving Garmin's API earns you a small badge of honor in this space. Worth it.
Congrats to the whole Momentum crew 🚀
Open Wearables
@farce1 That Garmin badge took longer to earn than we'd like to admit. 😅 You put it well: the data was never really the problem, getting it into a shape any app can reliably build on is. Thanks for the kind words to the whole team.
@farce1 haha, agree - worth it!
Open Wearables
@farce1 "surviving Garmin's API" is going on the team wall
and yeah - the standardization layer is the unglamorous part nobody wants to build twice. that's exactly why it should be shared infrastructure
thanks for the kind words
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
YES - free my Oura data!
Open Wearables
@therealkaczor Ha, love the energy Michal, small clarification though: the data is still in Oura's cloud, we just give you programmatic access to it via their OAuth API in a unified format. Not quite "freeing" it, but at least you can pipe it into anything you want without rebuilding the integration.
@piotr_ratkowski Yes, much better than me going trough the faff of requesting data and then analyzing on the side. Good enough for me. Hope to meet you in person soon. Good luck 🙌
GrowMeOrganic
Are you planning integrations with Apple Health and Google Fit out of the box? Congrats on shipping.
Open Wearables
Hi @iamanantgupta We already integrate with Apple Health and Google Health and provide SDKs for SDK-based providers - you can see providers we support and full coverage matrix in the documentation: https://openwearables.io/docs/providers/supported
@iamanantgupta Is Google Fit the same thing as Google Health? If so, we already have it.