Amatra is proud to contribute to the OpenWearables project
Wearable APIs are fragmented, brittle, and constantly changing. We're contributing to OpenWearables because we think the data layer should be open, maintained, and shared.
Amatra is proud to be a contributor to OpenWearables — an open-source project building a unified integration layer for wearable device data.
If you've tried to build on top of wearable APIs, you know how painful they are. Every device speaks a different language. Rate limits, auth flows, and schema changes vary by provider and shift without warning. Teams end up maintaining a patchwork of brittle adapters — time that should go into building products, not plumbing.
Why open source
The data layer for wearables shouldn't be a competitive moat. It should be infrastructure — stable, auditable, and maintained by the teams who depend on it most. OpenWearables gives every developer, sport scientist, and health team access to a single normalized schema across Whoop, Oura, Garmin, Apple Health, Polar, and more.
Amatra uses OpenWearables in production. That means every fix, adapter, and schema update we contribute is code that runs inside real deployments. We're not maintaining a fork in isolation — we're shipping upstream.
What this means for Amatra users
For teams using Amatra, this changes nothing day-to-day — wearable data has always flowed in automatically. What it does mean is that the integration layer underneath is open and inspectable, and that the community contributing to it now includes our engineering team.
If you want to self-host OpenWearables, the project is at github.com/the-momentum/open-wearables. If you'd rather we manage it for you, get in touch.