[opensourcedex]

Open Wearables is a free, open source data engineering & integration project written in Python and released under MIT. It has 2,515 GitHub stars, 493 forks and 173 open issues, and was last pushed 8 hours ago. On this registry it ranks #20 of 39 tracked projects in Data Engineering & Integration, with 5 head-to-head comparisons available. It gained 24 stars over the last 6 tracked days.

What is Open Wearables?

What it is

Open Wearables is an open-source, self-hosted platform written in Python under the MIT license. It lives in the wearable health data and healthcare analytics ecosystem, and it provides a unified API and developer portal for connecting, syncing, and normalizing data from multiple wearable devices and fitness platforms.

The concrete problem it addresses is the repetitive integration work required when a health application supports several providers. Instead of building separate OAuth flows, data mapping, sync logic, unit handling, and maintenance paths for each service, it exposes normalized health data through one API and offers AI-ready automations and notifications for downstream health insights.

Key capabilities

  • The platform provides a unified API for wearable and fitness data, reducing the need to maintain separate provider integrations.
  • It supports normalized access to common metrics such as heart rate, sleep, activity, and steps across connected devices.
  • It includes a developer portal for connecting and syncing data from multiple wearable devices and fitness platforms.
  • It is designed for self-hosted deployment, allowing operators to keep wearable data on their own infrastructure.
  • It can be run locally with Docker Compose, and the README states that core functionality does not require third-party dependencies.
  • It plans to support AI-powered health insights and natural language automations, although these capabilities are marked as coming soon.
  • It mentions embeddable widgets and intelligent webhook notifications, with the widgets marked as coming soon.

Who uses it and how

  • Fitness coaching applications can connect user wearables and use unified data for personalized training recommendations.
  • Healthcare platforms can aggregate patient health data from several devices and configure automations for health alerts.
  • Research projects can collect standardized health data from multiple sources for analysis and comparison.
  • Non-technical product owners can test the platform by sharing connection links with users without building an application.
  • Individuals can self-host the platform to connect devices and explore metrics through the API, with future plans for an AI Health Assistant and personal insights.

Getting started

The README directs users to clone the repository, copy the backend and frontend example environment files, and start the application with Docker Compose. The recommended path is Docker-based local execution, and no hosted deployment option is mentioned.

When to use it — and when not to

Open Wearables is useful when an organization wants a Python-based, MIT-licensed, self-hosted integration layer for wearable data and can operate its own infrastructure. It is less suitable for teams that need a mature hosted service today, because the project is very young, lists zero contributors, and has 173 open issues. No paid products are listed as being replaced, and the facts do not specify database, storage, or SMTP requirements, so self-hosters should verify those needs first.

project readme (upstream, from github) — read inline

Open Wearables

License: MIT PRs Welcome Built with: FastAPI + React + Tanstack Discord

Open Wearables - Open infrastructure for wearable-powered health products. | Product Hunt

Documentation: https://openwearables.io/docs

Open-source platform that unifies wearable device data from multiple providers and enables AI-powered health insights through natural language automations. Build health applications faster with a single API, embeddable widgets, and intelligent webhook notifications.

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 each provider (e.g., Garmin, Whoop, Apple Health), you can use a single platform to access normalized health data and build intelligent health insights through AI-powered automations.

image

[!IMPORTANT] For Individuals: This platform isn't just for developers - individuals can self-host it to take control of their own wearable data. Connect your devices, explore your health metrics through the unified API, and stay tuned for upcoming features like the AI Health Assistant and personal health insights automations. Best of all, your data stays on your own infrastructure, giving you complete privacy and control.

Why Use It

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
  • 🤖 Build AI-powered health insights and automations using natural language (coming soon)
  • 🧩 Embeddable widgets for easy integration into your applications (coming soon)

The Problem It Solves:

Building a health app that supports multiple wearables typically requires:

  • Significant development effort per provider (Garmin, Whoop, Apple Health, etc.) to implement OAuth flows, data mapping, and sync logic
  • 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

  • 🏃 Fitness Coaching Apps: Connect user wearables to provide personalized training recommendations. Running coaches can create users, share connection links via WhatsApp, and test AI insights capabilities
  • 🏥 Healthcare Platforms: Aggregate patient health data from various devices and set up automations for health alerts
  • 💪 Wellness Applications: Track and analyze user activity across different wearables with AI-powered insights
  • 🔬 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
  • 👤 Personal Use: Individuals can self-host the platform to connect their own wearables, chat with their health data using the AI Health Assistant, and set up personal health insights - all with complete data privacy and control

