Hardware Partnership Programme

Connect your device.
Let's build it together.

BCILattice is built for live signal capture and offline recording replay across EEG, fNIRS, and EMG. We're actively looking for hardware manufacturers to partner with, and we'll do the integration work together.

EEG · fNIRS · EMG

signal modalities supported

Local-first

all processing on device

Open

driver architecture

Built for every major BCI modality

BCILattice's signal pipeline is designed around EEG, fNIRS, and EMG. If your device captures one of these signals, BCILattice is built to work with it.

EEG Systems

OpenBCI, Emotiv, Muse, BrainProducts, g.tec, Neuroelectrics, ANT Neuro, Cognionics

fNIRS Devices

NIRx, Artinis, Hitachi, Shimadzu, fNIR Devices, Gowerlabs, SEEQ

EMG / EXG

Delsys, OttoBock, BioSignal Group, Noraxon, Cometa, Quattro

Hybrid & Novel

EEG+fNIRS combos, dry electrode arrays, wearable neural interfaces, consumer headsets

From your device to a full research workflow

Your hardware captures the signal. BCILattice handles everything from there, live streaming, recording, preprocessing, ML, and collaboration, all in one desktop app.

Live signal capture

BCILattice is built to stream directly from devices via LSL, USB, or Bluetooth, real-time display, marker injection, and session recording included

Recording replay

Saved sessions load back into the same pipeline, offline analysis, re-epoching, and model re-training from any prior recording

Full signal pipeline

Filtering, referencing, artefact rejection, epoching, your raw stream flows straight into research-grade preprocessing

Local-first ML

All training runs locally on the researcher's machine, no data ever leaves without their explicit action

Growing community

BCILattice is actively growing its user base, hardware partners who integrate early will be among the first devices researchers reach for

Compliance ready

HIPAA / GDPR-aware data handling built in, regulated labs can use your device without additional compliance setup

Three ways to work together

Whether you want to contribute a driver independently or build something deeper, we're open to all of it.

Community Driver

Contribute an open-source Python driver for your device. We review the code together and integrate it into BCILattice, no formal agreement required.

  • Open a pull request against BCILattice, we co-review it
  • Driver loads into the live device list on merge
  • Access to BCILattice's real-time signal ingestion API
  • Listed in docs as a community-supported device
View Driver API
Most common

Certified Partner

We work with your team directly, build the driver together, write the setup documentation, and officially list your device as BCILattice-supported.

  • Direct engineering collaboration on your integration
  • Co-authored device setup guide in our docs
  • Listed as an officially supported device on release
  • Priority support for issues reported by researchers
  • Joint announcement when your device ships
Get in touch

Deep Collaboration

A closer working relationship, we build native, first-class support for your hardware together: live streaming, trigger injection, impedance UI, and more.

  • Everything in Certified Partner
  • Native streaming integration (LSL, proprietary SDKs)
  • Custom impedance and electrode map visualisation
  • Co-developed features tailored to your hardware
  • Ongoing compatibility commitment across BCILattice updates
Start a conversation

How a hardware integration works

01

Reach out

Email us your device name and a brief description of your SDK. We'll get back to you within a few days to discuss how to proceed.

02

Build the driver together

We collaborate on the Python driver using BCILattice's signal ingestion API. You know your hardware, we know the pipeline.

03

Test and document

We test the integration end-to-end together and co-write the setup guide so researchers can get your device running in minutes.

04

Ship it

Your device is listed in BCILattice as supported. Every researcher who installs BCILattice can discover and connect to it.

Interested in integrating your device?

Send us your device name and a brief description of your SDK, we'll get back to you and figure out the best way to work together.