Skip to main content
Open Wearables - Open infrastructure for wearable-powered health products. | Product Hunt

Welcome to Open Wearables

Open-source platform that unifies wearable device data from multiple providers. Build health applications faster with a single API and normalized health data.

Get started

Follow our quickstart guide to set up Open Wearables in minutes.

What It Does

Open Wearables provides a unified API and developer portal to connect and sync data from multiple wearable devices and fitness platforms. Instead of implementing separate integrations for Garmin, Fitbit, Oura, Whoop, Strava, Apple Health, and more, you can use a single platform to access normalized health data.
For Individuals: This platform can also be used by individuals who want to interact with their own wearable data. Connect your devices and query your health data from AI assistants like Claude or Cursor through the MCP server - all while keeping your data on your own infrastructure.

Key Features

Unified API

Access health data through a consistent REST API regardless of the source device.

Multiple Providers

Connect cloud-based wearable platforms and on-device health data from mobile apps, with new providers added regularly.

MCP Server

Query wearable health data in natural language from AI assistants like Claude Desktop and Cursor.

Self-Hosted

Deploy on your own infrastructure with full data control.

Why Use Open Wearables

For Developers Building Health Apps:
  • ๐Ÿ”Œ Integrate multiple wearable providers through one API instead of maintaining separate implementations
  • ๐Ÿ“Š Access normalized health data across different devices (heart rate, sleep, activity, steps, etc.)
  • ๐Ÿ  Self-hosted solution - deploy on your own infrastructure with full data control
  • ๐Ÿš€ No third-party dependencies for core functionality - run it locally with docker compose up
The Problem It Solves: Building a health app that supports multiple wearables typically requires:
  • โฑ๏ธ Weeks of development per provider integration
  • ๐Ÿ” Managing different OAuth flows and APIs for each service
  • ๐Ÿ“ฆ Handling various data formats and units
  • ๐Ÿ”ง Maintaining multiple SDKs and dealing with API changes
Open Wearables handles this complexity so you can focus on building your product.

Use Cases

  • ๐Ÿ‘ค Personal Use: Individuals can self-host the platform to connect their own wearables, and query their health data from AI assistants through the MCP server - all with complete data privacy and control
  • ๐Ÿƒ Fitness Coaching Apps: Connect user wearables to provide personalized training recommendations. Running coaches can create users and share connection links via WhatsApp
  • ๐Ÿฅ Healthcare Platforms: Aggregate patient health data from various devices and build your own health alerts on top of outgoing webhooks
  • ๐Ÿ’ช Wellness Applications: Track and analyze user activity across different wearables
  • ๐Ÿ”ฌ Research Projects: Collect standardized health data from multiple sources
  • ๐Ÿงช Product Pilots: Non-technical product owners can test platform functionality by sharing connection links with users without needing their own app

Next Steps

Quickstart

Get up and running with Open Wearables in minutes.

API Reference

Explore the unified API endpoints.

Flutter SDK

Sync health data from Apple Health and Health Connect.

React Native SDK

Sync health data from Apple Health and Health Connect.

GitHub

View the source code and contribute.

Discord

Join the community, ask questions, and get help.