Getting Started

Get Open Wearables up and running in minutes.

  1. Clone the repository:

    git clone https://github.com/the-momentum/open-wearables.git
cd open-wearables

  2. Configure environment variables:

    Backend configuration:

    cp ./backend/config/.env.example ./backend/config/.env

    Frontend configuration:

    cp ./frontend/.env.example ./frontend/.env

  3. Start the application

    Using Docker (Recommended):

    The easiest way to get started is with Docker Compose:

    docker compose up -d

    For local development setup without Docker take a look at docs

  4. Log in to the developer portal:

    An admin account is automatically created on startup using the ADMIN_EMAIL and ADMIN_PASSWORD environment variables (defaults: [email protected] / your-secure-password). The seed runs only while the developer table is empty: once any developer account exists it is skipped, so changing ADMIN_PASSWORD later does not update an existing account - change the default password from the developer portal right after your first login. To add further accounts, invite them from the developer portal.

    Open http://localhost:3000 to access the developer portal and create API keys.

  5. Seed sample data (optional): If you want test users and sample activity data:

    make seed

    This will create:

    • Test users
    • Sample activity data for test users

  6. View API documentation:

    Open http://localhost:8000/docs in your browser to explore the interactive Swagger UI.

Core Features

Developer Portal Dashboard

Web-based dashboard for managing your integration:

  • 📈 General Statistics: View number of users and data points at a glance
  • 👥 User Management: Add users via the portal or through the API
  • 📋 User Details: View connected data sources, integration status, and user metrics with visualizations
  • 🔑 API Key Management: Generate and manage credentials in the Credentials tab

Health Insights & Automations (coming soon)

The platform's most powerful feature - define intelligent health insights using natural language:

  • 💬 Natural Language Conditions: Describe when notifications should be triggered in plain English
  • 🔔 Webhook Notifications: Configure your backend endpoint to receive real-time health insights
  • 🧪 Test Automation: Run dry runs on historical data to see how automations work in practice
  • 👤 Human-in-the-Loop: Mark incorrect AI interpretations during testing to continuously improve the system
  • ✨ Improve Description: AI-powered suggestions to refine your automation descriptions
  • 📜 Automation Logs: Review past automation triggers and provide feedback

AI Health Assistant (coming soon)

  • 💬 Interactive chat interface for debugging and exploring user data
  • 🧩 Embeddable widget that can be integrated into any app with just a few lines of code
  • 🔄 Customizable AI models (swap models to match your needs)
  • 🔍 Natural language queries about user health metrics

Unified API

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

Provider Support

  • ☁️ Cloud-based: Garmin, Oura, Whoop, Suunto, Polar, Ultrahuman, Strava, Fitbit
  • 📱 SDK-based: Apple HealthKit, Samsung Health, Google Health Connect

OAuth Flow Management

Simplified connection process for end users:

  1. Generate a connection link for your user (or use the SDK widget)
  2. User authenticates with their wearable provider
  3. Data automatically syncs to your platform
  4. Access via unified API

Mobile Sync SDKs

Native SDKs for push-based health data sync from on-device health stores:

  • iOS SDK (Swift) - Apple HealthKit
  • Android SDK (Kotlin) - Samsung Health & Google Health Connect
  • Flutter SDK (Dart) - Cross-platform Flutter wrapper around native SDKs
  • React Native SDK (TypeScript) - Cross-platform React Native wrapper around native SDKs

Widgets (coming soon)

  • 🔌 Connection Widget: Allow users to connect their wearables directly from your app
  • 🤖 AI Health Assistant Widget: Embed the AI chat interface for user health queries

Architecture

Built with:

  • 🐍 Backend: FastAPI (Python)
  • ⚛️ Frontend: React + TanStack Router + TypeS

readme truncated — read the full docs on github

Frequently asked questions

Is Open Wearables free to use?

Open Wearables is open source under the MIT licence. There is no licence fee and no seat count — you can self-host it or, where the project offers one, pay a vendor for a managed version instead.

What does Open Wearables do?

Convert wearable data into actionable health insights with open algorithms

What is Open Wearables written in?

Open Wearables is primarily written in Python. Its source is publicly available at https://github.com/the-momentum/open-wearables, and it has 2,515 GitHub stars.