Skip to main content

​
Checklist

1

An Elata account

Sign in at app.elata.bio. You can sign in with a social login or connect an existing wallet.
2

A registration fee

Registering an app name costs a small one-time fee in USDC. The current amount is shown in the wizard.
3

An app that uses an Elata sensor SDK

Uploads are rejected if no Elata SDK usage is detected. Use camera rPPG (rppg-web), EEG over Bluetooth (eeg-web + eeg-web-ble), or headband PPG (ppg-web, which runs on the EEG transport).
4

A static web build

A .zip with index.html at its root (or a single .html file). Asset paths must be relative, because apps are served under a sub-path. See Upload and hosting.
5

A version

Add an elata.json so Elata shows v1.2.3 instead of a release number.
6

Listing assets

An app icon and a header image are required to submit. Screenshots and an extended description are recommended. See App listing.

​
SDK usage check

Elata looks for real calls into the Elata SDK in your bundle, for example createRppgSession(...) from rppg-web, or initEegWasm(...) and BleTransport from the EEG packages, along with the packaged WASM files. Importing a package without using it is not enough.
The templates from npm create @elata-biosciences/elata-demo already pass this check. If you integrate the SDK by hand, keep the packaged .wasm files in your build output.

​
Things your app must not do

Apps run in a sandbox. Reviews and the automated scan reject apps that:
  • start wallet transactions, signatures, or approvals outside Elata’s own checkout
  • send raw camera frames, microphone audio, or raw biosignals off the device
  • try to reach the parent page, its cookies, or storage, or escape the sandbox
  • impersonate another app, developer, or service
The full list is in Review and policy.

​
Next

Publish Your App

Walk through the wizard

elata.json

The app manifest