More
About PiEEGContactCareersPartnershipPiEEG StoreOculomotor & Pupillometry BenchOptical Physiological BenchPiEEG XRAura VRoctoWatch (Garmin)BodyPress MobileBrowser Extension1020 AcademybioIDEBio-Pen (Live Lab)octoBridgeSignal LabBCI guidesTutorialsExamples & DemosSupportOpen Ideas & VolunteersOctopus-16 FirmwareExplore all pages16 open-source ideas you can pick up today and build independently on MIT-licensed PiEEG hardware and software. Your project, your repository, your name on it.
PiEEG Ltd is a UK company and does not take on volunteers, interns or unpaid workers. The ideas below are shared publicly as inspiration. Anyone can work on them, on their own initiative, for their own open-source project. You do not work for PiEEG, and PiEEG does not assign, supervise or direct your work.
Choose one below, or invent your own. No application, no sign-up.
Create a repository under your own account. Fork or reuse our MIT-licensed code.
Work at your own pace. Publish code, results and write-ups openly.
Post it on Discord. We may choose to feature notable projects.
Starting points, not specifications. Change the scope, combine ideas, or take them somewhere we never thought of.
For PCB designers and analog / mixed-signal engineers.
Measure input-referred noise, CMRR and channel crosstalk of an open PiEEG board using your own setup, and publish the method so others can repeat it.
Possible outcome: A public report + scripts in your own repository.
Design an open active-electrode (buffer at the electrode) board that plugs into an existing open-source EEG front end, and compare it with passive electrodes.
Possible outcome: Open KiCad files, BOM and a comparison write-up.
How much do cable length, twisting and shielding change mains interference? Run simple, repeatable experiments and document the results with photos.
Possible outcome: A practical guide others can follow.
Design a printable case, battery holder or headband mount for an open PiEEG-family board. Share STL + source files under an open licence.
Possible outcome: Files on your GitHub or Thingiverse.
For data scientists, ML students and DSP engineers.
Compare classic and ML methods for removing blinks, jaw clenches and motion artifacts from low-channel EEG, using public datasets or your own recordings.
Possible outcome: A notebook + short paper-style write-up.
Build an open, real-time left/right motor-imagery classifier that runs on a Raspberry Pi or laptop and streams from an open EEG board.
Possible outcome: An open-source library with accuracy and latency numbers.
A web-based SSVEP speller with flicker targets and CCA detection that works with an open EEG data stream.
Possible outcome: A live demo + source code.
Can models pre-trained on large public EEG datasets be adapted to 8 or 16 consumer-grade channels? A good topic for a thesis or a preprint.
Possible outcome: Code, model weights and a preprint (e.g. arXiv).
For developers who like building things people use.
Write and maintain a bridge that streams open PiEEG data into Lab Streaming Layer or another common neuro-tool, so it works with existing research software.
Possible outcome: A package published under your name.
Create a new visualisation or neurofeedback mini-game for the open-source dashboard and offer it as a pull request.
Possible outcome: A merged PR or your own fork.
Extend the open brain-state browser extension: focus timers, reading-load indicators or accessibility helpers.
Possible outcome: A fork or plugin in your repository.
For teachers, students and science communicators.
Translate an open README or tutorial into your language so more students around the world can start with neurotech.
Possible outcome: A pull request or a translated guide on your own site.
Write a 3–5 session school or university lab course on biosignals (EMG, ECG, EEG basics) built on open-source tools, with safety notes included.
Possible outcome: Open teaching materials (CC-BY licence suggested).
Make a short, accurate video about how EEG amplifiers work, what alpha waves are, or how to read a spectrum — on your own channel.
Possible outcome: A video you own and publish.
For researchers who want reproducible, public results.
Replicate a well-known effect (alpha blocking, P300, SSVEP) with low-cost open hardware and publish data and code. Recording other people requires your own institution's ethics approval.
Possible outcome: An open dataset + analysis on OSF or Zenodo.
Compare several open and commercial EEG systems on the same test signals with a transparent, repeatable method.
Possible outcome: A preprint with all raw data released.
Built an independent open-source project on PiEEG hardware or software? Share your public repository on Discord—notable projects get their own dedicated showcase page to highlight your work and credit your name.
Pick any hardware, DSP, ML, software, or open-science idea above, build it in your own GitHub repository, and document your results.
Notable community repositories shared on Discord can be featured with a dedicated article page linking directly to your GitHub, paper, and author profile.
See the 5 selected makers building mind-guided drones, robotic arms, c-VEP spellers, and neural jazz in the Octopus 16 Maker Challenge.
Information only. This page is general information and inspiration published by PiEEG Ltd. It is not an offer of work, volunteering, training or collaboration, and it does not create any employment, worker, volunteer, agency or partnership relationship between you and PiEEG Ltd.
Your project, your responsibility. Any project you start is your own independent activity. You decide whether to do it, how, and when. You are responsible for your own work, costs, equipment, safety and compliance with any laws that apply to you.
No obligations either way. PiEEG Ltd has no obligation to review, use, merge, feature or respond to anything you create, and you have no obligation to PiEEG Ltd. Contributions to PiEEG repositories are welcome but are accepted or declined at the maintainers' discretion under each repository's licence.
Ideas are provided “as is”. Ideas may be incomplete, may not work, and may change or be removed at any time without notice. To the extent permitted by law, PiEEG Ltd accepts no liability for any loss or damage arising from acting on them.
Use the name honestly. You may say your project is built on or compatible with PiEEG open source. Please don't present it, or yourself, as official, endorsed by, or working for PiEEG Ltd.
No. PiEEG Ltd does not offer volunteer, internship or unpaid roles. This page is a public list of ideas for independent open-source work. Picking an idea does not create any relationship with the company.
No. Everything listed builds on MIT-licensed code and open hardware files. Read the licence, start a repository under your own account, and go. There is nothing to apply for.
No. The company does not supervise, assign tasks, set deadlines or provide mentoring. The community on Discord often helps each other, but that is people helping people, not PiEEG Ltd managing a project.
No. We do not issue certificates, reference letters or confirmations of volunteering. Your public repository, commits, merged pull requests and publications are the best evidence of your work, and they belong to you.
Describe it as your own independent open-source project (for example, "Author of [your project name], an open-source tool compatible with PiEEG"). Please do not list PiEEG Ltd as your employer, host or organisation.
Yes, and that is often the best route. Your university supervises, assesses and covers ethics approval; you simply use open-source tools. PiEEG Ltd is not a party to the project and does not sign academic agreements for it.
Not as part of this page. Hardware is available through the normal store. Any separate community programmes (such as maker challenges) are announced on their own pages with their own terms.
You do. You choose the licence for your own code, designs and data, subject to the licences of anything you reuse. If you choose to submit a pull request to a PiEEG repository, it is accepted under that repository's licence.
You may say factually that your project works with or is built on PiEEG open hardware or software. Please don't name your project in a way that suggests it is official, endorsed or made by PiEEG Ltd.
Grab the code, start your own repository, and share what you build with the community.
