Skip to content

Product overview

What Controll3r does

Controll3r turns a Windows computer into a hardware crash cart for another computer — the monitor-and-keyboard station a technician would physically wheel up to a broken machine, rebuilt as software plus two small pieces of hardware. The operator sees the target's real video output through a capture device and sends keyboard and pointer input through the Controll3r Interface, which the target sees as ordinary USB input hardware.

Because control happens below the target operating system, Controll3r remains useful when software-only remote access cannot work:

  • BIOS and UEFI configuration
  • boot menus and recovery environments
  • operating-system installation and imaging
  • machines with broken networking or remote-access services
  • air-gapped targets
  • locked or unresponsive operating systems
  • repeatable setup work across similar machines

Nothing is installed on the target. The target does not need an account, network connection, driver package, or cooperating operating system.

The three-part connection

Operator Windows PC
  |-- USB or PCIe capture device <--- target video/audio output
  |
  `-- Controll3r Interface
        |-- control-side USB ---> operator Windows PC
        `-- target-side USB  ---> target computer

The capture device carries video and, when supported, audio back to the operator. The Controll3r Interface carries keyboard and pointer actions to the target.

More than a live KVM

Controll3r also provides:

  • snapshots and MP4 recording
  • local audio monitoring with volume, mute, and loudness leveling
  • paste-as-typing, reusable Paste Snippets, and shortcut buttons
  • local OCR from the captured screen
  • a target-input-to-captured-frame latency test
  • saved hardware and UI sessions
  • visual automation macros that find controls on screen before acting
  • unattended headless operation and a bearer-authenticated REST API

Visual Anchoring

Traditional input macros assume that a button will always be at the same coordinate. Controll3r can instead record a Visual Anchor: a small image of the control or region that matters. During playback it searches the live target image for that anchor and acts at the matched location.

Macros can wait for an anchor to appear or disappear, choose between two paths, repeat work, pause for an operator, and stop safely when a condition is not met. This makes automation useful on boot screens and other environments where ordinary software automation has nothing to hook into — there is no app, browser, or operating system to script, only the picture on the screen.

Automation acts like a person at the keyboard

A Controll3r macro sends real keyboard and pointer input to a real machine, including firmware screens. It can change BIOS settings, delete data, or start an operating-system reinstall exactly as a person sitting at the keyboard could. Build and test macros against non-production systems first, use timeouts and Wait For Operator steps around risky actions, and review what a macro does before running it unattended. You are responsible for what your automation does to your systems.

Intended users

  • technicians who need a desk-side alternative to a physical crash cart
  • system builders and lab operators
  • deployment and imaging teams
  • firmware and BIOS validation teams
  • operators repeating structured input across similar systems
  • advanced users who need auditable automation without target-side software

Controll3r is not a replacement for RDP or other high-bandwidth desktop streaming when the target operating system is healthy and reachable. It is for the layer beneath those tools and for workflows that must behave like physical keyboard, pointer, and monitor hardware.