Our mission

You bought the hardware. Own the behavior.

A keyboard is not a layout. A mouse is not a preset. They are general-purpose input devices, and the person who owns them should decide what every input means. Rebind exists to make input programmable, portable, and answerable to its user.

How Rebind works

What we believe

Ownership should mean more than a menu.

Most input hardware is sold as capable equipment and delivered as a closed set of approved behaviors. Access to settings is not ownership. The ability to define the behavior is.

programmability

Input should be programmable

Input is where intention becomes action. A Rebind script can read an event, replace it, combine it, delay it, or route it by application. One key can change. So can the whole system.

portability

Rules outlive the hardware

A rule should not disappear because the keyboard changed logos. Rebind works at the input layer, so the same core script moves across supported keyboards, mice, and operating systems.

software first

The idea proves itself in software

The Rebind Engine is free in software mode. Learn the model, build useful rules, and decide whether Rebind belongs in your workflow before buying anything. Rebind Link adds a hardware output path, if you ever need it.

What ownership requires

Control is only real when it is inspectable.

Programmability alone is not enough. Ownership requires visibility, an exit, and honest boundaries.

visibility

The logic is readable

Local scripts are files you can inspect, edit, copy, and keep. Generated scripts are reviewed before they run. Behavior is never buried in a profile database only one application understands.

recovery

There is always an off switch

Left Ctrl + Left Alt + K stops every script and releases held keys. Power over input includes the power to stop it immediately.

permissions

Permissions are explained

Input, screen, files, networking, and remote control are different powers. Rebind states which one it needs, why it needs it, and how to remove it.

boundaries

Limits stay visible

Core scripts travel across Windows, macOS, and Linux. Some desktop integrations do not. We publish the platform boundaries instead of smoothing them into a promise the product cannot keep.

What we are not building

Control without deception.

Rebind is not an anti-cheat bypass, a stealth-input promise, or a way to take control of someone else's machine. It gives people a programmable layer over input they own, on computers they control.

We will not call platform differences identical. We will not describe host-side scripts as hardware execution. We will not hide a recurring term behind the word lifetime. Power without accurate terms is just another locked menu.

The Rebind mission

Make input belong to the person providing it.

Your hands provide the intention. Your hardware carries it. Your code decides what happens between them.

Download free

you bought the hardware. own the behavior.