Launched this week
Open Wearables
Open infrastructure for wearable-powered health products.
1.4K followers
Open infrastructure for wearable-powered health products.
1.4K followers
Build personalized health products with one API for every wearable. Access wearable data, open health scoring algorithms, and structured context your AI can reason with. Self-hosted, open-source, MIT licensed.
great idea. I am missing easy way to get data from my garmin watch!
Open Wearables
@gregory80pl Garmin is fully supported. Deploy on Railway in about 5 minutes and your watch data starts flowing through the API. GitHub link is in the description if you want to dig in.
@gregory80pl We too xd Garmin is a tough one, but we handled it!
OpenAI
This removes a huge dependency on multiple SDK integrations, yes??
Open Wearables
@divya_kothari1 Yes, basically you have the integration part covered by Open Wearables. Data fetched from different providers is aggregated and normalized, and you only need to consume APIs provided by Open Wearables instead of integrating with many providers. For some integrations like Apple Health you can only get the data from mobile device as they don't expose any APIs, but we also have SDKs for that to make these integrations easier 😎
@divya_kothari1 You still need a separate SDKs for Apple and Android, that's it.
Open Wearables
@jenson_chow1 Thanks, fair question. Honest answer: we've absorbed the maintenance burden rather than solved it. Provider changelogs, scope drift, rate-limit shifts all land on our team first, ship as patches, you pull the update. Three things make it sustainable: the team has been doing healthtech integrations for 10+ years (so we know each provider's quirks), enterprise contracts include SLA-backed commitment to maintain through breaking changes, and open source means contributors share the load (Fitbit, Ultrahuman, Oura were all community-contributed integrations). Won't pretend it's a permanent moat. It's ongoing work. The bet is that one well-maintained open layer beats every team rebuilding the same OAuth dance in isolation.
Spent some time in the repo before commenting – looks like the data model is actively evolving, which makes the question I had even more relevant. The docs frame ingestion as either Cloud-based (OAuth provider) or SDK-based. Is there a planned third pattern for sources that fit neither – e.g. a desktop client generating data locally and POSTing records via the public API directly? Technically nothing seems to block it, but curious whether that's intended usage or off-pattern.
Have a project sitting in this exact gap, so watching with interest. Aware it's early-stage.
Congrats on shipping 🚀
Open Wearables
@zhuzhavladislav not sure if that's the case, but we have data generator built in the Open Wearables dashboard - you can see it in action in our docs: https://openwearables.io/docs/dev-guides/seed-data-generator#seed-data-generator
And like you've mentioned - it could be also done by any client and using POST endpoints to store data in OW
@piotr_sobusiak Got it, thanks Piotr – that's what I needed to know. Will dig into the POST endpoints 🙌
As I’m not a developer, is there an easy way for me to test this tool?
Open Wearables
@michal_kukul sure, probably the easiest way to give it a try is using one-click deployment on Railway - you can check how it works in our docs: https://openwearables.io/docs/deployment/railway
Quick one: can you use this with just Apple Health data from an iPhone, no additional wearable required?
Open Wearables
@mikolaj_sedzik Yes. Apple Health works standalone, you'll get whatever's already in HealthKit (steps, heart rate, sleep, workouts, etc., depending on what apps and devices feed it). Just needs the iOS, Flutter, or React Native SDK to pull the data, since HealthKit is on-device only.
Open Wearables
@mikolaj_sedzik worth to mention we already have an app to sync your Apple Health - most likely will be available soon on App Store
Lancepilot
Open Wearables
@priyankamandal Thanks Priyanka. Self-hosted + MIT removes two of the hardest conversations with compliance teams: where does the data live, and what happens if the vendor disappears. The architecture is HIPAA-ready out of the box (encryption, audit logging, RBAC), though the cert itself sits with whoever operates the deployment, not the software.
@priyankamandal Open source community is a real strength! We have 40+ contributors.