Open Wearables

Open Wearables removes the work of integrating each wearable vendor separately. Rather than writing an OAuth flow, a data mapping and sync logic for Garmin, then again for Whoop, then again for Apple Health, you read normalized health data from a single API.

The backend is FastAPI with PostgreSQL, Redis and Celery running the sync jobs, while the developer portal is React with TanStack Router and TypeScript. Authentication is self-contained, needing no external identity service, and each deployment serves one organization, so there is no multi-tenancy to reason about.

Some pieces are ready today and others are still being built.

• Developer portal: a dashboard for adding users, inspecting connected sources and generating API keys.
• Connection links: a user opens a link, authenticates with their provider, and data begins syncing.
• Cloud providers: OAuth and workout sync currently work for Garmin, Polar and Suunto.
• Mobile SDKs: native iOS and Android libraries push from Apple HealthKit, Samsung Health and Google Health Connect, with Flutter and React Native wrappers.
• Health insights: automations described in plain English, an AI assistant and embeddable widgets are in development.

Setup is two copied environment files and docker compose up. An admin account is seeded on first start, and that default password should be changed from the portal immediately. This is an early-stage project whose APIs may change before version 1.0, so pin a version in production. Individuals can self-host it for their own data too.