I built a browser shell for Linux devices stuck behind 4G/CGNAT. How do you reach yours today?
I'm Abner, solo developer in Brazil. Fieldhand gives you a shell in the browser, health data and fleet commands for Linux devices already in the field: kiosks, signage, lockers, gateways on 4G.
Those devices sit behind CGNAT and customer firewalls, so nothing can connect in. The agent is one static Go binary that dials a single WebSocket over TLS on 443. You install it on the OS that's already there, no reflash.
- Real PTY shells that survive 2-minute drops
- CPU, disk, temperature, offline alerts (email, Slack, Discord, webhooks)
- Fleet commands in waves, with canaries and a stop on failure rate
- Agent, CLI and protocol are open source (Apache-2.0)
Free for 5 devices, then $1.50 per device that connected that month. Not self-hostable, no Windows/macOS.
Live read-only demo, no sign-up: https://www.producthunt.com/products/fieldhand?launch=fieldhand
If you run devices on networks you don't control: what do you use to get a shell on them now, and what breaks?
Replies
Be the first to reply
Have a question or a thought to share? Add a comment above to start the conversation.