--- title: "Wearable Data Platform | Self-Hosted" description: "Every part of Open Wearables in one place: the wearable API, mobile SDKs, raw data, health scores, MCP server and the roadmap. Self-hosted, MIT licensed." canonical_url: "https://openwearables.io/platform" --- # One platform for the wearable data your product runs on. Platform Open Wearables collects data from the devices your users own, keeps it in one schema in your own cloud, and gives you what to build on top of it. Below is every part, with what ships today and what is on the roadmap. [Get started](https://openwearables.io/docs/quickstart) [Book a demo](https://openwearables.io/book?tier=pro) In Core ## What every deployment runs. Free and self-hosted, and each part has its own page. [See pricing](https://openwearables.io/pricing#core) ### Wearable API One schema across cloud providers and on-device stores, delivered over a REST API and webhooks. [Learn more](https://openwearables.io/platform/wearable-api) ### Mobile SDKs Read Apple Health, Health Connect and Samsung Health from inside your app, synced in the background. [Learn more](https://openwearables.io/platform/mobile-sdks) ### Raw data The provider's original payload kept under the schema, in a bucket you own. [Learn more](https://openwearables.io/platform/raw-data) ### MCP server Point Claude Desktop or Cursor at your deployment and ask about your users in plain language. [Learn more](https://openwearables.io/platform/mcp-server) ### Connect App A ready iOS and Android app, under your brand on request, that brings Apple Health, Health Connect and wearable data into your deployment. Free on every plan under the Open Wearables name. [Connect App](https://openwearables.io/platform/connect-app) Part of Pro ## What Pro adds to your deployment. Licensed modules and add-ons, running inside your own deployment. [Book a demo](https://openwearables.io/book?tier=pro) [See pricing](https://openwearables.io/pricing#pro) ### Health scores Sleep, recovery and activity scores from our science team, on one method. [Learn more](https://openwearables.io/platform/health-scores) ### AI insights An AI health coach on your users' own data. [Learn more](https://openwearables.io/platform/ai-insights) ### Medical-grade integrations A private catalogue of integrations with certified medical devices, added to your deployment as extensions and kept up to date by us. [See pricing](https://openwearables.io/pricing#modules) ### Observability Sync health per provider and per user across your deployment, so a broken connection is caught before your users notice. [See pricing](https://openwearables.io/pricing#modules) How it fits together ## From the device to the answer. 01 ### Collect Cloud providers connect server to server, and the mobile SDKs read the stores that live on the phone. Every source ends up in the same deployment. 02 ### Store Everything lands in one schema in your own database, with the original payload kept underneath, so a metric you invent later can be computed against history you already hold. 03 ### Compute Health scores from our science team, computed inside your deployment and validated before release. 04 ### Use Your product reads it over the REST API, reacts to webhooks, or asks questions through the MCP server. The same guarantees ## What holds across the whole platform. ### Your cloud, your region. Every part runs inside your own deployment, under your credentials, so health data does not reach a vendor tenant. - Your account - Your region ### One schema. A watch, a ring and a phone come back in one shape, whichever part of the platform reads them. - One schema - Any source ### Costs you can see. Running it costs your own cloud bill, paid to your provider. Deployment and Integration are one-off services, and health scores and the other licensed modules come with Pro. - Your cloud bill - One-off services ### No dependency on us. MIT licence, full source, public roadmap and public issues, plus community support on Discord. - MIT license - Full source - Discord ## Deploy Open Wearables in your own cloud The repository is public and the deployment is yours from the first commit. Start from the source, or bring us in to stand it up in your account. [Get started](https://openwearables.io/docs/quickstart) [Book a demo](https://openwearables.io/book?tier=pro) [See pricing](https://openwearables.io/pricing) FAQ ## Do you have more questions? ### Do we have to use every part? No. Most teams start with the Wearable API and add the rest as the product needs it: the mobile SDKs when on-device data matters, the MCP server when someone wants to ask the data questions. Each part works on the same deployment and the same schema, so adding one later does not change what you already built. ### Where can we see what is coming next? On the [public roadmap](https://openwearables.io/docs/roadmap) in the docs, which lists what is being built next. Anything on this page that is not live yet is marked as on the roadmap. ### Can we add our own sources or scores? Yes. The code runs in your own deployment, so you can add a provider by following [the guide in the docs](https://openwearables.io/docs/dev-guides/how-to-add-new-provider), or compute your own scores on the raw data you already hold. ### Where does it run? In a cloud account you control, in the region you choose. Locally it starts with Docker Compose in a few minutes. ### Can Momentum run it for us? Yes. If you would rather not run it yourself, Momentum can set it up and maintain it inside your own account, so the data and the deployment stay yours. ### Do we need a mobile app? Only for Apple Health, Health Connect and Samsung Health, because their data never leaves the phone on its own. Cloud providers connect server to server with no mobile work. For teams without an app, the [Connect App](https://openwearables.io/platform/connect-app) is that app: people join from an invitation and the data lands in your deployment.