--- title: "Live versus Roadmap" description: "What runs in production today and what is still being built, on one page, updated when it changes." canonical_url: "https://openwearables.io/live-vs-roadmap" --- # What runs today, and what does not. Live versus roadmap Software companies describe what they are building as though it already exists. This is the list of what actually runs, so you can check the rest of the site against it. [Get started](https://openwearables.io/docs/quickstart) [Book a demo](https://openwearables.io/book) Live ## The whole platform, as it runs today. Everything here is in the project you clone, from the first connection to the developer portal, except what is marked Pro: those are licensed modules that run in your own deployment. Anything not listed is not built yet. 01 ### Connect Every source your users already wear. - [Cloud providers and more](https://openwearables.io/integrations) - [Mobile SDKs](https://openwearables.io/platform/mobile-sdks) - [Connect App](https://openwearables.io/platform/connect-app) - [Apple Health XML import](https://openwearables.io/docs/api-reference/guides/apple-xml-import) - [Historical backfill](https://openwearables.io/docs/providers/historical-data) 02 ### Store One model, in your own cloud. - [Unified data model](https://openwearables.io/platform/wearable-api) - Daily summaries - [Raw payloads](https://openwearables.io/platform/raw-data) - Source priorities - Archiving and retention - [Coverage matrix](https://openwearables.io/docs/providers/coverage) 03 ### Compute Scores and answers, inside your deployment. - [Health scores Pro](https://openwearables.io/platform/health-scores) - [Health agent Pro](https://openwearables.io/platform/ai-insights) - Provider scores, passed through - [MCP server](https://openwearables.io/platform/mcp-server) 04 ### Deliver Into your product, on your schema. - [REST API](https://openwearables.io/platform/wearable-api) - [Outgoing webhooks](https://openwearables.io/webhooks) - [Live sync status](https://openwearables.io/docs/api-reference/guides/sync-status-stream) - Write-only mobile tokens 05 ### Operate A deployment you can see into. - [Developer portal](https://openwearables.io/docs/developer-portal) - Team and API keys - [Seed data generator](https://openwearables.io/docs/developer-portal/settings/seed-data-generator) - [Docker or Railway](https://openwearables.io/docs/deployment/docker) - [Add your own provider](https://openwearables.io/docs/dev-guides/how-to-add-new-provider) - [MIT licensed source](https://github.com/the-momentum/open-wearables) [See what's coming next](https://openwearables.io/live-vs-roadmap#roadmap) Roadmap ## What we are building next The modules planned for Open Wearables, grouped by what each one adds. Everything here is planned, not live, and has no date until it ships. ### Interoperability Data your clinical partners' systems can read. EHR-ready output In Core Planned The data model written out in the form record systems read (observations, devices, provenance and consent), so an EHR can take it in as is. ### Compliance The controls your auditors ask for. Data deletion and retention In Core Planned A user's data removed on request, and kept only as long as your policy says. Auditable access In Core Planned A record of who read which user's data, and when. ### Data sources New sources in the same model as the wearables. CGM Custom work Planned Add continuous glucose to the same user profile and timeline. Lab results Custom work Planned Show blood work next to wearable data in one user profile. Medical-grade devices In Pro Planned Bring certified medical devices into the same data model as consumer wearables. Raw signal processing Custom work Planned Turn raw sensor signals into metrics of your own, for teams building hardware. ### Infrastructure Faster data where your product needs it. Real-time data Custom work Planned React to heart rate and activity as they happen, not hours later. 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 providers you can connect today. Cloud providers connect server to server, and the phone's health stores through the SDKs. Every one lands in the same schema. [Browse all 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) ## If something missing here decides your timeline, ask Where a thing sits for your case is a better conversation than a guess at a date. Bring the one you need and we will tell you honestly where it stands. [Book a demo](https://openwearables.io/book) FAQ ## Common questions. ### How do you decide what counts as live? It runs in Open Wearables today and you can use it. Something planned, in progress or shown once in a demo is not on this page. ### Where do we see what is coming next? In [the roadmap](https://openwearables.io/live-vs-roadmap#roadmap) on this page, grouped by what each module adds, with no dates. For technical detail and sequencing, [the roadmap in the docs](https://openwearables.io/docs/roadmap) is kept current by the product team. ### Which providers can we connect? The [integrations page](https://openwearables.io/integrations) lists every provider, and [the coverage matrix](https://openwearables.io/docs/providers/coverage) shows what each one returns. ### Is all of it free? Not all of it. Running the platform yourself costs your own cloud bill, and the Pro modules, health scores and the health agent among them, are licensed. The plans and the work Momentum does around them are on [the pricing page](https://openwearables.io/pricing). ### How do we keep up with what changes? Each release is published on [GitHub](https://github.com/the-momentum/open-wearables/releases), and this page is updated when something new starts to run. ### We need something that is not live yet. Can we get it sooner? Sometimes. Momentum builds custom features on top of the platform. Tell us what you need and where it sits for your timeline, and we will say honestly whether that is realistic. ### Can we add a provider that is not supported? Yes. The code is in your repository, and [the guide in the docs](https://openwearables.io/docs/dev-guides/how-to-add-new-provider) walks through adding one.