
Keyboard
split keyboard for everyone
- Size
- 149.2 × 105.8 mm
- Copper layers
- 2
- Thickness
- 1.6 mm
- Parts
- 54
- Nets
- 55
- Pads
- 424
- Tracks, vias
- 1,203, 102
- Pours
- 2
- Routed
- Yes
- KiCad
- KiCad 10.0 (file 20260206)
- Created
- 12 Jul 2026
- Updated
- 16 Jul 2026
Overview
Keyboard is an open-source printed circuit board by pixel-and-circuit, from the pixel-and-circuit/ghkb repository on GitHub, published under the GPL-3.0 licence. It is a 2-layer board of 149.2 × 105.8 mm with 54 parts on 55 nets, routed with 1,203 tracks and 102 vias.
Its parts include 22 diodes and 21 switches. It belongs with the keyboards and input boards of this library.
README
README.mdGHKB
GHKB is an open-source split mechanical keyboard project focused on custom hardware, modern firmware, and long-term experimentation.
The goal of this project is to build a fully custom wireless split keyboard from the ground up, including both the hardware and firmware stack. Rather than assembling an existing design, GHKB documents the complete engineering process—from PCB and enclosure design to firmware development.
Goals
Phase 1: Build a Reliable Daily Driver
Develop a fully functional wireless split keyboard featuring:
- Custom PCB designed with KiCad (single reversible design shared by both halves)
- Custom 3D-printed enclosure
- MX-compatible mechanical switches on hotswap sockets
- Battery-powered operation
- Bluetooth Low Energy (BLE)
- ZMK firmware
- Comfortable ergonomic layout
Controller strategy: the first prototype targets an off-the-shelf nRF52840 controller module (e.g. Nice!Nano) socketed onto the PCB. Designing a fully custom controller—placing the nRF52840 QFN/BGA package directly on the board—is a later, optional goal once the socketed design is validated.
Hardware design decisions:
- Layout: 42 keys — a 3x6 column-staggered matrix plus a 3-key thumb cluster per half (Corne-style), with an optional EC11 rotary encoder position.
- PCB: one reversible PCB serves both halves (components mount on the front for one half and on the back for the other), halving design and manufacturing effort.
- Switches: MX hotswap sockets (Kailh), so the prototype can be reworked without desoldering.
- Display: none. A display only shows status (battery, layer, BLE profile) and is not needed for keyboard operation; omitting it saves cost, battery, and three GPIOs kept as spares.
- RGB: deferred past Phase 1. Per-key RGB is battery-hostile on a wireless board; at most, unpopulated footprints are reserved.
- Layout generation: switch placement and the board outline are generated with ergogen and imported into KiCad, so layout iterations stay reproducible.
Phase 2: Develop a TinyGo Firmware
Create a native TinyGo firmware targeting the same hardware platform. The long-term objective is not simply to recreate existing keyboard firmware, but to explore whether a modern Go-based embedded ecosystem can become a practical alternative for custom keyboard development.
Because the wireless BLE stack is by far the highest-risk part of this effort, Phase 2 is split into two independent milestones:
Phase 2a: USB-wired TinyGo firmware (high feasibility)
Bring up a wired, single-board or wired-split TinyGo build using USB HID, which is well supported in the TinyGo ecosystem and has existing precedent. This establishes the matrix scanning, keymap, and feature layer in Go without depending on wireless.
Phase 2b: BLE-wireless TinyGo firmware (research / uncertain)
Extend the firmware to full wireless operation. This is genuinely exploratory
and may not be achievable: TinyGo's BLE support (tinygo.org/x/bluetooth) has
historically centered on the central/scanner role and relies on Nordic's
SoftDevice, whereas a keyboard needs a BLE peripheral with HID-over-GATT,
pairing/bonding, and a wireless split link. ZMK gets these for free from
Zephyr's mature BLE stack; in TinyGo much of it would have to be built from
scratch. Treat Phase 2b as an open question, not a scheduled deliverable.
Planned Features
- Wireless split architecture
- Bluetooth Low Energy (BLE)
- Multi-device pairing
- Battery management
- USB-C charging
- Layer support
- Mod-Tap / Hold-Tap
- Combo keys
- Rotary encoder support
- Optional RGB lighting (post-Phase 1)
- Firmware updates via bootloader
Repository Structure
Note: this is the planned/target layout for the completed project. The repository currently contains only this README while the project is in the planning and hardware design phase; directories below are created as work progresses.
.
├── README.md
├── HARDWARE.md
├── LICENSE
├── .gitignore
├── config/
│ ├── west.yml
│ ├── ghkb.keymap
│ └── boards/shields/ghkb/
├── build.yaml
├── firmware/
│ └── tinygo/
├── pcb/
│ ├── ergogen/
│ │ ├── config.yaml
│ │ └── footprints/
│ ├── keyboard.kicad_pro
│ ├── keyboard.kicad_sch
│ ├── keyboard.kicad_pcb
│ └── libraries/
├── case/
│ ├── source/
│ │ ├── params.py
│ │ ├── layout.pyDirectory Overview
Directory Description
HARDWARE.md Sourcing guide: full parts table with purchase links, PCB fab options, and assembly cautions.
config Production ZMK firmware config (west manifest, keymap, custom ghkb shield). Lives at the repo root because ZMK's reusable CI workflow expects config_path/build_matrix_path relative to the west topdir, which must be the repo root - not a nested subdirectory.
firmware/tinygo Experimental TinyGo firmware implementation.
pcb KiCad project files, schematics, PCB layout, and custom libraries.
pcb/ergogen Ergogen layout source (YAML) and reversible footprint library.
case/source Parametric enclosure build scripts (params/layout/ghkb_case.py) and the generated FreeCAD documents. The switch plate is integrated into the top shell, so there is no separate plate design. Rebuild everything with freecadcmd case/source/ghkb_case.py; the build asserts its geometry against the routed PCB and aborts on drift. render_preview.py regenerates the README preview images from the built FCStd documents (needs the FreeCAD GUI).
case/exports Exported manufacturing files (per-half STEP, print-ready top/bottom STLs).
case/reference kicad-cli STEP export of the routed PCB, used for interference checks.
docs Assembly guide, wiring documentation, and project images.
bom Bill of Materials used to build the keyboard.
Roadmap
- Finalize the keyboard layout (42-key, 3x6+3 per half)
- Design the PCB (single reversible board, ergogen + KiCad)
- Design the enclosure (integrated-plate top shell + screwed lid, parametric FreeCAD build; v1 done, pending print validation)
- Build the first prototype
- Bring up ZMK firmware
- Validate the hardware
- Use as a daily driver
- Develop USB-wired TinyGo firmware (Phase 2a)
- Investigate BLE-wireless TinyGo firmware (Phase 2b, research)
- Document the complete development process
Status
This project is currently in the planning and hardware design phase.
Contributing
Contributions are welcome.
Whether you are interested in mechanical keyboards, embedded systems, TinyGo, ZMK, PCB design, or 3D modeling, feel free to open an issue or submit a pull request.
License
This project is dual-licensed to ensure that anyone who uses, modifies, or sells GHKB — commercially or otherwise — must release their own source under the same copyleft terms.
-
Software / firmware / source code (everything in
config/,zmk/,modules/,firmware/, build scripts, documentation sources, etc.) is licensed under the GNU General Public License v3.0 (GPL-3.0) — a strong copyleft license. You may sell copies, but any distributed modified version must be released as source under GPL-3.0. See theLICENSEfile. -
Hardware designs (
pcb/,case/, including KiCad projects, schematics, PCB layouts, footprints, and 3D-printed enclosure source) are licensed under the CERN Open Hardware Licence v2 – Strongly Reciprocal (CERN-OHL-S). Any product or design derived from these must have its corresponding design source made available under the same licence. See theLICENSE-HARDWAREfile.
In short: commercial sale is allowed, but reciprocity is mandatory — if you convey GHKB (or a derivative) to others, your modified software and hardware source must stay open under these licenses.
Parts
54| Qty | Value | Footprint | References |
|---|---|---|---|
| 22 | ceoloide:diode_tht_sod123 | D1, D2, D3, D10, D11, D12, D13, D14, D15, D16, D17, D18, D19, D20, D21, D22 +6 | |
| 21 | ceoloide:switch_mx | S1, S2, S3, S4, S10, S11, S12, S13, S14, S15, S16, S17, S18, S19, S20, S21 +5 | |
| 6 | MountingHole_2.2mm | MountingHole:MountingHole_2.2mm | MH1, MH2, MH3, MH4, MH5, MH6 |
| 1 | ceoloide:rotary_encoder_ec11_ec12 | RE1 | |
| 1 | ceoloide:power_switch_smd_side | PWR1 | |
| 1 | ceoloide:battery_connector_jst_ph_2 | JST1 | |
| 1 | ceoloide:mcu_nice_nano | MCU1 | |
| 1 | ceoloide:reset_switch_tht_top | RST1 |
Similar boards
- 2 layers203 × 26.6 mm

- 2 layers30 × 50 mm

- 2 layers100.1 × 40 mm

32Bit shift register
MaltWhiskey/Mega-Cube
16x16x16 PL9823 Cube with Teensy 4.0 and FlexIO driver
54 parts766 - 2 layers100 × 120 mm

- 2 layers

- 2 layers104.3 × 38.9 mm

- 2 layers

- 2 layers93.8 × 64.2 mm

PiFinder smt
brickbots/PiFinder
A plate solving telescope finder based around a Raspberry PI and RPI HQ Camera
54 parts257GPL-3.0
Questions
How big is the Keyboard PCB?
It measures 149.2 × 105.8 mm and has 2 copper layers, 1.6 mm thick.
What parts does the Keyboard use?
54 parts. The full list of its parts is on this page, with links to each part's symbol and footprint where PCBKit's library has them.
Where can I download the Keyboard KiCad files?
From the pixel-and-circuit/ghkb repository on GitHub, at the commit this page was made from: the board is pcb/keyboard.kicad_pcb. PCBKit opens the board in the browser, with nothing to install.
Can I use the Keyboard design in my own project?
Its repository publishes it under the GPL-3.0 licence: you may reuse it on that licence's terms (keep the author's notice, and for a copyleft licence share your changes alike).