Comparison Tool
Wearable health data aggregator chooser: Terra, ROOK, Junction, Spike, Thryve, Sahha, Open Wearables, Validic
There is no single best aggregator: the right one depends on which sources you need, how you want to be billed and what compliance you must show. Of the 8 here, all publish a starting price, 7 document a BAA (on which plan varies), 4 say where data is stored or let you choose (Terra, Junction, Thryve and Open Wearables), and only Open Wearables is software you host yourself. Tick what you need and the table reorders by what each vendor's own pages document. Every cell quotes its source, each quote re-found in its live source on 2026-11-05; "not stated" means the pages read do not say, not that a feature is missing.
| Aggregator | Sources claimed | Apple Health / Health Connect SDK | Garmin | Continuous glucose | Your own developer accounts | How it bills | Published price | Free way to build | Webhooks | Signed webhooks | BAA (HIPAA) | Where data is stored | Self-host | Lab data | MCP server | Company changes |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Junction (formerly Vital) | 300+ wearables and devices Source quote
| DocumentedMobile SDKs for Apple HealthKit and Android Health Connect, native, React Native and Flutter 2 source quotes
| Not statedNot stated in the passages read | Not statedNot stated in the passages read | Some OAuth providers are unavailable unless you Bring Your Own OAuth; custom OAuth credentials are listed under Enterprise 2 source quotes
| Launch: one flat monthly fee for 1-500 connected users; Enterprise is custom and billed annually 2 source quotes
| DocumentedLaunch at a flat $300 a month, billed monthly with no annual contract 2 source quotes
| DocumentedThe sandbox and developer docs are free Source quote
| DocumentedPushes wearable data as webhook events as soon as they are discovered Source quote
| Not statedNot stated in the passages read | DocumentedThe signed BAA is part of Enterprise; every plan handles data in a HIPAA-compliant way 2 source quotes
| DocumentedEach team is tied to an EU or US region, which dictates where data is stored 2 source quotes
| Not statedNot stated in the passages read | DocumentedLab testing across all 50 US states, on Enterprise 2 source quotes
| Not statedNot stated in the passages read | Unveiled its new brand, Junction, in a post dated March 11, 2025 2 source quotes
|
| Open Wearables | Open-source platform that connects wearables and health apps and serves one schema through one REST API Source quote
| DocumentedSDKs read Apple Health, Samsung Health and Health Connect on the device and upload to your deployment Source quote
| DocumentedGarmin, once you apply to the Garmin Developer Program Source quote
| NoDexcom is not in the open-source project today; continuous glucose is on its roadmap Source quote
| Your own app with every cloud provider; approval takes from days to months 2 source quotes
| Core is free software you run yourself; Pro is priced per deployment 2 source quotes
| DocumentedCore $0 forever; Pro from $999 a month per deployment 2 source quotes
| DocumentedSelf-hosted Core under the MIT license, $0 per user Source quote
| DocumentedOutgoing webhooks, signed and retried, off by default 2 source quotes
| DocumentedEach outgoing event is signed Source quote
| DocumentedA BAA comes with Enterprise, where your cloud provider and scope support it Source quote
| DocumentedRuns in your own cloud account, in the region you chose Source quote
| DocumentedMIT-licensed; you host it, and there is no hosted version 2 source quotes
| Not statedNot stated in the passages read | Not stated in the passages read | |
| ROOK | 400+ wearables and health data sources in its docs; its integrations page counts 72 data sources, 59 of them indirect, and 500+ devices 3 source quotes
| DocumentedMobile SDKs for Apple Health, Health Connect and Samsung Health Source quote
| DocumentedGarmin is a direct API-based integration, like Fitbit Source quote
| DocumentedDexcom, through a developer account your organization provisions Source quote
| Your own accounts for Dexcom, Samsung Health, Strava and WHOOP, which can take several weeks 2 source quotes
| By plan and number of active users; past a plan's limit, billing adjusts based on usage 2 source quotes
| DocumentedCore $399 a month for up to 750 active users, Core+ $999 for 5,000, Business $1,999 for 15,000 3 source quotes
| Not statedSandbox access before Production; the passages read do not say whether it costs anything Source quote
| DocumentedWebhooks or API queries; on Core the Notification Webhook is a $99 add-on 2 source quotes
| Not statedNot stated in the passages read | DocumentedSigns BAAs with covered entities, when a BAA applies to the relationship 2 source quotes
| Not statedNot stated in the passages read | Not statedNot stated in the passages read | DocumentedLab Data API: PDF and image lab reports to LOINC-coded biomarkers with FHIR R4 output Source quote
| Not statedNot stated in the passages read | Not stated in the passages read |
| Sahha | 800+ devices across 165 integrations, mostly arriving on-device through Apple Health or Health Connect, plus the phone itself as a passive sensor 3 source quotes
| DocumentedA direct Garmin cloud integration in public beta, Sandbox only, with approval required 2 source quotes
| Not statedNot stated in the passages read | Its beta cloud integrations use an app you create with the provider Source quote
| DocumentedStarter $299 a month billed annually with 1,000 users; Pro $1,499 a month billed annually | Documented25 free development users in sandbox, and every plan starts with a 30-day free trial | DocumentedREST API and webhooks, with deliveries capped per day by plan | DocumentedAn HMAC-SHA256 of the raw body, compared with the signature header Source quote
| DocumentedA DPA on every plan; a BAA from Pro Source quote
| Not statedNot stated in the passages read | Not statedNot stated in the passages read | Not statedNot stated in the passages read | Not statedNot stated in the passages read | Not stated in the passages read | ||
| Spike | 500+ wearables and IoT sensors on its homepage; 40+ providers and 500+ devices on its pricing page 2 source quotes
| DocumentedAn SDK for Apple Health, Health Connect and Samsung Health Source quote
| DocumentedGarmin is named among providers whose users grant consent before Spike reads their data Source quote
| DocumentedDexcom and Freestyle Libre are on its integrations page 2 source quotes
| Not stated in the passages read | Calls its pricing usage-driven Source quote
| DocumentedSandbox starts from $450 a month; each plan is bought through Book a demo 2 source quotes
| Not statedNot stated in the passages read | DocumentedWebhook events, each one signed Source quote
| DocumentedHMAC-SHA256 signature in an X-Body-Signature header Source quote
| Not statedNot stated in the passages read | Not statedNot stated in the passages read | Not statedNot stated in the passages read | DocumentedLab Reports API: OCR of PDF, JPEG or PNG reports up to 10MB, with LOINC codes 2 source quotes
| DocumentedSpike MCP connects wearable, IoT, lab and nutrition data to your LLM Source quote
| Its site carries the banner "Raintree Systems Acquires Spike Technologies" Source quote
|
| Terra | 500+ providers through one API, among them Garmin, Fitbit, Apple Health, Oura, WHOOP and Strava; its setup docs say over 150 data sources 2 source quotes
| DocumentedPhone health stores have no cloud API, so your app reads them with the Terra SDK and sends the data to Terra Source quote
| DocumentedGarmin data flows through Terra's own long-standing partner integration Source quote
| DocumentedDexcom is in its integrations table, periodically fetched Source quote
| Terra manages data sources' API keys; WHOOP, Dexcom, Huawei, Strava and Virtuagym need special processes first 2 source quotes
| Credits: 200 a month per connected data source per end user; the first 400 events per source each month are free Source quote
| DocumentedFrom $399 a month billed annually or $499 billed monthly, with 100,000 credits a month Source quote
| Not statedNot stated in the passages read | DocumentedDelivers to webhooks, SQL databases, Supabase, cloud storage, queues, MongoDB and Firestore Source quote
| DocumentedEvery webhook carries an HMAC-based signature header Source quote
| DocumentedA signed BAA is listed on Enterprise; Terra says it is HIPAA compliant 2 source quotes
| DocumentedEnterprise lists a dedicated instance in a localized area Source quote
| Not statedNot stated in the passages read | DocumentedBlood and DNA tests through home kits, mobile phlebotomy or lab walk-ins, in the US and the UK, results in FHIR 3 source quotes
| DocumentedAn MCP server through its AI Interface Source quote
| Not stated in the passages read |
| Thryve | Over 500 wearables and health data ecosystems, including Apple HealthKit, Fitbit, Garmin and Samsung Health Source quote
| DocumentedNative SDKs for Apple Health and Health Connect 2 source quotes
| DocumentedGarmin is in its data-sources table with a shared OAuth client Source quote
| DocumentedDexcom, with your own OAuth client, since Thryve has no shared one 2 source quotes
| Your own OAuth client where Thryve has no shared one, as for Dexcom, WHOOP and Google Health 4 source quotes
| Users included per plan, then €0.50 per additional user on Start Up 2 source quotes
| DocumentedStart Up from €499 a month with 500 users; Scale Up from €1,000 a month for startups under ten years old 4 source quotes
| DocumentedPushes new and updated user data to your system through webhooks Source quote
| Not statedNot stated in the passages read | DocumentedBAAs and DPAs are standard on every plan Source quote
| DocumentedAll data processed and stored by Thryve is hosted in Germany Source quote
| Not statedNot stated in the passages read | Not statedNot stated in the passages read | Not statedNot stated in the passages read | Not stated in the passages read | |
| Validic | 700+ devices normalized into one standard Source quote
| DocumentedMobile SDK for iOS and Android: full access on Enterprise, coming soon on the other plans Source quote
| Not statedNot stated in the passages read | Not statedNot stated in the passages read | Samsung Health approval requires a direct relationship with Samsung, which is not accepting new applications Source quote
| A free Developer plan; Enterprise pricing is negotiated 2 source quotes
| DocumentedInform Developer plan free for 5 users and 5 cloud integrations; Enterprise negotiated 2 source quotes
| DocumentedFree for 5 users, with no contract and no credit card 2 source quotes
| Not statedA Streaming API (server-sent events) and a REST API preview; webhooks are not mentioned Source quote
| Not statedNot stated in the passages read | DocumentedBAA available for Enterprise customers Source quote
| Not statedNot stated in the passages read | Not statedNot stated in the passages read | Not statedNot stated in the passages read | Not statedNot stated in the passages read | ChartSpan announced the completed acquisition of Validic on June 22, 2026 2 source quotes
|
Trade-offs by use case
No aggregator wins every case. Each case below lists what every vendor's cell says for the column that decides it, and names the vendors whose pages do not say. The quotes behind each line are in the table above.
Your users mostly carry iPhones and Android phones
Apple Health and Health Connect keep data on the phone, so an aggregator reaches them through its own mobile SDK. What differs is which SDKs ship and on which plan.
- Terra: Phone health stores have no cloud API, so your app reads them with the Terra SDK and sends the data to Terra
- ROOK: Mobile SDKs for Apple Health, Health Connect and Samsung Health
- Junction: Mobile SDKs for Apple HealthKit and Android Health Connect, native, React Native and Flutter
- Spike: An SDK for Apple Health, Health Connect and Samsung Health
- Thryve: Native SDKs for Apple Health and Health Connect
- Sahha: One SDK; sources arrive on-device through Apple Health or Health Connect
- Open Wearables: SDKs read Apple Health, Samsung Health and Health Connect on the device and upload to your deployment
- Validic: Mobile SDK for iOS and Android: full access on Enterprise, coming soon on the other plans
You want to build before you pay
A trial ends; a free plan or a self-hosted core does not. Check which one a vendor offers before you plan a pilot around it.
- Junction: The sandbox and developer docs are free
- Thryve: A 14-day free trial
- Sahha: 25 free development users in sandbox, and every plan starts with a 30-day free trial
- Open Wearables: Self-hosted Core under the MIT license, $0 per user
- Validic: Free for 5 users, with no contract and no credit card
Not stated in the pages read: Terra, ROOK, Spike.
You build for a covered entity or a business associate
Which plan carries the BAA matters as much as whether there is one: it sets your real entry price.
- Terra: A signed BAA is listed on Enterprise; Terra says it is HIPAA compliant
- ROOK: Signs BAAs with covered entities, when a BAA applies to the relationship
- Junction: The signed BAA is part of Enterprise; every plan handles data in a HIPAA-compliant way
- Thryve: BAAs and DPAs are standard on every plan
- Sahha: A DPA on every plan; a BAA from Pro
- Open Wearables: A BAA comes with Enterprise, where your cloud provider and scope support it
- Validic: BAA available for Enterprise customers
Not stated in the pages read: Spike.
Your data has to stay in one region
A stated hosting country, a region you pick per team and a deployment in your own cloud are different promises.
- Terra: Enterprise lists a dedicated instance in a localized area
- Junction: Each team is tied to an EU or US region, which dictates where data is stored
- Thryve: All data processed and stored by Thryve is hosted in Germany
- Open Wearables: Runs in your own cloud account, in the region you chose
Not stated in the pages read: ROOK, Spike, Sahha, Validic.
You want to own the stack
Self-hosting trades the vendor's managed provider credentials for your own developer account with every provider; read the own-accounts column with this one.
- Open Wearables: MIT-licensed; you host it, and there is no hosted version
Not stated in the pages read: Terra, ROOK, Junction, Spike, Thryve, Sahha, Validic.
You need continuous glucose
Glucose providers are where aggregators most often need your own developer account, so read the own-accounts column with this one too.
- Terra: Dexcom is in its integrations table, periodically fetched
- ROOK: Dexcom, through a developer account your organization provisions
- Spike: Dexcom and Freestyle Libre are on its integrations page
- Thryve: Dexcom, with your own OAuth client, since Thryve has no shared one
Not stated in the pages read: Junction, Sahha, Open Wearables, Validic.
You want lab results beside wearable data
Some vendors order tests, others parse lab reports your users upload. They are different products, billed differently.
- Terra: Blood and DNA tests through home kits, mobile phlebotomy or lab walk-ins, in the US and the UK, results in FHIR
- ROOK: Lab Data API: PDF and image lab reports to LOINC-coded biomarkers with FHIR R4 output
- Junction: Lab testing across all 50 US states, on Enterprise
- Spike: Lab Reports API: OCR of PDF, JPEG or PNG reports up to 10MB, with LOINC codes
Not stated in the pages read: Thryve, Sahha, Open Wearables, Validic.
You are wiring health data into an AI agent
An MCP server saves writing a retrieval layer; it does not change which sources the vendor can reach.
- Terra: An MCP server through its AI Interface
- Spike: Spike MCP connects wearable, IoT, lab and nutrition data to your LLM
- Open Wearables: An MCP server in Core
Not stated in the pages read: ROOK, Junction, Thryve, Sahha, Validic.
How to choose: questions
Is there a best wearable health data aggregator for developers?
No single one: each documents a different mix of sources, billing, compliance and hosting, so decide by use case. If your users are mostly on phones, compare the mobile SDKs. For HIPAA work, compare which plan carries the BAA. For a fixed data region, Terra, Junction, Thryve and Open Wearables state one. To own the stack, Open Wearables is self-hosted. The chooser on this page orders all 8 by what their own pages document for the needs you tick, and quotes the page behind every cell.
Which aggregators can I build on without paying first?
Junction: The sandbox and developer docs are free. Thryve: A 14-day free trial. Sahha: 25 free development users in sandbox, and every plan starts with a 30-day free trial. Open Wearables: Self-hosted Core under the MIT license, $0 per user. Validic: Free for 5 users, with no contract and no credit card. That is 5 of the 8; for Terra, ROOK and Spike the pages read do not state a free plan, free sandbox or free trial.
Which aggregators say where my users' data is stored?
Terra: Enterprise lists a dedicated instance in a localized area. Junction: Each team is tied to an EU or US region, which dictates where data is stored. Thryve: All data processed and stored by Thryve is hosted in Germany. Open Wearables: Runs in your own cloud account, in the region you chose. For ROOK, Spike, Sahha and Validic, the pages read do not say.
Can I self-host a wearable data aggregator?
Open Wearables: MIT-licensed; you host it, and there is no hosted version. The trade-off is credentials. Open Wearables on your own accounts: Your own app with every cloud provider; approval takes from days to months.
Which aggregators publish a starting price?
All of the 8. Terra: From $399 a month billed annually or $499 billed monthly, with 100,000 credits a month. ROOK: Core $399 a month for up to 750 active users, Core+ $999 for 5,000, Business $1,999 for 15,000. Junction: Launch at a flat $300 a month, billed monthly with no annual contract. Spike: Sandbox starts from $450 a month; each plan is bought through Book a demo. Thryve: Start Up from €499 a month with 500 users; Scale Up from €1,000 a month for startups under ten years old. Sahha: Starter $299 a month billed annually with 1,000 users; Pro $1,499 a month billed annually. Open Wearables: Core $0 forever; Pro from $999 a month per deployment. Validic: Inform Developer plan free for 5 users and 5 cloud integrations; Enterprise negotiated. Spike and Validic still route part of the purchase through sales. The billing units differ (per connected source, per active user, per deployment), so compare them at your own user count.
Prices at your own user count: health data aggregator pricing. Head to head: Terra vs ROOK, Terra vs Spike, Terra vs Thryve, Terra vs Sahha, Terra vs Open Wearables, Terra vs Junction (Vital) and ROOK vs Spike. Replacing one: Terra alternatives.
How this matrix is built
- Every cell cites rows of ops/sources/evidence/fitness-apis-health-data-aggregator-apis.json, the evidence the roundup page was written from, or of the evidence files of the site's pages on the same vendors (compare-terra-vs-open-wearables.json, pricing-health-data-aggregator-pricing.json, alternatives-rook-alternatives.json, compare-terra-vs-rook.json, pricing-rook-api-pricing.json, pricing-junction-api-pricing.json, compare-rook-vs-spike.json, compare-terra-vs-spike.json, compare-terra-vs-thryve.json, pricing-sahha-api-pricing.json, compare-terra-vs-sahha.json), and the page prints each row's verbatim quote under the cell. No fact here is new.
- Every quote in those files was found again in its live source by the source-quotes workflow (run 42085175043) on 2026-11-05, and each vendor's cells may only quote that vendor's own sites.
- "Not stated" means the vendor passages read do not say. It is not a "no": a cell says no only where a quoted passage does.
- The order after you tick needs counts documented features only. It ranks documentation, not products, and nothing on this page is a recommendation.
The full write-up, with the context these cells leave out: Wearable health data aggregator APIs compared.
Next step
Turning this into a choice of API: