Unlike health trackers with locked-down APIs, Aidlab ships with a free SDK [1] across 6+ platforms so you can just pip install aidlabsdk or flutter pub add aidlab_sdk or whatever platform (even Unity), and start streaming raw health data and events in real time with simple didReceive*(timestamp, value) callbacks.

Currently, we are exposing 13 data types including raw ECG, cough/snoring, motion, raw respiration, skin temperature, bodyweight reps, body position, and 20 high-level stats like stress or readiness through the API.

The most common questions I got are:

1) "how is it better than my smartwatch?"

2) "why we built it?"

Chest-mounted wearables are considered the gold standard for physiological measurements. For example, whenever Apple validates their watch, they benchmark against chest straps [2], as some signals can only be reliably measured (or measured at all!) near the heart including continuous ECG, true respiration (based on lung volume changes) or body position/orientation.

As for the second question: the problem for us was that smartwatches were too simple and the data too inaccurate, while advanced medical devices were too pricey or too complicated. We found a sweet spot between accuracy and accessibility - Aidlab delivers medical-grade signals without the hospital-level complexity. As "medical-grade" is a bold statement, we’ve published validation papers comparing Aidlab’s performance with other certified medical devices [3].

Today Aidlab is already a pretty mature concept. We've been building Aidlab for 2 years, shipped our first version in 2020, we got our first clients including Boeing/Jeppesen (monitoring pilots’ bio-signals during tests&training).

Now we're about to release Aidlab 2 [4] - with additional signals like EDA and GPS, and a bunch of new features, including on-device ML (we've trained a few small LSTM models running inference with TensorFlow Lite for Micro). The cool part is that we've built a custom shell on top of FreeRTOS, letting anyone invoke POSIX-like commands directly on the device, for example:

timeout 10 temperature --sampling-rate 1 | tee /data/temperature.csv | tail -n 5

The biggest breakthrough for us was realizing that cloud-based processing was the wrong approach. In the beginning, we pushed most of the computation to the cloud - it seemed natural, but turned out to be slow, costly, and devs didn't want it ("hey, is there a way to use your product without cloud?"). For example, our ECG analysis pipeline used to send raw data to an external microservice, processing it in 30-minute chunks through Bull queues. A 24-hour Holter analysis could spawn 100k+ event objects and take significant time to complete. Now we're doing everything we can to move computation to the edge. In an ideal world, the cloud wouldn't store or process anything - just receive already-analyzed, privacy-preserving results straight from the device.

Another lesson: don't hand-solder prototypes at 3 a.m. to save money -> please pay professionals to assemble PCBs.

We decided to showcase this now for three reasons:

- health feels more relevant than ever with the rise of longevity research and biohacking,

- we are close to finalizing Aidlab 2,

- and I am super curious to see if anyone here finds it useful!

If you'd like to check the quality of Aidlab for yourself, we are publishing free datasets every week during different activities [5].

[1] https://github.com/Aidlab

[2] https://www.apple.com/health/pdf/Heart_Rate_Calorimetry_Acti...

[3] https://aidlab.com/validation

[4] https://aidlab.com/aidlab-2

[5] https://aidlab.com/datasets