Open Wearables, launching open infrastructure for wearable health products
We launched Open Wearables on Product Hunt today. For teams building AI agents, coaches, or copilots in health, OW turns raw wearable streams into the structured, scored, time-series context an LLM can actually reason over.
What it is
One open-source layer for building health products on top of wearable data.
Unified API across Oura, Garmin, Whoop, Apple Health, Polar, Suunto, Samsung, Strava, and Google Health Connect
Standardized schema, so you stop writing per-vendor normalization code
Open scoring algorithms you can audit, fork, and tune for your domain
Coaching profiles for wellness, clinical, and performance use cases
MCP server, so any LLM can reason over health trends instead of just reading raw numbers
Self-hosted by design, MIT licensed, HIPAA and GDPR friendly
$0 per user at any scale
Our story
We're Momentum, a healthtech engineering company. For the last decade, we've shipped digital health, wellness, and clinical products with teams across regulated industries. And every single time, the same thing happened: weeks of plumbing before anyone touched the actual product. New vendor, new API, new schema, new quirks.
After watching the same wheel get reinvented in dozens of codebases, we put the whole stack in the open. Open Wearables is what we wish had existed when we started. It's already running in production inside healthcare and wellness apps, including AI coaching products built on top of it.
The bet is simple. Wearable data is becoming infrastructure, not a feature. Infrastructure should be open.
Help us out
If any of this is useful to you or to a team you know, an upvote makes a real difference today.
Upvote here → https://www.producthunt.com/products/open-wearables
Try it: openwearables.io
Happy to answer anything in the comments.

Replies
Curious about the scoring algorithms part. Who defines what “good” or “healthy” looks like across different use cases? That layer seems powerful, but also very sensitive depending on context
@lara_bishop This feels more like infrastructure than a product. Which is interesting because people often underestimate how valuable that layer is. If it works well, a lot of downstream tools could depend on it.