Garmin policy change

Move off your SaaS aggregator, onto your own keys.

Affected by the Garmin policy change? Open Wearables runs the connection in your own cloud, with no shared keys and no one in between.

Built on Open Wearables

  • Heart Monitor logo
  • Hundred logo
  • JustGains logo
  • Lifelong logo
  • MoveTogether logo
  • ROXFIT logo
  • Smarter Diagnostics logo
  • Suna logo
  • Yoboo logo

Who this is for

Your Garmin data runs through someone else's key.

When a SaaS aggregator connects many companies to Garmin through one registration, a policy change upstream reaches your users before it reaches you. These are the teams we hear from.

Your aggregator asked you to bring your own keys

Garmin's developer agreement does not allow passing keys or data to a third party without written permission. If you now hold your own credentials, the aggregator is one more party between you and data you can hold yourself.

Your users' Garmin data stopped arriving

With a shared registration, the connection your users depend on sits in someone else's agreement. With your own app, the relationship with Garmin is yours, and so is the fix.

It is not only Garmin

Strava's API agreement, in force since June, says a developer may not share its API token with any third party. Device makers are moving the same way: each company holds its own key.

Your customers ask who sits in the middle

Enterprise customers and security reviews ask where wearable data flows and who can reach it. With no aggregator in the path, the answer is your own cloud account.

What a migration means

Usually a re-integration rather than a data migration.

Your historical data stays where it is. What changes is where new data lands from the switch onwards: your own database, in your own account, under your own keys.

  • What changes

    Garmin and your other providers connect to your own deployment instead of the aggregator's. New data lands in your own database, on one standard schema.


    • Your cloud
    • Your keys
    • One schema
  • What stays the same

    Your users, their devices and your product. Most teams keep the aggregator running while the new path is validated, then cut over.


    • Parallel run
    • Cut over when ready
  • What you gain

    Provider apps registered in your name, no shared keys, raw payloads kept before standardisation, and source code you can read line by line.


    • No shared keys
    • Raw payloads
    • MIT license
  • What to plan for

    Each user authorises your app once, because their current connection belongs to the aggregator's app. Plan it as a short step in your product, not as a technical task.


    • One-time reconnect
    • Your consent screen

How it runs

From a SaaS aggregator to your own keys, in five steps.

Each step is something you can see working before the next one starts. Your aggregator keeps running until the last one.

  1. 01

    Start with an architecture audit.

    We look at the providers you use through the aggregator today, how your product reads the data and what has to keep working on day one. You leave with a written plan for your setup.

  2. 02

    Register your own Garmin app, and your other providers.

    Apply to the Garmin Connect Developer Program under your organisation's name, and to each other provider you use. Open Wearables does not replace Garmin's approval; the relationship is between you and Garmin. If you already hold your own keys, the slow part is behind you.

  3. 03

    Deploy next to the aggregator.

    Production and staging in your own cloud account and region, defined as infrastructure code in your repository. Either your team stands it up, or we do.

  4. 04

    Validate on real accounts.

    Connect test accounts and compare what comes back with what each provider's own app shows. Provider quirks surface here rather than after launch.

  5. 05

    Move users across, then switch the aggregator off.

    Users reconnect through your own consent screen, in batches you control. Where a provider offers history, it is requested as each user connects. When the new path is proven, the aggregator goes.

What stays yours

The deployment, the data and the keys stay in your account, whoever runs it

Sovereignty

Health data does not pass through an aggregator's cloud.

Residency

Your users' data stays in the region you chose, provable by pointing at an account.

Control

It runs in your cloud account, under your credentials. When we work on your system, we do it under a DPA you sign.

Your own reasons

If you stop working with us, the deployment and the data stay where they are. What you build on top of Open Wearables is yours.

Two ways to move

Run the move yourself, or have us stand it up in your cloud.

Same code, same cloud account, either way. What changes is how quickly it is live and who carries the work.

Self-host it

The full source under an MIT license, Docker Compose to start and infrastructure as code for production. Your engineers own the plan and the pace.

We stand it up in your cloud

Same architecture, same account, your keys. We deploy it, connect your providers, validate them on real accounts and stay on while your users move off the aggregator.

Connect the devices your users already own.

The coverage matrix lists what each source returns, so you can check it against the providers you use through your aggregator today rather than against a total.

Plan your move off the aggregator.

Tell us which providers you run through your aggregator today and how your product reads the data. We will say honestly what moving takes, and what it does not.

FAQ

Common questions.

We were affected by the Garmin policy change. What do we do first?

Apply for your own Garmin app under your organisation's name, because approval is the slowest step and nothing else depends on it. In parallel, stand up Open Wearables in your own cloud and validate your other providers. When your Garmin app is approved, add the keys and move users across.

Does Open Wearables give us Garmin access?

No. You apply to the Garmin Connect Developer Program yourself, and the relationship is between your organisation and Garmin. Open Wearables is the software that runs your approved connection alongside your other providers, in your own cloud account.

What does "no shared keys" mean?

Every provider app in your deployment is registered to your organisation, and its keys live only in your deployment. Nobody else's users run through them, and you do not run through anybody else's.

Is moving off an aggregator a data migration?

Usually a re-integration rather than a data migration. Your historical data stays where it is, and what changes is where new data lands from the switch onwards. Most teams run both in parallel while they validate, then cut over. It starts with an architecture audit.

Do our users have to reconnect their devices?

Yes, once. A connection belongs to the app that requested it, so moving from the aggregator's apps to apps registered in your name means each user authorises again. Treat it as a short step in your product with a clear reason.

What happens to the history we already have?

It stays where it is today. From the switch onwards, new data lands in your own database. Where a provider offers history, it is requested when each user connects to your app, and a full Apple Health export can be imported directly for users who want years of it.

We already have our own Garmin keys. What changes?

Then the slow part is behind you. Bring the client ID and secret, point the deployment at your callback, and the connection flow works from there.

How long does a migration take?

It depends on the providers you use and how long their credential approval takes, which is usually the slowest part. The architecture audit ends with a timeline for your setup rather than a general estimate.

Who supports us during and after the move?

Community support is on Discord and GitHub. Momentum, the team that builds Open Wearables, runs the Deployment and Integration services and Enterprise support with an SLA, a named on-call and tested upgrades. When we work on your system, we do it under a DPA you sign.

What if we stop working with you later?

Nothing stops. The platform sits in your cloud account, under your keys, built from infrastructure code in your repository, under an MIT license.

Is an aggregator ever the better choice?

Yes. A hosted service is faster to start and someone else runs it. If speed matters more than control and nobody is asking where the data sits, take the faster route. Compare alternatives.