---
title: "Pricing: Core, Pro and Enterprise"
description: "Open Wearables runs in your own cloud. Core is free to self-host, Pro adds scores and insights for apps in production, Enterprise adds the assurance."
canonical_url: "https://openwearables.io/pricing"
---

# What it costs to run Open Wearables in your own cloud

Everything runs in your own cloud account. Run the core yourself for free, or put our team behind it with Pro or Enterprise.

## 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 the three paths](https://openwearables.io/pricing#paths)

## Compare every feature, plan by plan

Platform, Pro modules, support, services and security, side by side.

The full picture

## Compare what each plan includes

| Feature | Core You run it yourself. $0 Self-hosted [Get started](https://openwearables.io/docs/quickstart) | Pro Scores, insights and cleaner data. From $999 Per month, per deployment [Book a demo](https://openwearables.io/book?tier=pro) | Enterprise Run, maintained and secured at scale. Custom Annual agreement [Talk to us](https://openwearables.io/book?tier=enterprise) |
| --- | --- | --- | --- |
| Wearable integrations Garmin, Oura, Whoop, Polar and more, connected through one standard schema. | Included | Included | Included |
| OAuth flow management | Included | Included | Included |
| Data sync New data from each provider lands in your own database as it arrives. | Included | Included | Included |
| Mobile SDKs iOS, Android, Flutter and React Native, for on-device sources like Apple Health and Health Connect. | Included | Included | Included |
| Developer dashboard | Included | Included | Included |
| Raw payload retention Original provider payloads kept for debugging. Off by default. | Included | Included | Included |
| MCP server Lets an AI assistant query a user's wearable data through your own deployment. | Included | Included | Included |
| Community on Discord | Included | Included | Included |
| Slack channel with our engineers A shared Slack channel where your team talks directly to the engineers who build Open Wearables. | Not included | Included | Included |
| Updates verified on your data Before you upgrade, we run the new release and its migrations against your deployment's data and tell you what changes. | Not included | Not included | Included |
| Ongoing maintenance Provider API changes, updates and fixes handled after launch. | Not included | Not included | Included |
| SLA support Response times agreed in your contract, for when something breaks. | Not included | Not included | Included |
| Roadmap input Your product's needs weighed when we decide what to build next. | Not included | Not included | Included |
| Health scores Scores designed and validated by our science team, running on your users' data in your cloud. | Not included | Included | Included |
| Health agent Plain-language answers for each user about their own data, inside your app. | Not included | Included | Included |
| 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. | Not included | Included | Included |
| Connect App A ready-made iOS and Android app, under the Open Wearables name, that brings your users' Apple Health, Health Connect and wearable data to your servers, without building a mobile app. | Up to 5 users | No user limit | No user limit |
| Connect App under your brand The same app under your brand, in your own store accounts. A paid option, per platform. | Not included | $5,000 per platform $5,000 per platform, iOS or Android. Your name, icon and colours, in your own store accounts. [Talk to us](https://openwearables.io/book?tier=custom) | $5,000 per platform $5,000 per platform, iOS or Android. Your name, icon and colours, in your own store accounts. [Talk to us](https://openwearables.io/book?tier=custom) |
| Observability Sync health per provider and per user across your deployment, so a broken connection is caught before your users notice. | Not included | Included | Included |
| What is planned next is on [the roadmap](https://openwearables.io/live-vs-roadmap#roadmap). |  |  |  |
| Deployment in your cloud Production and staging, infrastructure as code in your repository, provider onboarding and handover documentation. | From $4,800 From $4,800, one-time. Production and staging in your cloud and region, providers onboarded under your credentials. Final figure confirmed before you commit. [Talk to us](https://openwearables.io/book?tier=deployment) | From $4,800 From $4,800, one-time. Production and staging in your cloud and region, providers onboarded under your credentials. Final figure confirmed before you commit. [Talk to us](https://openwearables.io/book?tier=deployment) | Included |
| Integration into your app The connection and consent flow in your own interface, behind your existing login, tested end to end before launch. | From $9,600 From $9,600, one-time, deployment included. The connection flow built into your app, behind your existing login. [Talk to us](https://openwearables.io/book?tier=integration) | From $9,600 From $9,600, one-time, deployment included. The connection flow built into your app, behind your existing login. [Talk to us](https://openwearables.io/book?tier=integration) | Included |
| Custom development Features, AI and coaching logic, or a whole healthcare or wellness app, built by Momentum. | Per scope Your product built by the team behind Open Wearables, at a fixed price per scope or from a monthly pool of engineering time. [Talk to us](https://openwearables.io/book?tier=custom) | Per scope Your product built by the team behind Open Wearables, at a fixed price per scope or from a monthly pool of engineering time. [Talk to us](https://openwearables.io/book?tier=custom) | Per scope Your product built by the team behind Open Wearables, at a fixed price per scope or from a monthly pool of engineering time. [Talk to us](https://openwearables.io/book?tier=custom) |
| SSO and roles Single sign-on and role-based access for your team in the developer portal. | Not included | Not included | Included |
| Audit logging A record of who accessed what in your deployment, for your auditors. | Not included | Not included | Included |
| Multi-tenant and multi-region Separate tenants for your own customers, and deployments in more than one region. | Not included | Not included | Included |
| GDPR tooling Data export, deletion and retention handled for your users' requests. | Not included | Not included | Included |
| Signed DPA A data processing agreement, signed whenever our people work on your running deployment. | With a service Signed when a Deployment or Integration service gives our people access to your running deployment. | Included | Included |
| Signed BAA, where supported A business associate agreement for HIPAA work, where the setup supports it. | Not included | Not included | Included |
| Security questionnaires Answers to your customers' and auditors' security questionnaires. | Not included | Not included | Included |
| Infrastructure hardening The deployment's configuration reviewed and tightened against common attacks. | Not included | Not included | Included |

- FROM: One-time, from that price
- PER SCOPE: Priced once scoped with you
- INCLUDED: Part of Enterprise

Is Open Wearables for you

## Three paths our clients usually choose

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.

### Digital health products

Build your product on a wearable data layer you own. It connects the devices your users already wear and runs secured in your own cloud account as your user base grows.

[Learn more](https://openwearables.io/for/digital-health)

### Care programmes

Run a monitored programme without building the software: a patient app and a care view for your team, running and secured in your own cloud account from the first reading.

[Learn more](https://openwearables.io/for/care-providers)

### Hospitals and telemedicine

Wearable data in the EHR your clinicians already open, with a source on every value and the evidence an auditor asks for, running in your own cloud account as you roll out site by site.

[Learn more](https://openwearables.io/for/hospitals-telemedicine)

The team behind it

## Built by Momentum, the team behind Open Wearables

A healthcare software company building health data software since 2016. The engineers who built Open Wearables deploy it and build on it for clients.

[Visit Momentum](https://www.themomentum.ai/) [Talk to us](https://openwearables.io/book?tier=custom)

Building health data software since

2016

Healthcare only

100%

Certified quality system

ISO 13485

Rating on Clutch

4.9 / 5

FAQ

## Do you have more questions?

### Is the free version really free?

Yes. MIT license, full source, no trial window. We charge for Pro, for Enterprise, and for deployment work if you want it done for you.

### How is Pro priced?

From $999 a month per production deployment, staging included. It includes health scores, the health agent, medical-grade integrations and observability. The [Connect App](https://openwearables.io/platform/connect-app) is included under the Open Wearables name with no user limit; a version under your brand is a paid option at $5,000 per platform. A second region, a second brand or a second client of your platform counts as a second deployment.

### Can we run it ourselves after the deployment?

Yes, and plenty do. You get the infrastructure code, the diagram, the operations guide and a walkthrough, plus 30 days of support. Enterprise is a decision you can take later.

### We have more than one app. What changes?

Integration covers one app, because that is where the connection flow gets built. A second app, whatever it runs on, is a second piece of front-end work and we scope and price it separately. Deployment is identical either way.

### What happens if we stop paying?

Nothing stops. The platform sits in your cloud account, under your credentials, built from infrastructure code in your repository, under an MIT license. You lose the licensed modules, the on-call and the tested upgrades, not the platform and not the data.

### What does it cost to run on top of your fee?

Your cloud bill, paid directly to your provider and never marked up by us. We size it with you before you commit.

### Is Enterprise only for large companies?

No. It suits any health app or platform that wants the platform run, maintained and secured for it, whether that is because of scale or because its customers run a security review. One agreement covers the licence, the deployment and the support.

### We run a care programme or a clinical service. Does this pricing apply?

These plans are built for health apps and platforms. Care programmes and clinical services need more around the data, so we scope them with you, usually starting with a fixed-fee pilot. Clinical logic on top, such as alerts and triage, is built with you under an ISO 13485 quality system. See how it works for [care providers](https://openwearables.io/for/care-providers) and for [hospitals and telemedicine](https://openwearables.io/for/hospitals-telemedicine), or talk to us and we will walk you through it.

### Do you hold SOC 2 or ISO 27001?

No. The deployment runs inside your certified environment, which is how most teams answer this in their own audit.

### Will you sign a DPA? A BAA?

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 obtains the provider credentials?

You do, in your name, so the data relationship is between you and them. Approval is slow with some sources, so we start on day one.

### We use a hosted aggregator today. How hard is moving?

Usually a re-integration rather than a data migration, because you own the raw payloads from then on. It starts with an architecture audit.