From the Thinger.io team · ThinRemote
Reach any Linux device in the field, without opening a port
ThinRemote is the remote access and monitoring service from the Thinger.io team. A terminal, files, tunnels and the desktop of every distributed device, over one outbound connection.
The problem
The data arrives. The device stays out of reach.
A gateway stops forwarding, a kiosk freezes, a controller needs a new config file. Someone has to get in without exposing the network.
09:12edge-gw-017 stopped forwarding data
- 09:20SSH to its addressTimed out
$ ssh admin@10.20.4.17 · Connection timed outBehind the site’s NAT, no inbound port - 09:35VPN into the site networkPending
Ticket IT-4821 · assigned to site ITWaiting on another team’s queue - 10:10Port forward on the routerRejected
Forward :2222 → 10.20.4.17:22Firewall policy: no inbound rules - 10:25Drive to Pump station 42 h 40 min
Leave 10:25 · on site 13:05One restart, once someone is there
Without data3 h 53 min09:12 → 13:05
Every way in depends on the site’s network, and the last one on a car
root@edge-gw-017:~#systemctl status gateway
× gateway.service - Data forwarder
Active: failed since 09:12:04
root@edge-gw-017:~#systemctl restart gateway
root@edge-gw-017:~#systemctl is-active gateway
active
root@edge-gw-017:~#
Data flowing again09:16
Without data4 min09:12 → 09:16
Fixed from the desk, over the connection the agent keeps open
Same gateway, same fault. Minutes instead of a drive.
What it does
Everything you would do on site, from where you are
Every tool rides the connection the agent already keeps open, so adding one never means opening another port.
A shell on the device
An interactive shell on any device, in the browser or from the CLI. No SSH port open, no VPN to set up first.
thinr device <id> console
The filesystem, in the browser
Browse, upload, download and edit files on the device, without an FTP or SFTP server to install and keep patched.
WEB CONSOLE · BROWSE · TRANSFER · EDIT
Local services, as if you were there
Reach what only listens on the device or its network, like a Node-RED editor, a database or a router page, on your own machine.
thinr device <id> tcp | http <port>
The graphical desktop
The full desktop of the device in a browser tab, for the applications and admin tasks that have no command line.
WEB CONSOLE · VNC
One command, no session
Run a command and get its output without opening a shell, from the console or a script, one device or a tagged group.
thinr device <id> exec "..."
Health before anyone drives out
CPU, memory, disk and network in real time, logs to inspect, and alerts on system metrics or events.
METRICS · LOGS · ALERTS
How it works
The device dials out, you step in
The agent calls the service, never the other way round, and every session you open rides on that call.
Local services
Shell, files, local ports and the desktop stay where they are, unexposed.
Agent
A static binary under 10 MB, set up as a service by one script. It dials out over the HTTPS port and reconnects on its own.
No inbound ports
One connection
Opened by the agent, IOTMP over TLS. Terminal, files, tunnels, desktop and metrics all share it, and the firewall stays shut to inbound traffic.
ThinRemote
Signs in every user and applies role based access per project, centrally.
Operator
The web console, the thinr CLI, or an AI agent through the MCP server in the CLI.
EVERY DEVICE WITHIN REACH
Thinger.io and IOTMP
Same team, same protocol
ThinRemote runs on the IOTMP Linux client that Thinger.io devices speak. Thinger.io raises the alert, ThinRemote is how you step in.
Thinger.io
- MonitorTelemetry, dashboards and buckets for the fleet.
- DetectAn alarm rule flags the device that needs attention.
ThinRemote
- InterveneA terminal, files or a tunnel into that device.
- ResolveFix it in place and watch it report healthy again.
ThinRemote also works on its own, for teams that only need remote access. Bringing devices into Thinger.io is covered in Device Connectivity.
Who it is for
For equipment nobody wants to visit
If it runs Linux and is expensive to reach, it is a candidate.
Industrial control and automation
PLCs, HMIs and controllers behind plant firewalls, updated without touching the network.
Way inFilesTerminal
Edge gateways
Node-RED, data aggregation or local inference, reachable on demand on small hardware.
Way inTunnelsTerminal
Kiosks, signage and self-service
Unattended screens and terminals that freeze, fixed without sending a technician.
Way inDesktopCommands
Equipment vendors and OEMs
Support for machines at customer sites, with a role based portal for the customer.
Way inCustomer portalRoles
Servers behind firewalls
Lab machines and private subnets, with no reverse proxy or static IP.
Way inTerminalTunnels
Response on alerts
When monitoring fires, go straight into the machine instead of opening a VPN ticket.
Way inAlertsTerminal
The agent
One agent under 10 MB, for every Linux device above
The blue mark on each drawing, dialing out to ThinRemote
- Size
- Under 10 MB
- Binary
- Statically linked
- Setup
- One script, as a service
- Link
- Outbound, IOTMP over TLS
Built for
- x86_64
- ARM64
- ARMv7
- ARMv6
- MIPS
- And more
Go deeper
Read more about ThinRemote
The product site, the guides, and the story behind the protocol.
ThinRemote sitesNew tab
Next step
Put your field devices one click away
See ThinRemote on its own site, or read how the IOTMP protocol underneath it works.