ZeroTrace Companion
Companion vs. Web UI vs. Terminal-only
When to use Companion, when to use the device's built-in Web UI, and when to use a generic serial terminal.
ZeroTrace devices can be managed three ways: via Companion, via the device's built-in Web UI, or via a generic serial terminal (PuTTY, screen, minicom, etc.). Each has its place.
Side by side
| Feature | Companion | Web UI | Generic terminal |
|---|---|---|---|
| Cross-device support | HID + BLE Logger + AirLeak in one app | One device per browser tab | Yes, raw connection |
| Auto device detection | Yes — probes every COM port | n/a (browser-based) | No — you pick the port |
| Visual dashboard | Yes — full UI | Yes — different per device | No — text only |
| AirLeak live workspace | Yes — full feature set | Limited | No |
| Capture sessions | Yes — disk-backed library | Limited (browser storage) | No |
| Known-device library | Yes — persists across sessions | No | No |
| Offline AI assistant | Yes — local LLM with tool calling | No | No |
| Multi-device switching | Yes — one click | Tab switching in browser | New connection per device |
| Works without internet | Yes | Yes — Wi-Fi to device | Yes |
| Always available | Requires install | Built into device firmware | Built into your OS |
| Free to install | Yes — no account, no subscription | Yes (built-in) | Yes |
When to use Companion
- You own multiple ZeroTrace devices — Companion is the only thing that handles HID + AirLeak + BLE Logger in one window.
- You do AirLeak work — the live workspace, sessions, library, insights, and alerts are Companion-only features.
- You want the AI assistant — local LLM with tool calling is Companion-only.
- You manage devices over USB — direct serial is faster and more reliable than Wi-Fi for routine management.
When to use the Web UI
- You're not at your usual workstation — your phone, a colleague's laptop, a hotel kiosk. The Web UI runs entirely on the device's own Wi-Fi access point.
- You're managing a remote-mounted device — the device is somewhere you can reach over Wi-Fi but not over USB.
- You don't have Companion installed and you only need to do one quick thing.
- You're using a device without a COM port (ZeroTrace Mini, Lilygo T-Dongle S3) — the Web UI is the only option.
See the per-device docs for the Web UI details:
When to use a generic terminal
- You're debugging Companion itself and need to verify the device is responding before involving Companion's logic.
- You are scripting the device from a shell pipeline and want raw serial access.
- You're on a system where Companion does not run (a build server, a remote SSH session, a stripped-down container).
- You prefer a terminal-first workflow and the Companion terminal does not fit your habits.
For HID devices, the on-device command set is documented at ZeroTrace HID scripting. The same commands work whether you type them into Companion's terminal, a generic terminal, or a script that pipes them in.
The three options coexist. Use Companion as your default; reach for the Web UI when you're away from your workstation; reach for a generic terminal when you're debugging.
Side note: ZeroTrace Proxy and ZeroTrace OSINT
Companion is the device-management app. It is not the same as:
- ZeroTrace OSINT — the desktop OSINT toolkit. Different application, different purpose.
- ZeroTrace Proxy — the proxy workflow suite. Different application, different purpose.
All three are separate desktop apps. They are designed to coexist on the same machine and have separate installs.