--- title: "Open-Source Wearable Data, Self-Hosted" description: "Open-source wearable data infrastructure in your own cloud. Connect the devices your users own and build your own health intelligence on top." canonical_url: "https://openwearables.io/" --- # The wearable data layer, in your own cloud [Join our Discord community](https://discord.gg/qrcfFnNE6H) Open Wearables is open-source infrastructure for wearable data. Connect the devices your users already own, keep the raw payloads, and build scores, insights and coaching on top, all inside your own cloud account. [Get started](https://openwearables.io/docs/quickstart) [Book a demo](https://openwearables.io/book) Built by [2.6k](https://github.com/the-momentum/open-wearables) - Open source - Self-hosted - MIT license Built on Open Wearables - Heart Monitor logo - Hundred logo - JustGains logo - Lifelong logo - MoveTogether logo - Suna logo - Yoboo logo What you get ## Every part of the wearable layer, complete and handled A product on wearable data needs the same groundwork: integrations, one schema, sync from the phone and the raw data underneath. Open Wearables ships it as one open-source project. [See the whole platform](https://openwearables.io/platform) ### Wearable API One standard schema across the wearables your users own. Authorisation flows, webhooks, delivery history for debugging, an admin panel for keys and connection status. [Learn more](https://openwearables.io/platform/wearable-api) ### Mobile SDKs iOS, Android, Flutter and React Native, plus the Connect App for teams without an app of their own, so you can pull Apple Health and Google Health Connect data before you build one. [Learn more](https://openwearables.io/platform/mobile-sdks) ### Raw data access Original provider payloads kept underneath the standard schema, in your own database, for debugging and for whatever the schema does not cover yet. [Learn more](https://openwearables.io/platform/raw-data) ### Health scores Health scores built with our science team, computed in your deployment. Part of Pro. [Learn more](https://openwearables.io/platform/health-scores) ### AI insights Trends across weeks, anomalies worth a second look, and the context an assistant needs to say something useful. [Learn more](https://openwearables.io/platform/ai-insights) Why it runs in your cloud ## The layer has to be yours before what you build on it can be A hosted API keeps the data, and every score computed from it, in a vendor's account. Running the layer yourself keeps it where HIPAA, GDPR and your own policy say it belongs. ### Sovereignty Your regulator, your board or your own policy says health data does not sit in a third party's cloud. ### Residency The data has to stay in a country or region you choose, and you have to prove where it is. ### Control You run the deployment under your own credentials and decide who gets access. What you build on top of Open Wearables is yours. ### Your own reasons No regulator forcing it and no security review coming. You want the data in your own account anyway. The honest comparison ## Hosted SaaS API, in-house build, or self-hosted Where each one wins. Self-host for control, for data sovereignty, for a regulator or your own reasons, and Open Wearables saves you the in-house build. [Get started](https://openwearables.io/docs/quickstart) [Book a demo](https://openwearables.io/book) | | Hosted SaaS API | Build in-house | Open Wearables, self-hosted | | --- | --- | --- | --- | | [01] Where the data sits | Their cloud, their regions | Yours | Yours, your account, your region | | [02] Who can reach the data | The vendor and its sub-processors | Your team | Your team, and us under a DPA you sign when we work on it | | [03] Provider credentials | Theirs. Your users connect through the vendor's provider account | Yours to obtain from each provider | Yours to obtain. The relationship is between you and the provider | | [04] Cost shape | Scales with monthly active users | Salaries and infrastructure | You pay for the infrastructure it runs on, and that is flat as you grow | | [05] Where your team's time goes | Your product, within the vendor's limits | Keeping each integration working | The intelligence layer on top | | [06] Choose this when | Speed matters more than control, no regulator, no enterprise security review | Wearable integration is your core differentiator and you have the team | A rule, a contract or a customer review says the data stays with you, or owning it matters to you | What you build on it ## The foundation for intelligent health products Open Wearables gives you clean wearable data you own. What you build on top of it is yours, and Pro adds scores and insights inside your deployment. ### Scores your users check every morning Health scores from our science team, computed inside your deployment and validated before release. ### Intelligence on data you control The models and rules you build run on data in your own cloud, under your credentials. ### An insight worth reading Written from each user's own history, so it says what they could not see alone. A paid module. ### Coaching that sounds like you The same number reads differently for an athlete and for a patient. Your tone, your rules. A paid module. Who is it for ## One platform in your cloud, three ways to run it Each path runs the same open-source core in your own cloud account. What changes is what sits on top of it, and how you start. [See all solutions](https://openwearables.io/for) ### Digital health products Ship wearable features in your own product: scores your users check every morning, coaching from each user's own history, analytics across the devices they already wear. [Learn more](https://openwearables.io/#core) A member's wellness app: this week's activity, sleep and a challenge in progress. ### Care programmes Run a monitored programme without building the software: a patient app or SDK, a care view your team opens every morning, consent on every reading. [Learn more](https://openwearables.io/for/care-providers) A care team's week: which patients are syncing and which have gone quiet. ### Hospitals and telemedicine Wearable data in the record your clinicians already open: readings written into your EHR, with a source on every value. [Learn more](https://openwearables.io/for/hospitals-telemedicine) A patient's record with wearable readings beside visits, results and medication. Case studies ## Products running on Open Wearables [See all case studies](https://openwearables.io/case-studies) Heart Monitor Consumer heart health app ### How Heart Monitor shipped wearable integrations in a week One engineer connected six providers for around 90,000 users, and every reading stays in infrastructure Heart Monitor controls. [Read the case study](https://openwearables.io/case-study/heart-monitor) Lifelong Family health app ### How Lifelong is building an AI health companion for the whole family “It let us start building the family experience instead of rebuilding wearable ingestion.” Razi Syed, Founder, Lifelong [Read the case study](https://openwearables.io/case-study/lifelong) MoveTogether Social fitness app ### How MoveTogether runs on one wearable data layer “It let a small team ship a broad device lineup and keep it current.” Sam Pullen, Founder, MoveTogether [Read the case study](https://openwearables.io/case-study/movetogether) JustGains Social workout platform ### How JustGains puts every run, ride and rep in one feed “We read the code, added it to our fork, and shipped. That is the difference open source makes.” James Greene, Founder & Engineer, JustGains [Read the case study](https://openwearables.io/case-study/justgains) ## Whatever your users wear, one schema Cloud providers and on-device sources arrive in the same shape, so supporting another device later does not change your code. [Browse integrations](https://openwearables.io/integrations) - [Garmin integration](https://openwearables.io/integrations/garmin) - [Whoop integration](https://openwearables.io/integrations/whoop) - [Oura integration](https://openwearables.io/integrations/oura) - [Polar integration](https://openwearables.io/integrations/polar) - [Suunto integration](https://openwearables.io/integrations/suunto) - [Withings integration](https://openwearables.io/integrations/withings) - [Strava integration](https://openwearables.io/integrations/strava) - [Ultrahuman integration](https://openwearables.io/integrations/ultrahuman) - [SensorBio integration](https://openwearables.io/integrations/sensorbio) - [Google Health API integration](https://openwearables.io/integrations/google-health) - [Fitbit integration](https://openwearables.io/integrations/fitbit) - [Apple Health integration](https://openwearables.io/integrations/apple-health) - [Google Health Connect integration](https://openwearables.io/integrations/google-health-connect) - [Samsung Health integration](https://openwearables.io/integrations/samsung-health) ## Start free, then build on it Run the open-source core yourself for free. Pro puts our licensed modules and our team behind your production deployment; Enterprise adds the security, scale and SLA a company at scale needs. [See pricing](https://openwearables.io/pricing) ## Core Self-hosted For teams building their first wearable features. You run the open-source platform yourself. $0 Forever - One API across cloud and on-device sources - Unified data model, raw payloads in your bucket - SDKs for iOS, Android, Flutter and React Native - Sync, backfill and webhooks - Admin panel and MCP server - Connect App for up to 5 users - Open source, MIT license, Discord support [Get started](https://openwearables.io/docs/quickstart) ## Pro Subscription For products in production. Licensed modules, with our engineers behind your deployment. From $999 a month, per deployment Everything in Core, plus The Pro modules, in your deployment - [Health scores](https://openwearables.io/platform/health-scores) - [Health agent](https://openwearables.io/platform/ai-insights) - [Medical-grade integrations](https://openwearables.io/pricing#modules) - [Observability](https://openwearables.io/pricing#modules) - [Connect App, no user limit](https://openwearables.io/platform/connect-app) - Modules run in your own cloud - Onboarding session with our team - Slack channel with our engineers [Book a demo](https://openwearables.io/book?tier=pro) ## Enterprise Annual agreement For health organisations at scale, from digital health to hospital groups. We run and secure it in your cloud, under an SLA. Custom Everything in Pro, plus - SLA support - Updates verified on your data before you upgrade - Deployed and set up for your use case, such as remote patient monitoring, then maintained - Security reviews and questionnaires answered by us - SSO, roles and audit logging - Multi-tenant and multi-region - GDPR tooling, signed DPA and BAA - Roadmap input Delivered by The team behind Open Wearables. [Talk to us](https://openwearables.io/book?tier=enterprise) A care provider, hospital or telemedicine platform? See [care providers](https://openwearables.io/for/care-providers) or [hospitals and telemedicine](https://openwearables.io/for/hospitals-telemedicine). ## Add a self-hosted wearable layer to your product Clone the repository and connect your first provider in your own account today. Or book a demo and leave with a scoped plan for your deployment. [Get started](https://openwearables.io/docs/quickstart) [Book a demo](https://openwearables.io/book) FAQ ## What teams ask before they add the layer ### Is it really free? Yes. The core is MIT licensed, with the full source. We charge for Pro, an Enterprise agreement, the Deployment and Integration services and custom development. ### Can we use it for HIPAA and GDPR workloads? Yes. The data goes into your cloud account and nowhere else, so access, encryption and retention stay under the controls you already run. We do not run a hosted version. ### What is actually live today? The API, the SDKs, raw data retention, webhooks and the admin panel, all in the free core. Health scores, the health agent and medical-grade integrations come with Pro, and the live versus roadmap page lists which is which. ### How many users has this been tested on? It runs in production at consumer app scale. Load testing results and the methodology behind the scores are published rather than described on a call. ### Do you have SOC 2 or ISO 27001? No. The deployment runs inside your certified environment, which is how most teams answer this in their own audit. The security page states what we do have. ### Will you sign a DPA? Yes, whenever our people can reach your deployment: under Pro support, during a Deployment or Integration service, and for as long as Enterprise runs. Where you self-host on Core, there is no processing for us to agree to, because we never touch it. A BAA comes with Enterprise, where your cloud provider and your scope support it. ### Who gets provider credentials? You do, in your name. It is real work and approval is slow with some providers, so we start it on day one of a deployment. ### We use a hosted aggregator today. How hard is migration? Usually a re-integration rather than a data migration, because you own the raw payloads going forward. It is a scoping conversation, and it is the most common shape of deal we do. ### What if we outgrow the free version? Nothing changes technically. You are already running the thing we would deploy. You add Pro when your users need scores and insights, and an Enterprise agreement when you want somebody accountable. ### Do we need a regulator to justify self-hosting? No. Teams self-host for their IP, for data residency, for a regulator, or because they want the data and the model in their own account. When time to market is what counts, Open Wearables gives you the in-house plumbing ready from day one, and Pro adds what your users see on top, so owning the layer does not slow the launch.