Open Wearables gives you a working foundation: unified wearable data, normalized across providers, self-hosted on your infrastructure. For many teams, that foundation is exactly what they need.
For others, the product requires more. A clinical platform needs scoring calibrated to patient populations, not general consumers. A corporate wellness tool needs deployment on a specific cloud with audit trail configuration. A performance app needs a readiness score that reflects the logic of their coaching methodology, not a generic algorithm.
Open Wearables is designed to be adapted. Here is what that looks like in practice.
What you can customize
Health scoring algorithms
The default Open Wearables scoring covers sleep and resilience. Every algorithm is published and auditable. You can read the code, understand the thresholds, and modify them.
Customization at this level means:
Adjusting population thresholds. A score calibrated for recreational athletes performs differently on sedentary office workers or post-surgical patients. The algorithm needs to know who it is scoring.
Weighting inputs differently. A longevity platform might weight HRV trends more heavily than acute strain. A clinical product might deprioritize exercise load entirely.
Building entirely new scores. Metabolic tracking, cognitive recovery, medication adherence signals. If the data exists in the platform, a score can be built on top of it.
This is not configuration. It is algorithm development, which is why Momentum's approach involves a dedicated health scientist from day one.
Provider integrations
Open Wearables ships with live integrations for all major wearable platforms. If your product needs a provider that is not on the list, a proprietary enterprise wearable, a legacy SDK, or a medical-grade device, Momentum builds the integration on top of the existing architecture. Custom integrations follow the same normalized schema as the rest of the platform.
Deployment and infrastructure
The open-source version runs on Docker Compose or Railway. Enterprise deployments go further: AWS, GCP, Azure, or on-premises, with HIPAA-eligible architecture, audit trail configuration, encryption, access controls, and network isolation. For teams with specific compliance requirements, Momentum handles the full infrastructure build and provides documentation for security reviews and BAAs.
The science behind custom scoring
Custom health scoring at Momentum is led by Anna Zych, PhD, an exercise physiologist with a research background in wearable data interpretation.
The practical implication: custom scores are grounded in the literature, not engineering intuition alone. When a threshold is set, there is a reason for it. When an algorithm weights HRV differently for a 60-year-old than a 25-year-old, that decision is documented and explainable.
For products in clinical or regulated contexts, that explainability matters. A score that cannot be justified to a medical review board is not deployable. Momentum's process produces scores that can be.
The six core score types available as custom implementations:
- Sleep score. Quality based on HRV, sleep stages, and resting heart rate, weighted against the user’s individual baseline.
- Recovery score. Overnight recovery measured against personal baselines using HRV trends and resting heart rate.
- Strain score. Cumulative cardiovascular load across training and daily activity, calibrated to individual capacity.
- Resilience score. Long-term adaptation to stress combining sleep quality, recovery trends, and HRV data.
- Readiness score. Daily actionable signal combining sleep, recovery, and strain into one number.
- Custom scores. Tailored algorithms for clinical populations, metabolic tracking, or cognitive recovery.
The customization process
Momentum works on customizations through a five-phase process.
Discovery (one week). Map your user population, data sources, and product goals. What devices do your users have? What does a good score mean in your context?
Scoping. Propose architecture, metrics, and algorithms with technical specifications. Define what gets built, how it integrates with your stack, and what the timeline looks like.
Development and integration. Build and deploy on your infrastructure. Custom scoring algorithms ship as API endpoints alongside the standard Open Wearables API.
Compliance and QA. Document methodology with auditable thresholds, ready for security reviews and regulatory scrutiny.
Launch and support. Thirty days of post-launch tuning with direct engineer access.
Enterprise support
The open-source tier is free forever and covers all wearable provider integrations, basic health scoring algorithms (sleep and resilience), REST API and webhooks, Docker Compose deployment, and community Discord support.
Enterprise support is where Momentum's team gets directly involved. The enterprise tier includes everything in the open-source plan plus:
- SLA-backed support with guaranteed response times
- Dedicated Slack channel with named engineers on your project
- HIPAA-eligible infrastructure with full compliance documentation
- BAA and GDPR documentation ready for your legal and security review
- Custom health score design and implementation by Anna Zych, PhD and Momentum’s engineering team
- Custom provider integrations for platforms not in the standard library
- Deployment on AWS, GCP, Azure, or on-premises
- Security questionnaire support for enterprise sales processes
- Quarterly architecture review as your product and user base grow
Momentum has delivered 220+ healthtech projects over 10 years. The team that built Open Wearables is the same team that works on enterprise customizations.
Starting points
Most engagements start in one of two places.
You have deployed Open Wearables and hit a ceiling. The default scoring does not fit your population. A provider you need is missing. Your compliance team has requirements the standard deployment does not cover.
You are evaluating Open Wearables for a new product. You want to understand what is possible before committing to the architecture. Momentum can scope what custom development would look like before you start.
In both cases the starting point is the same: a discovery call to map what you have, what you need, and what it takes to get there.
See the full pricing and support options or book a demo to talk through your use case.