How does the driver interface work?

IsoKey utilizes a custom-signed kernel-mode driver that hooks directly into the Windows Human Interface Device (HID) stack. By intercepting raw input packets at the lowest level, we bypass the standard message queue, allowing for absolute isolation of secondary hardware from your primary system input.

Is there any input latency?

Because the interception occurs at the driver level rather than the user-mode hook level, latency is effectively sub-millisecond. In benchmarking, IsoKey overhead is statistically insignificant compared to native Windows input processing.

What hardware is supported?

IsoKey is hardware-agnostic. It works with any USB or Wireless keyboard that identifies as a standard HID device. It does not require proprietary drivers from the manufacturer, as it communicates directly with the Windows Raw Input API.

Can I use more than two keyboards?

Yes. The IsoKey engine can bind to an unlimited number of secondary devices simultaneously. Each device is assigned a unique Hardware Instance ID, allowing you to create massive multi-keyboard command centers.

What are Action Clusters?

Action Clusters allow you to chain multiple automation steps—keystrokes, script executions, and window movements—into a single trigger. Each step can have a micro-delay defined in milliseconds for perfect synchronization with slow-loading applications.

Is IsoKey safe for Anti-Cheat software?

While IsoKey uses kernel drivers, it does not use "cheat" techniques like code injection or memory manipulation. It is a legitimate productivity tool. However, because it bypasses standard input, some highly aggressive anti-cheats (like Vanguard) may flag the driver signature. We provide a native uninstaller in the settings to completely remove all driver hooks when not in use.