The big picture
Elata has four layers. Each one has its own section in these docs.1. Devices
The sensors are things people already own:- A webcam can estimate pulse from tiny color changes in the skin (remote photoplethysmography, or rPPG).
- A consumer EEG headband, such as Muse 2 or Muse S, measures electrical activity from a few points on the scalp, and some models also have an optical (PPG) heart-rate sensor.
2. The Elata SDK
The Elata SDK is a set of open-source packages that connect to those devices and turn raw signals into usable measures such as heart rate, heart-rate variability, and EEG band powers. Processing runs in the browser, on the user’s device, using WebAssembly. Builders use the SDK so they don’t have to write signal processing from scratch.3. Apps
Builders combine the SDK with their own ideas: games you steer with focus or calm, breathwork guides that follow your heart rate, live dashboards, research tools. Apps are ordinary web apps. See Apps on Elata.4. Elata
Elata is where those apps live. It:- Reviews every release (an automated security scan plus a human moderator)
- Hosts each app in an isolated sandbox, so an app can’t see who the user is or touch their account
- Provides sign-in, purchases, subscriptions, and saved progress, so builders don’t have to
- Asks for consent in its own interface before any derived result leaves an app
Across all apps
Two things span every app on Elata:- Elata Points reward taking part: playing, reviewing, building, and inviting friends.
- The biometric Score is an optional, cross-app measure built only from derived session results, and only if the user opts in. See Privacy and consent.
How value moves
Details: Monetization.