DMDeepMindex

For wearable manufacturers

License the measurement layer.

DeepMindex licenses its signal-quality assessment and brain–body modelling algorithms to manufacturers building EEG, PPG and multimodal wearables. Add interpretable attention, regulation and recovery outputs to your own hardware ecosystem — without building the measurement science from scratch or adopting our dashboard.

Licensed layer
Signal quality · brain–body modelling
Signals
EEG · PPG · respiration where available
Integration
Embedded, cloud or hybrid

The modelling approach draws on Dr. Junling Gao’s research at HKU and the DeepMindex deep-jhana research base. Read the publications.

The licensed layer

From raw signal to a measure you can ship.

Your device captures the signal. DeepMindex supplies the quality gate, the brain–body model and the output contract — so your team can build the product experience without rebuilding the science.

  1. 01

    Your hardware

    EEG, PPG and respiration signals from your device.

  2. 02

    Signal-quality gate

    Usable segments are separated from noise before a model runs.

  3. 03

    Brain–body model

    Neural and autonomic signals are read together against a baseline.

  4. 04

    Your product

    Attention, regulation and recovery outputs inside your experience.

What you can license

Measurement science, not another dashboard.

Three components, licensed separately or together, depending on what your hardware already captures and what your product needs to say.

01

Signal-quality assessment

A quality layer that decides whether a recording is fit to interpret before any measurement is produced. It assesses incoming EEG and PPG, flags poor contact and motion, and excludes unusable segments rather than averaging them into a result.

  • Per-session and per-segment quality assessment
  • Explicit exclusion rules and quality flags
  • Quality metadata returned alongside every output

02

Brain–body modelling

Models that read EEG and PPG together to estimate attention, physiological regulation and recovery. Outputs are measured against the individual's own baseline and carry an explicit statement of uncertainty.

  • Neural and autonomic signals modelled together
  • Individual baseline rather than population ranking
  • Uncertainty stated with every reading

03

A headless output layer

The licensed components can sit behind your existing app, firmware or cloud platform. There is no requirement to adopt the DeepMindex practitioner interface or send your users into a separate dashboard.

  • Outputs designed for your own product experience
  • No consumer checkout or per-seat model
  • Integration scoped to your data architecture

Engagement models

Three ways to license.

The right structure depends on whether the hardware is already in market, how many devices it covers and how much of the signal chain still needs engineering.

Commercial terms are scoped in a written licence. There is no public price list and no per-seat retail model.

An existing device or product line

Integration licence

License the agreed algorithm components for a defined device family. Integration, output specification and calibration are scoped to the signals your hardware already captures.

Multiple devices or generations

Product-line licence

Cover a family of devices under one agreement, with shared integration artefacts and a common validation and claims schedule across the range.

A new sensor configuration

Co-development licence

For new hardware, we scope a joint technical programme — signal access, evaluation, integration and validation — with licensing terms agreed before engineering begins.

How an engagement runs

Evaluate first. Integrate second.

We do not license an output on the strength of a form factor. The device is tested against the method before integration begins.

  1. 01

    Scope the fit

    Share the device, signal chain, intended use and target population. We confirm whether the hardware can supply what the models need, and which components belong in scope.

  2. 02

    Evaluate on your hardware

    Representative recordings from your device are run through the quality and modelling pipeline. You receive a written read on performance, limits and the gaps that remain.

  3. 03

    Integrate

    Choose an embedded, cloud or hybrid deployment. We agree the output schema, calibration approach, engineering responsibilities and support path.

  4. 04

    Validate and release

    The validation plan, permissible claims and licence terms are agreed before any output ships under your brand. Nothing is presented as validated until the evidence supports it.

What the licence covers

What you receive.

The licence is a defined technical package, not a promise that a model will work on every device.

  • A licence to the agreed algorithm components for defined products and markets
  • Integration documentation and the output specification
  • Signal-quality thresholds and calibration guidance
  • The validation report and permissible-claims schedule
  • A named technical contact through integration and launch

What we need from your hardware

The evaluation inputs.

A fit assessment needs more than a datasheet. We ask for the signals, the constraints and the intended use before quoting an integration.

  • Representative raw recordings from the target device and use conditions
  • Sensor placement, sampling rates, firmware and data-access constraints
  • Intended population, use context and the outputs you want to offer
  • Named technical and regulatory owners on your side
  • Written data-use and consent terms for evaluation data

Evidence before claims

A licence does not transfer a claim.

Validation is component-specific and hardware-specific. The licence states what has been validated, on which signals and populations, and what remains a candidate feature. An output is never presented as more certain than the evidence allows.

DeepMindex is an assessment and feedback platform. It is not a diagnostic instrument, and it does not diagnose, treat or cure any condition. Partners remain responsible for their own regulatory positioning and for the claims they make about their products.

Licensing commitments

  • Unvalidated features are labelled as candidate, not sold as established measures.
  • Evaluation data is used only under written data-use and consent terms.
  • No population norms are published as if they described an individual.
  • No ranking of practitioners, and no competitive or gamified scoring.

Common questions

What manufacturers ask.

If your question is not here, put it in the first conversation. We would rather answer it before a technical evaluation than after.

Do we have to use the DeepMindex dashboard?
No. The licensed layer is designed to sit behind your own product. Outputs can feed your app, firmware or cloud service; the practitioner and instructor surfaces are separate DeepMindex products.
Which devices are a fit?
The starting point is access to usable EEG and PPG signals, with respiration where available. Fit depends on sensor placement, sampling, signal access and the conditions in which the device is worn — not on the form factor alone.
Can we white-label the outputs?
Outputs can be presented inside your product experience under the agreed claims schedule. Branding, attribution and any DeepMindex endorsement are set in the licence rather than assumed.
Are the algorithms clinically validated?
DeepMindex is not a diagnostic instrument. Validation is assessed per component and per hardware configuration, and the licence states the current evidence and any remaining candidate status. We do not present provisional results as clinical proof.
What happens to data from our devices?
Evaluation data is used only for the agreed assessment, under written data-use and consent terms. Production data can remain in your architecture, with processing on-device or in your cloud where the integration allows.
Can you support a sensor configuration that does not exist yet?
That is the co-development route. We assess the signal chain first, then scope the engineering and validation work together. Licensing terms are agreed before the programme starts.

Device partnerships

Bring your hardware. We will scope the measurement layer.

Tell us what the device captures, how it is worn and what you want your users to see. We will come back with a technical fit assessment and a licensing outline.