Inside Keychron's Open-Source Gaming Mouse Firmware

Keychron's pitch for the project is a complaint about the whole category: every gaming mouse on the market runs firmware you can't read, can't audit, can't change. Mechanical keyboards escaped that world years ago with QMK and ZMK. Mice never did.

So Keychron announced ZGM, short for Zephyr Gaming Mouse, on July 29, 2026, with a planned launch around Q1 2027. Here is the honest part: the public repo does not contain firmware yet. The README states plainly that sources, board support, build instructions, and flashing guidance are still being prepared.

That makes this a deep dive into an architecture Keychron has committed to, not one it has shipped. The interesting engineering is in the decisions already locked in: the base it builds on, how it plans to split the code, and how it is licensed.

The Z in ZGM is Zephyr, the same real-time OS that ZMK already uses for keyboards. That lineage is the point. Instead of writing an RTOS and a peripheral layer from scratch, Keychron inherits Zephyr's existing MCU support, its device model, and its config and build tooling.

Coverage reporting frames ZGM as the mouse-side counterpart to what ZMK did on keyboards, running on the same underlying framework. Picking a mature RTOS with broad MCU and peripheral support means the hard, generic plumbing is a dependency rather than a deliverable. The team gets to spend its budget on the parts that make a mouse a mouse.

The central design commitment is a driver-model abstraction. Common mouse behavior, things like input processing, HID reporting, debounce policy, lighting, and power management, lives in a shared layer, while the hardware specifics of which sensor, which MCU, and which switches sit behind driver interfaces. The stated goal is that one firmware base can support different hardware variants without turning into a monolith.

If it works, the payoff goes past Keychron's own catalog. One report notes this could eventually let a single PCB design run different internal components under a shared firmware layer, even community-designed or hot-swappable parts. That last part is journalistic extrapolation, not a published spec, so treat it as the direction of travel rather than a promise.

ZGM ships under GPL-3.0. That is a deliberately permissive pick: it allows remixing, repackaging, and redistribution, including commercial use. In practice it means other mouse manufacturers could take ZGM as the basis for their own products, which is a striking thing for a hardware company to invite.

It is worth contrasting with Keychron's separate hardware-design repository, which holds industrial CAD for 100+ models but is only source-available, allowing personal use and original compatible accessories while restricting resale of Keychron's own designs. The firmware being GPL and the CAD being merely source-available is a clear signal about where Keychron thinks the leverage is: give away the code, keep a fence around the branded hardware.

The reference hardware is the Keychron G6 HE, a 46 g wireless mouse with a swappable battery, a charging puck, and hybrid MagOpt switches that combine magnetic and optical sensing. Keychron positions it directly against Logitech's G Pro X2 Superstrike, which is the whole reason the firmware story carries weight. Open firmware on a genuinely competitive flagship is a very different bet than open firmware on a budget peripheral.

The roadmap runs eight milestones, and the ordering tells you what to expect first. USB HID functionality lands before the extended device features where wireless and lighting live, so wired support arrives ahead of wireless. Keychron is explicit that this is a plan, not a guaranteed schedule, and it is even asking the community to help define an input-latency measurement methodology, which means no latency benchmarks exist yet.