Open Wearables Review
A FastAPI + React platform that unifies wearable data from Garmin, Polar, Suunto, Oura, Whoop, Strava, Fitbit, and more through a single self-hosted API.
Each review covers deployability, value versus commercial alternatives, and privacy model. Tools that can run locally were started and exercised; mobile or backend-dependent tools were assessed from published builds, source code, and deploy guides. Ratings reflect what we were able to verify.
Open Wearables — Self-Hosted Wearable Data Unification Platform
A FastAPI + React platform that unifies wearable data from Garmin, Polar, Suunto, Oura, Whoop, Strava, Fitbit, and more through a single self-hosted API. Last updated: 2026-06-21.
One-sentence verdict: A developer-focused wearable-data gateway with a polished portal and broad provider support, best suited for teams building health apps that need normalized sensor data.
What the System Is
Open Wearables is a self-hosted platform for wearable device data. It is built as:
- FastAPI backend with OpenAPI/Swagger docs.
- React + TanStack Router + TypeScript frontend.
- PostgreSQL + Redis for data and caching.
- Celery for background sync jobs.
- Svix for webhook notifications.
- OAuth flow management for wearable providers.
- Mobile SDKs for iOS, Android, Flutter, and React Native.
Supported cloud providers include Garmin, Oura, Whoop, Suunto, Polar, Ultrahuman, Strava, and Fitbit. SDK-based providers include Apple HealthKit, Samsung Health, and Google Health Connect. The deploy guide notes a small fix is needed: the Compose file references postgres:18, which should be changed to postgres:17.
| Key data | |
|---|---|
| Category | Wearables / Developer Platform |
| Language | Python / FastAPI + React |
| License | MIT |
| Self-hosted | Yes |
| AI | Planned (AI Health Assistant, automations) |
| Database | PostgreSQL + Redis |
| Deployment | Docker Compose |
How to Install and Deploy
The deploy guide applies a small Postgres image fix before starting.
cd /data2/docker/going-global/repos/open-wearables
# Fix docker-compose postgres image
sed -i 's/postgres:18/postgres:17/' docker-compose.yml
cp backend/config/.env.example backend/config/.env
cp frontend/.env.example frontend/.env
# Edit backend/config/.env: SECRET_KEY, ADMIN_PASSWORD, OAuth clients
# Edit frontend/.env: VITE_API_URL
docker compose up -d
Then open http://localhost:3000 for the developer portal and http://localhost:8000/docs for the Swagger API docs.
How to Test
The documented test flow is:
- Open
http://localhost:3000and log in with the admin credentials configured inADMIN_EMAIL/ADMIN_PASSWORD(defaults areadmin@admin.com/your-secure-password). - Create an organization user and generate an API key.
- Create a connection link for a supported provider (e.g., Garmin, Polar, Suunto).
- Complete the OAuth flow for a test account.
- Verify data sync and access normalized metrics through the unified API.
- Explore the Swagger docs at
http://localhost:8000/docs.
Privacy & Compliance
Open Wearables is self-hosted, so health data stays on your own infrastructure. However, OAuth connections with wearable providers involve third-party data flows, and the roadmap includes cloud-dependent AI features. It is not advertised as HIPAA compliant. Do not use it for PHI without a full compliance review and appropriate agreements with wearable providers.
Open Wearables vs Commercial Wearable APIs
| Dimension | Open Wearables | Commercial API (e.g., Terra, Vital, Human API) |
|---|---|---|
| Cost | Free / self-hosted | Usage-based SaaS |
| Data location | Your server | Vendor cloud |
| Provider coverage | Garmin, Polar, Suunto, Oura, Whoop, Strava, Fitbit, Apple Health, Samsung Health, Google Health Connect | Often broader and commercially maintained |
| Mobile SDKs | iOS, Android, Flutter, React Native | Varies |
| Setup effort | High: Docker, OAuth keys, Redis, Postgres | Low: API key signup |
| AI features | Roadmap | May already be offered |
| Open source | Yes | No |
Who Should Use It
- Developers building health or fitness apps that need normalized wearable data.
- Enterprises that want to self-host wearable integrations for data-control reasons.
- Teams that already maintain OAuth relationships with wearable providers.
Who Shouldn't Use It
- Non-technical users looking for a plug-and-play consumer health app.
- Teams without the resources to configure and maintain OAuth apps across multiple wearable providers.
- Anyone needing a HIPAA-compliant wearable data pipeline out of the box.
FAQ
Which wearable providers does Open Wearables support?
Cloud-based: Garmin, Oura, Whoop, Suunto, Polar, Ultrahuman, Strava, Fitbit. SDK-based: Apple HealthKit, Samsung Health, Google Health Connect.
Why do I need to change postgres:18 to postgres:17?
The checked-in docker-compose.yml references postgres:18, which does not exist at the time of the deploy guide. Changing it to postgres:17 allows the database container to start.
Is the AI Health Assistant available?
It is listed on the roadmap as "in development" and is not available in the current release.
Verdict
Open Wearables is a promising self-hosted alternative to commercial wearable-data APIs. The developer portal, unified API, and broad provider support are genuinely useful. The trade-off is the operational burden of configuring OAuth apps and maintaining the self-hosted stack. AI features are still on the roadmap.
Ratings: Deployability 3/5 · Value vs Commercial 4/5 · Privacy Compliance 4/5