Your firmware builds itself.

Describe your keymap in plain English. InputForge generates production-ready QMK and ZMK configs, manages sensor calibration, and keeps every device in sync. Built for the builders who refuse to use stock firmware.

inputforge build
$ describe your layout
"Split 3x5+3. Left thumb: space hold-tap
 layer 1. Right thumb: backspace.
 Home row mods GACS. PMW3389 trackball
 on right half, 800 CPI default."


// Generating QMK config...
✓ keymap.c   generated
✓ config.h   sensor calibrated
✓ rules.mk  build flags set
✓ firmware.hex ready to flash

$ _

The Problem

Custom input devices deserve better than editing C header files at 2am to change a key binding.

01

Natural Language Config

Describe your layout, layers, and combos in plain English. InputForge generates correct QMK or ZMK code, handles hold-tap timing, and resolves conflicts automatically.

02

Sensor Calibration

PMW3389, PMW3360, Cirque Pinnacle, ADNS-9800. Dial in CPI, lift-off distance, angle snapping, and smoothing through a guided workflow instead of trial-and-error flashing.

03

Multi-Device Sync

Manage configs for every board you own in one place. Push a layer change to your daily driver and your travel board simultaneously. Version every edit.


How It Works
01

Describe

Tell InputForge what your hardware is and how you want it to behave.

02

Generate

AI produces a complete firmware config: keymaps, sensors, build rules.

03

Tune

Adjust timing, calibration, and layers through conversation, not code.

04

Flash

Download your compiled firmware or push directly via WebUSB.


Stop configuring.
Start building.

InputForge exists because the best input devices in the world shouldn't require a CS degree to configure. The firmware should work as hard as the person who soldered the PCB.