Get started

How Fieldhand works

One agent, one outbound connection, a shell and health data in your browser.

Fieldhand is a small agent you install on each Linux device and a dashboard at fieldhand.dev. The agent dials out to Fieldhand over TLS and keeps that one connection open. Through it you get a root shell in the browser and a live view of the device's health, from anywhere, without port forwarding, a VPN or a public IP on the device.

The pieces

PartWhat it does
AgentA single static Go binary (about 11 MB of RAM when idle). Opens shells, reports health, updates itself.
Relayrelay.fieldhand.dev. Holds each device's WebSocket and pairs it with your browser's terminal.
APIapi.fieldhand.dev. Enrollment, the device list, metrics, alerts, team and billing.
Dashboardfieldhand.dev/app. The fleet, each device's page and the browser terminal.

Why it works on any network

The device only makes outbound HTTPS connections on port 443, the same traffic as a web browser. That gets through home routers, carrier-grade NAT on 4G and 5G, hotel Wi-Fi and most corporate firewalls. Nothing listens on the device, so there is no port for anyone to scan.

Cellular carriers silently drop idle connections, each after a different amount of time. The agent learns how long the link can stay quiet and sends a heartbeat just before that, between every 30 seconds and every 10 minutes. On metered links, that keeps data use low.

Next

Install the agent on one device, or enroll a whole fleet from your image.

Something wrong or missing on this page? Tell us.