Launched this week
Open Wearables
Open infrastructure for wearable-powered health products.
1.4K followers
Open infrastructure for wearable-powered health products.
1.4K followers
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.
Can I use it as a proof of life?
Open Wearables
@pawel_soproniuk Technically yes: if HR or activity data is flowing, that's a proxy. The catch is latency. Most providers sync from device to cloud in batches, so you'd be looking at minutes delay, not real-time. Outbound webhooks (in development) plus the planned automation rules layer would make a "no signal in X hours, fire alert" pattern straightforward. For actual proof-of-life with strict timing guarantees, you'd want a device with continuous BLE streaming, that's a different architecture. Curious what you're building though, drop into Discord if you want to dig in.
Not a developer but I understand the problem well. I switched from Whoop to Oura last year specifically because I wanted to own my data and then realized neither platform gives you anything meaningful on export. Upvoted.
Open Wearables
@krzysztof_kundys this is exactly why we built it
"own your data" is marketed everywhere but the export is usually a CSV with 12 columns and no context. that's not ownership, that's a file dump
the goal is that your health data actually does something - feeds AI, triggers automations, gets reasoned over. not just sits in a folder
glad you upvoted, means a lot on launch day
@krzysztof_kundys Exactly! Whoop charges me $30/month and won't let me export my data in any useful format. I didn't realize this was a solved problem. Congrats to the team on shipping this.
@krzysztof_kundys That’s a pretty common realization after switching — the “you own your data” message sounds straightforward, but in practice the export layer is often just raw logs without much structure or context.
Open Wearables
@krzysztof_kundys "own your data" as a feature that doesn't actually let you own your data - that's the whole problem in one sentence
glad you upvoted, means a lot today
Open Wearables
@hamza_afzal_butt thank you!
fully customizable - that's kind of the whole point. the base algorithms are open so you can read exactly how a score is calculated, then tweak weights, swap inputs, or build your own on top
fixed black-box scores are what everyone else ships. we wanted the opposite
FuseBase
Great launch, team! This is super interesting, especially the “one API for wearables” angle. How many devices are supported today?
Open Wearables
@kate_ramakaieva Hey, we currently support Apple Health, Samsung Health, Google Connect, Polar, Suunto, Ultrahuman, Oura, Whoop, Strava, Fitbit.
Lancepilot
Open Wearables
@raihanshezanPlugs directly. Our MCP server gives any LLM (Claude, GPT, local via Ollama) structured access to user health data with context, scores, trends, anomalies, so you're not dumping raw numbers into a prompt. If you'd rather wire it into your own pipeline, the REST API works the same way.
For production-grade use cases (coaching, clinical reasoning, longitudinal context), an agentic layer on top earns its keep fast. We build that at Momentum for clients and might share some templates soon, stay tuned.
Healthtech open source is having a real moment. Between this and a few other projects I've seen lately, feels like the closed-platform model for health data is getting challenged from multiple directions.
Open Wearables
@renata_hara1 Health data is probably the worst category for closed platforms: it's sensitive, personal, and the people building on top of it often need to explain exactly how scores are computed to users or regulators. The pressure from open source was going to come eventually.
@renata_hara1 Yeah, there’s definitely a broader shift happening — less tolerance for “walled garden” health data, especially as people start accumulating years of wearable history across multiple devices.
@renata_hara1 It has, indeed.
Open Wearables
@renata_hara1 yeah the tide is turning
closed platforms made sense when the tooling didn't exist. now it's just a choice - and developers and builders are starting to notice there's a better one
good time to be building in this space
Rabbithole
I’ve previously built and sold a company using wearable data to predict drug relapses and then sought to build a better infrastructure layer for wearable data similar to how Stripe changed the world for fintech.
I didn’t do it nearly as well as Open Wearables has done it. Absolutely huge kudos to the team behind this — super excited to see it grow.
@raztronaut Razi this means a lot coming from someone who's actually been in the trenches with this data. The Stripe-for-fintech analogy is exactly the framing we kept coming back to - wearables need that layer or every team just keeps reinventing the same auth + schema mess. Would love to swap notes - DM open. 🙌
@raztronaut Haha, so maybe this is time to try with another product, but this time built around Open Wearables? :D