The Keybytes system combines magnetic cases, pogo‑pin connections and Bluetooth in a fully rearrangeable layout.
OPEN-SOURCE KEYBYTES MODULAR KEYBOARD SHOWS REARRANGEABLE KEYS
*A GitHub project delivers a fully modular, Bluetooth‑enabled keyboard where each key is a standalone 1u PCB. The design packs RISC‑V microcontrollers, magnetic cases and open‑source tooling, promising a new DIY path for enthusiasts.*
A new open‑source keyboard project has hit GitHub, promising a level of modularity rarely seen in consumer keyboards. The repository, notaroomba/keybytes, showcases a design where every key is a self‑contained 1u PCB equipped with its own RISC‑V microcontroller and four‑sided pogo pins. Users can rearrange keys at will, snapping them together with magnetic cases and linking them to a Bluetooth‑enabled main board. The project bundles firmware, PCB layouts, 3D case models and a video demo, all under an MIT license. With 199 stars and a handful of forks, the community response suggests strong interest among DIY hardware enthusiasts.
How does Keybytes achieve true modularity?
Keybytes treats every key as an independent 1u PCB called a Keybit. Each Keybit houses a CH32V003 RISC‑V microcontroller, a Cherry MX switch and pogo pins on all four sides for 3.3 V, GND and I²C. The pins let a Keybit snap to any other Keybit or to the central Keyword board, forming a rearrangeable matrix without soldering. Magnetic cases lock the modules together, while programming occurs over the same pogo pins from the main board. This architecture eliminates a fixed PCB layout, letting users reconfigure the keyboard on the fly.
What hardware makes the system tick?
The Keyword board is a split stack of two PCBs. The top layer carries an STM32WB55RGV6 Bluetooth/USB controller, a ceramic antenna and a 2 MB QSPI flash (W25Q16JV) for key firmware. The bottom layer provides a USB‑C connector with ESD protection, a BQ25895 charger, and a TPS631000 buck‑boost converter for a 1S LiPo cell. RGB status LEDs indicate power and connection state. All boards are designed in KiCad, and the case files reside in Onshape STEP format. The design includes pogo pins on every side of each Keybit, enabling power, data and programming pathways without additional wiring.
Why does open‑source matter for keyboard design?
Keybytes is released under an MIT license, with source files for firmware, PCB schematics and case geometry publicly available. The repository lists 199 stars, 4 forks and a single watcher, indicating a niche but engaged community. By exposing the BOM.csv, KiCad projects and Blender renders, the project invites collaborators to iterate on the hardware, firmware or aesthetics. Open‑source tooling lowers the barrier for hobbyists to build custom keyboards, potentially disrupting proprietary key‑matrix manufacturers that lock users into fixed layouts.
What are the next steps for the project?
The GitHub page hosts a video demo, a README and a JOURNAL.md documenting development milestones across 40 commits. Contributors can clone the repo, flash the CH32V003 on each Keybit via the programming pads, and assemble the magnetic case using the provided CAD files. Future work may expand the firmware library, add alternative switch options or integrate additional sensors. With the core architecture proven, the community can focus on scaling production, refining battery life and exploring new form factors.
Frequently asked questions
What microcontroller does each Keybit use?
Each Keybit contains a CH32V003 RISC‑V microcontroller.
How does the keyboard achieve wireless connectivity?
The main Keyword board houses an STM32WB55RGV6 chip that provides Bluetooth and USB connectivity.
Under what license is the Keybytes project released?
The project is released under the MIT license.
Keybytes demonstrates that a fully modular, Bluetooth‑ready keyboard can be built from off‑the‑shelf microcontrollers and open‑source design tools. By exposing every layer of the stack—from firmware to case geometry—the project invites rapid iteration and community‑driven improvement. If the momentum translates into broader adoption, we could see a shift away from monolithic keyboard PCBs toward truly customizable input devices.
Sources: [GitHub - notaroomba/keybytes]