Supported Devices
Wearables and biosignal sources AnyBio integrates today.
AnyBio supports a range of wearables across categories. New integrations are added regularly; if you don't see your device, contact us.
By signal type
The same device often emits multiple biosignals; the table below groups by what the platform receives, not by hardware category.
| Signal | Sources |
|---|---|
| ECG (waveform) | Single-lead chest straps and patches; rings and watches with ECG capability |
| PPG (waveform) | Optical sensors in rings, wristbands, and finger pulse oximeters |
| EDA | Wristbands and patches with electrodermal sensing |
| Body Temperature | Skin-temperature sensors in rings, watches, and patches |
| Heart Rate (device-reported) | Any device that exposes the Bluetooth SIG Heart Rate profile, plus vendor-specific HR streams |
| SpO2 | Pulse oximeters and watches with SpO2 capability |
| Glucose | Continuous glucose monitors via vendor APIs |
| Steps, Calories, Active Zone Minutes | Activity-tracking wearables and watches |
| Sleep | Sleep-staging wearables and rings |
Categories of integration
Three broad categories of wearable integrate cleanly today:
- Direct BLE wearables that stream waveform or HR data over Bluetooth. The BioSDK handles discovery, connection, and the protocol translation; your application code stays at the biosignal layer.
- Cloud-to-cloud sources like continuous glucose monitors and aggregated activity data, which arrive via vendor APIs rather than direct BLE.
- Standards-based devices implementing public profiles like Bluetooth SIG Heart Rate. These work without any per-vendor code.
Active integrations
We currently maintain integrations across several major wearable categories. For specific device names, model numbers, or to confirm whether a particular wearable is supported in your project, contact us - we keep the per-device list current with our partners directly rather than in public docs.
What "supported" means
A supported device gets:
- Real-time streaming through the BioSDK or platform APIs.
- Automatic translation from the device's native data format to the AnyBio biosignal catalog.
- Per-biosignal validation (range checks, quality mask propagation).
- DSP processing for waveforms (HR/HRV from ECG; HR/PRV from PPG).
- FHIR observation export for clinically relevant biosignals.
It does not require any device-specific code in your application. Swap hardware, keep the integration.