... year and saw several very large launches: Kilo Code v7 for VS Code = Dev Tools + Open

... Quick update for anyone who followed the OpenWearables launch. We just published the second edition of our

... launched OpenWearables on Product Hunt today. For teams building AI agents, coaches, or copilots in health, OW turns raw

... your users? How do you calculate it consistently across 5 different devices? What's the HRV baseline for a 60-year-old versus a 25-year-old? Another few months of research and engineering. That's why we built Open

... Body Battery, Oura gives a Readiness Score. Three different algorithms, three different scales, no way to compare them. You either pick one device and exclude everyone else, or you build your own normalization layer from scratch. We launched OpenWearables on Product Hunt today to fix exactly this. It's an

... just went live. OpenWearables is an

... hardware problem. It's an algorithm problem. Different weightings, different baseline calculations, different thresholds - all proprietary, all invisible. You're left choosing which black box feels more right today. The reason we open-sourced the scoring algorithms in Open

... than you'd think: An algorithm tuned for 25-year-old athletes gives bad scores to 65-year-old cardiac rehab patients Sleep scores built for monophasic sleepers break for shift workers HRV baselines vary wildly between populations With OpenWearables every algorithm is

... massive daily value versus those that are just cool, experimental concepts. I'd love to hear what your tech stack looks like. I'll start with mine: Most useful - as working in wellness healthcare, my fav right now is Open

... users. At 10,000 users: $5,000-20,000/month. Just for data access. No scoring, no AI. Just moving heart rate from point A to point B. At 100,000 users: $50,000-200,000/month. For data plumbing. OpenWearables: you pay for your own infra. $200-500/month for a typical startup, whether you have 1,000 or 100,000 users. Data layer, scoring, AI reasoning, all MIT licensed. We think the margin should be in what you build ... ... maksymowicz): @judith_wang  Per-user pricing is fine at 100 users. At 10,000 it becomes a business model problem. Self-hosted means you pay for infrastructure only: at that scale, the difference is typically $200-500/month

... 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 OpenWearables, 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 ... ... 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. Oura, WHOOP, Garmin they're all great devices but their scores are black boxes.

... Something we kept running into across projects: wearable integration eats months and adds zero product value. Every provider does things differently. Garmin sends XML. Whoop sends JSON but paginates differently than Oura. Apple Health needs on-device processing. Samsung has its own SDK. Different auth flows, different rate limits, different webhook formats. A typical startup spends ... ... months just getting data flowing from 3-4 providers. Then another month normalizing everything so a Garmin sleep session and a Whoop one are actually comparable. That's time you could spend on what makes your product different. Open

... Piotr, one of the people behind OpenWearables. we're launching on PH in the coming weeks and I wanted to actually show up in the community before that, not just drop a link on launch day.