Launched this week
Open Wearables
Open infrastructure for wearable-powered health products.
1.4K followers
Open infrastructure for wearable-powered health products.
1.4K followers
Build personalized health products with one API for every wearable. Access wearable data, open health scoring algorithms, and structured context your AI can reason with. Self-hosted, open-source, MIT licensed.
Three people in my Slack have tagged me in this today. The health data fragmentation problem is real and annoying, and the open-source angle means it might actually last longer than a VC-funded API startup.
Open Wearables
@sebastian_krol Thanks Sebastian, that's a good signal. The durability point is exactly why we went MIT. Even if Momentum disappeared tomorrow, the code keeps working: you fork it, maintain it, extend it. Different risk profile than betting your product on a Series A startup's runway and pricing strategy. Plenty of healthtech teams have been burned by aggregators getting acquired, pivoting, or hiking prices once dependency lock-in kicks in. Open source isn't a magic shield, but it removes that specific failure mode.
@sebastian_krol Three people? Those are still rookie numbers ;)
@sebastian_krol That kind of organic Slack/word-of-mouth signal is usually more telling than any launch post.
Open Wearables
@sebastian_krol three tags is a good sign
open source compounds - community keeps it alive, extends it, catches breaks. that's the whole advantage
Free, self-hosted, MIT license. Those three together in a health data tool is rare enough that I had to double-check the page. What's the long-term monetization plan, just curious?
Open Wearables
@dawid_stajszczyk Ha, fair reaction. The model is intentionally boring: Open Wearables stays free and MIT, Momentum sells services on top (enterprise deployment, custom scoring algorithms, AI/coaching layers, HIPAA support, SLA-backed maintenance).
@dawid_stajszczyk This campaing is one of the monetization plans ;)
@dawid_stajszczyk The "AI/coaching layers" part caught my eye as a running coach. The infrastructure being free and open is what makes it trustworthy and trustworthy infrastructure is exactly what premium coaching tools need to be built on.
Showed this to a founder friend building a longevity tracking app. She said the API coverage alone would have saved them six months of backend work. Congrats Momentum, timing on this feels right.
Open Wearables
@jakub_mikolajczyk1 Thanks Jakub, that's exactly the use case we built it for. Six months of OAuth flows, schema mapping, and provider edge cases is real time most teams don't have. If your friend wants to compare notes (or just complain about Garmin's docs), send her our way: Discord is the fastest path, or DM works too.
@jakub_mikolajczyk1 High five! And thanks!
Open Wearables
@jakub_mikolajczyk1 six months is honestly conservative for some teams - the provider integrations alone are brutal to maintain
tell her we're here if she wants to talk through the use case: https://discord.gg/openwearables
Velo
Open Wearables
@sourav_sanyal Three-device cross-talk is exactly where the unified model earns its keep. Quickstart is 5 minutes via Docker, would love to hear how it goes once you've plugged it in. One heads-up: CGM coverage is still in progress (Dexcom is on the roadmap, no committed date yet). Which CGM are you working with? If it's a high-demand one, that's useful signal for prioritization.
@sourav_sanyal haha, yeah that's amazing setup. Let us know on Discord, how it worked! :D
Open Wearables
@sourav_sanyal CGMs are already on our roadmap, the problem is they mostly don't provide real-time data via API (most have few minutes delay) but we will get there 😎
Slightly skeptical question: how stable is the Garmin and Oura API access? Those platforms have changed or restricted third-party access before. What happens to a self-hosted deployment if an upstream provider breaks the connection?
Open Wearables
@anton_zaporozhets1 Fair question. Both have official OAuth-based developer programs, and we've been shipping against them long enough to know the quirks (Garmin especially took real engineering time). If a provider changes something breaking: we patch, you pull the update. That's the OSS advantage. With a SaaS aggregator you wait for the vendor's roadmap and keep paying while you wait. No third-party integration is fully immune. The difference is how fast the fix lands and whether you can read the diff yourself.
@anton_zaporozhets1 Of course Open Wearables will propagate error (I suggest to use something like sentry to catch such exceptions), but you will still be able to connect with other providers, even if you will have broken connection with Garmin.
And I understand your concenr. In 2024 (or event 2025, don't remember) Garmin switched from OAuth v1 to Oauth v2 for example. It's a big change, but they didn't remove old endpoints which based on old OAuth standsrd. Of course it wasn't documented after the update to not tempt new users to use this.
Open Wearables
@joanna_samek Thanks Joanna! Honest answer: closer to "low maintenance" than "set and forget."
Once it's running, the main things are pulling updates when we ship a release, watching logs for errors, and occasional database housekeeping. Provider APIs change sometimes (Garmin tweaks something, Oura updates a field), we patch it, you pull the update. Security patches are mostly automated via Dependabot.
Realistically, a small team spends a few hours a month on it. If that sounds like more than you want to take on, Momentum offers managed deployments where we handle all of that for you.
Open Wearables
@joanna_samek the easiest option is to use one-click deployment on Railway so you don't have to worry about infrastructure so much. At least with relatively low scale this might be the best solution but once your user base grows it might become a bit pricey
HeyForm
This could help a lot of indie health apps that never get built because of infra friction. Good stuff.
Open Wearables
@itsluo That's the exact problem we keep seeing. Six to twelve months of OAuth integrations before you can ship anything meaningful kills most indie health projects before they start. Railway deploy in five minutes was a deliberate choice.
@itsluo Does the `indie health app` label fits to you company? :)