Redox Keyboard: Split QMK Build Guide

Why the Redox Split Layout Exists

Redox addresses builders who want an ergonomic mechanical keyboard with fewer keys than the Ergodox design that inspired it. Its goal is stated plainly in the project name and README: reduce the Ergodox footprint without sacrificing too many keys. The physical arrangement is a 7x5 columnar stagger on each side. That matters for keyboard selection because column staggering, tenting, thumb reach, and case geometry affect the fit of a keyboard to a user's hands and desk. A smaller split board can occupy less desk space than a full Ergodox, but the Redox is still a custom mechanical build rather than a compact office keyboard.

The design also addresses several practical complaints the designer had as an Ergodox user. The README identifies an easier-to-reach thumb cluster and adds a rotated 1.25u thumb key. Each half can act as the keyboard master, so either side can be connected to a PC. A single half can also operate as a standalone keyboard, which gives the design a route to use as a macropad or gaming keyboard. Those choices are useful for builders who want flexible firmware and split-board operation, but they do not remove the need to understand USB connections, controller placement, and key-matrix firmware.

Redox targets hobbyist keyboard builders, people familiar with Ergodox-style layouts, and users who prefer QMK or another supported firmware ecosystem. It is less suitable for someone buying a finished keyboard and expecting a software-only setup. The repository presents physical design files, assembly references, PCB revisions, case options, and links to firmware projects. It is therefore closer to a complete hardware project hub than a conventional keyboard firmware repository.

Redox Hardware and Firmware Architecture

The wired Redox uses Cherry MX style mechanical switches and Arduino Pro Micro controllers. The README specifically contrasts Pro Micro with the Teensy 2.0 used by the Ergodox, describing the Pro Micro choice as a way to reduce cost. The keyboard's split construction means the two halves have separate physical assemblies. The documentation says that either half can be plugged into the PC and either half can act as master, so the firmware and wiring arrangement are expected to support either side becoming the USB-connected device.

The project supports more than one firmware path. QMK is the primary firmware named in the README, with Redox firmware sources linked separately under the `redox` directory. VIA compatibility is also documented, and the README links QMK, ZMK, and KMK resources for Redox. The presence of several firmware ecosystems gives a builder choices, but it also makes firmware selection part of the build decision. A layout written for QMK cannot be assumed to be directly interchangeable with ZMK or KMK without checking the linked source for the relevant keyboard and revision.

The repository separates wired and wireless designs. The `redox/` directory is associated with Redox rev1.0, while `redox-w/` covers Redox rev1.0W. The README states that rev1.0W PCB gerbers are available in the repository and links separate firmware for Redox wireless and Nordic MCUs. It also notes that Falbatech's wireless hot-swap PCBs are incompatible with the listed 3D-printable cases. That is an important hardware boundary. Buyers cannot treat the wired and wireless parts lists as interchangeable.

Building Redox from the Available Revisions

Redox does not provide a software installation command in the README. The project is a physical keyboard, so the first real use begins with selecting a revision and obtaining the relevant hardware. For the wired rev1.0, the README points to Falbatech for a set of two PCBs and separately links firmware sources, printable cases, a high-profile case, a travel-friendly case, and other community case projects. For rev1.0W, it points to the repository's Gerber files for the PCBs and to a separate `redox-w/case` directory for a printable case.

A builder should begin by deciding whether the goal is the wired or wireless revision. Then select a case whose design matches that revision and PCB set. The README's incompatibility note for Falbatech's rev1.0W hot-swap PCBs makes this check explicit. Cherry MX style switches are the stated switch family, so switch compatibility should be checked against the PCB and case rather than assumed from the general category of mechanical keyboard.

After the parts are selected, the build involves assembling the switch matrix, fitting the controller, soldering the split interconnect and USB connection, and mounting the electronics in the chosen case. The README gives links to firmware sources, but the excerpt does not give a complete step-by-step flashing procedure, connector pinout, BOM, or calibration sequence. No command is included here because the project documentation does not define a universal installation command that would complete those steps. The practical first use is therefore a hardware build followed by flashing the firmware selected for the exact Redox revision.

Case Options and Revision Compatibility

The case is not a single fixed enclosure in this project. The README lists a freely available 3D-printable case, a high-profile case, a travel-friendly case, and additional community designs. It also links bamboo cases and a tilt kit offered through Falbatech, but the commercial case listing is specifically described as compatible with Falbatech's PCBs. This distinction matters because a printable design that looks appropriate for the keyboard silhouette may not match the PCB footprint, mounting posts, connector position, or wireless electronics.

The project also points to variants inspired by the Redox, including Dactyl Manuform, Iris, and tenting designs. Those links show an active design ecosystem, but they should not be treated as drop-in replacements without checking their documentation. The README calls out special cases such as a tilted case with Pro Micro and USB-C support, a Redox tenting kit, and a Redox big battery project. Each changes at least one physical constraint, so case choice affects the parts list and possibly the assembly process.

For a first build, the least ambiguous route is the wired rev1.0 documentation paired with a case explicitly identified for that PCB set. The wireless route requires checking the rev1.0W Gerber and case together. The absence of GitHub releases means there is no repository release artifact to use as a stable, bundled build target. The last push was on 2026-05-26, so revision details should be checked against the current files and linked firmware repositories before purchasing components.

Maintenance, Firmware Updates, and MIT Licensing

The repository is not archived, and its last push was on 2026-05-26. That is recent repository activity, although the project has no GitHub releases. Updates may therefore be made directly in the default branch and related repositories rather than through a documented release process. This creates a maintenance consideration: a builder should record the revision and firmware source used for a build instead of assuming that a later branch state is interchangeable with the files already in a case.

Maintenance cost is mostly assembly and compatibility work rather than subscription cost. The hardware uses standard Cherry MX style switches and Arduino Pro Micro controllers, but the controller, PCB revision, case, wireless hardware, and firmware still have to be treated as one build configuration. A firmware change can affect key behavior, RGB support, split operation, or wireless operation, although the README does not provide a formal upgrade policy or rollback procedure. It also does not document a release cadence.

The repository identifies the project as MIT licensed. That permits use and modification under the license's terms, subject to its conditions, but this review does not interpret the license or provide legal advice. Users who distribute a Redox case, PCB modification, or keyboard product should review the repository's `LICENSE` file and any separate firmware and hardware licenses themselves. The firmware is linked to QMK, ZMK, KMK, and project-specific repositories, so the root project's MIT status should not automatically be assumed to cover every external component.

Editorial conclusion

Builders who want the Redox layout, can assemble a split keyboard, and need QMK, ZMK, KMK, or VIA options should adopt it. Users seeking a ready-to-use keyboard, a conventional unsplit layout, or a fully documented one-command setup should look elsewhere. Before ordering parts, verify controller compatibility, wired or wireless PCB revision, case fit, and the firmware source for that exact revision; Redox is a hardware design and build project, not a packaged keyboard application.

Frequently asked questions

Official sources

1. Issues
2. License: MIT
3. mattdibi/redox-keyboard on GitHub
4. README