Skip to content

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.

For HID and AirLeak, the answer is now the mobile app

This comparison reflects the legacy desktop-first workflow. Today, HID and AirLeak are managed from the ZeroTrace mobile app over Bluetooth, that is the recommended path. The desktop Companion now applies mainly to BLELogger. The device Web UI and a generic serial terminal remain valid for all devices.

ZeroTrace BLELogger can be managed three ways: via the desktop Companion, via the device's built-in Web UI, or via a generic serial terminal (PuTTY, screen, minicom, etc.). Each has its place. HID and AirLeak are managed from the mobile app, see that section for those devices.

Side by side

FeatureCompanionWeb UIGeneric terminal
Device supportBLELogger (HID + AirLeak moved to the mobile app)One device per browser tabYes, raw connection
Auto device detectionYes, probes every COM portn/a (browser-based)No, you pick the port
Visual dashboardYes, full UIYes, different per deviceNo, text only
AirLeak live workspaceYes, full feature setLimitedNo
Capture sessionsYes, disk-backed libraryLimited (browser storage)No
Known-device libraryYes, persists across sessionsNoNo
Offline AI assistantYes, local LLM with tool callingNoNo
Multi-device switchingYes, one clickTab switching in browserNew connection per device
Works without internetYesYes, Wi-Fi to deviceYes
Always availableRequires installBuilt into device firmwareBuilt into your OS
Free to installYes, no account, no subscriptionYes (built-in)Yes

When to use Companion

  • You use BLELogger, Companion is its desktop home, terminal access plus the offline AI assistant.
  • You want the AI assistant, local LLM with tool calling is a Companion feature.
  • You manage a BLELogger over USB, direct serial is fast and reliable for routine management.
HID and AirLeak work?

Use the mobile app. It handles HID payloads and live input, the full AirLeak suite (live scanner, Fox Hunt, Drive, Insights), and the TraceNet mesh over Bluetooth, no cable, no desktop.

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:

(ZeroTrace HID no longer has an on-board web UI, it is driven from the mobile app.)

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.

For BLELogger the three options coexist: use Companion as your default, reach for the Web UI when you're away from your workstation, and reach for a generic terminal when you're debugging. For HID and AirLeak, the mobile app is the default.

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.