How it works

Every input runs through your scripts.

Rebind sits between your devices and your computer. Every keypress and mouse movement passes through your Luau scripts before anything else sees it.

fig. capture · script · output

The pipeline

Three stages, every event.

Capture, script, output. When no scripts are loaded, the engine passes input straight through.

01 · capture

Capture

Every keypress, mouse movement, and scroll delta is taken before your applications see it. Software mode captures through OS event hooks. Hardware mode captures inside the Rebind Link, before your OS sees the raw input at all.

02 · script

Script

Each event fires your hooks: OnDown, OnUp, OnMove, OnScroll, OnTick. Remap keys, transform movement, run macros, make HTTP calls. Scripts are sandboxed Luau with execution budgets, so a runaway script stops itself and a crash takes only that script down.

03 · output

Output

The transformed result reaches your computer. Software mode injects through OS input APIs. Hardware mode emits real USB HID, so your OS sees a standard keyboard and mouse and needs no special drivers.

Two paths out

Software first. Hardware when you need it.

Both paths run the same scripts. What changes is how the result reaches your computer.

software mode

No hardware required

The engine captures and emits through operating system input APIs. Remaps, macros, text expansion, per-app profiles, and the full Luau SDK all work this way, on the keyboard and mouse you already own.

hardware mode

Output leaves as a real device

Rebind Link plugs in as its own USB device and performs the input itself. Scripts still run on the host; the device carries the result onto the wire.

The hardware line

What only hardware can do.

One capability software cannot reach on any operating system: rewriting mouse movement.

The operating system draws the cursor below anything a host process can intercept, so only a device that owns the input stream can transform motion. Keys, buttons, and scroll can be suppressed in either mode.

The full physics of both paths is in the documentation(opens in a new tab).

How it works

Nothing reaches your OS that you did not write.

Your devices feed in, your scripts decide what every event means, and your computer receives the result as ordinary input.

Download v3.3.7

capture · script · output