Everything runs in your own cloud account. Run the core yourself for free, or put our team behind it with Pro or Enterprise.
For teams building their first wearable features. You run the open-source platform yourself.
$0Forever
For products in production. Licensed modules, with our engineers behind your deployment.
From$999a month, per deployment
Everything in Core, plus
The Pro modules, in your deployment
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
A care provider, hospital or telemedicine platform? See the three paths
Platform, Pro modules, support, services and security, side by side.
The full picture
You run it yourself.
$0Self-hostedScores, insights and cleaner data.
From $999Per month, per deploymentRun, maintained and secured at scale.
CustomAnnual agreementIs Open Wearables for you
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.
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 moreRun 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 moreWearable 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 moreThe team behind it
A healthcare software company building health data software since 2016. The engineers who built Open Wearables deploy it and build on it for clients.
FAQ
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.
From $999 a month per production deployment, staging included. It includes health scores, the health agent, medical-grade integrations and observability. The 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.
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.
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.
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.
Your cloud bill, paid directly to your provider and never marked up by us. We size it with you before you commit.
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.
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 and for hospitals and telemedicine, or talk to us and we will walk you through it.
No. The deployment runs inside your certified environment, which is how most teams answer this in their own audit.
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.
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.
Usually a re-integration rather than a data migration, because you own the raw payloads from then on. It starts with an architecture audit.
