Open Wearables

Basic setup takes minutes using Docker. Open Wearables itself deploys in minutes but you need to apply for API credentials with each wearable provider (Garmin, Oura, etc.). Provider approval processes vary, some are immediate, others take weeks. It's a one-time process, and it's the same whether you use Open Wearables or build integrations yourself. Once you have credentials, the actual integration (OAuth flows, data sync, testing) takes days, not months.

Yes. You apply directly to each wearable provider (Apple, Garmin, Oura, etc.) for API credentials. This typically takes 1–4 weeks per provider. You create developer accounts with each platform, submit applications explaining your use case, and receive OAuth client IDs and secrets. These credentials live in your environment variables, not in a vendor's system. The benefit: you own the relationship with wearable providers directly. The tradeoff: you handle the application process yourself, though Momentum can guide you through it if needed.

Open Wearables is MIT licensed, so the platform itself is free to use commercially. You pay for your own infrastructure (hosting, database storage), optional expert services or custom features from Momentum, and LLM API costs if you use AI chat features. Because you self-host, your cost tracks your infrastructure rather than your user count. SaaS aggregators charge $1-3+ per active user, so for B2C apps with thousands of users those charges can consume 20-40% of margin just for wearable data access.

Ongoing costs include infrastructure (hosting and database storage, scaling with your data volume) and optional LLM API costs if using AI features. No hidden fees, no pricing tiers. Open Wearables itself is MIT licensed, so you pay only for the infrastructure you would need anyway.

Absolutely. The platform provides normalized, time-series health data in a consistent format across all wearable devices, creating the foundation for your proprietary algorithms and AI models. Instead of spending months on data cleaning and integration, you get clean, structured data ready for machine learning from day one. Teams are building personalized recovery scores, training readiness indicators, stress detection algorithms, sleep quality predictions, and custom health insights.

Data lives on your infrastructure. Open Wearables is self-hosted, which means you control where data goes, who can access it, and how long it's retained, it never flows through our servers. The platform always runs on your servers, not ours. For HIPAA or GDPR compliance, this matters because you can demonstrate complete data lineage without third-party data processing agreements.

Deploy Open Wearables locally using Docker. The platform includes sample data generation scripts that populate realistic health data, just run 'make seed' to seed synthetic user data and test your integration without connecting actual wearables. For Apple Health testing, you'll need physical iOS devices since HealthKit doesn't work in simulators.

Yes, but it depends on the provider. Apple Health supports full historical synchronization through the Flutter SDK. Garmin provides recent data by default, with historical access depending on your developer agreement. Other providers vary, most support some level of historical backfill through their APIs. For new users connecting wearables, historical data means they see immediate value instead of starting from zero.

Open Wearables collects data from all connected sources. Deduplication happens when multiple devices report the same metric for the exact same timestamp. The platform resolves duplicates using configurable priority rules at two levels: device-type priority (smartwatch > phone > other devices) and provider priority (choose between providers when device types match). You configure these rules in your Open Wearables instance.

No. Open Wearables currently operates as read-only, meaning you can pull health data from wearables but not write data back to them. This covers the majority of health app use cases: tracking metrics, analyzing patterns, providing coaching insights, and building personalized recommendations. Write capabilities may change in future releases based on community demand. If your application specifically requires write functionality, you'll need to implement direct integrations with individual wearable APIs alongside Open Wearables.