Device Integration Overview

The AnyBio platform is device-agnostic by design. Whether the source is a chest strap, a ring, a smartwatch, a continuous glucose monitor, or a custom-built sensor, the same biosignal catalog and the same APIs apply. Device-specific protocols are handled inside the platform, so your application code stays the same as you add or swap hardware.

How it works

When a wearable connects, AnyBio normalizes its raw output into the platform's canonical wire format. From there:

• Waveforms (ECG, PPG, EDA, temperature traces) flow into the DSP pipeline, which produces feature series like heart rate and HRV.
• Discrete signals (device-reported HR, glucose, steps, sleep, calories, etc.) become observations directly.
• Both are queryable through the same endpoints documented in Biosignals.

Your application sees biosignals - not protocols, not characteristic UUIDs, not vendor binary formats.

Two integration paths

AnyBio supports two paths for getting a device onto the platform:

1. Standardized protocols. For devices that implement the Bluetooth SIG Heart Rate or other standard profiles, the platform integrates without per-vendor work. See Bluetooth SIG profiles.

2. Vendor-specific integrations. For devices with proprietary protocols, the platform ships per-vendor decoders that translate the device's binary format into the canonical wire format. We maintain integrations for several major wearable categories - see Supported Devices.

If you have a device that isn't yet supported, see Adding a Device for how integrations are added.

Where to go next