Show HN: Beacon CLI for self-hosted monitoring, remote access and deployments

[matebajusz]

I've been building a cli for my homelab/self-hosted setup. The original motivation was getting tired of stitching together deployments, monitoring, remote SSH access and random scripts. It’s a open source CLI, all-in-one tool for monitoring, secure remote accces (tunnel and terminal), log forwarding, automated deployments. No exposed ports, or endpoint, everything is configurable how the user wants it. One use case that multiple friends are interested in is replacing HomeAssistant’s Nabu Casa subscription with tunneling through BeaconInfra. The cloud/control-plane part (BeaconInfra) is optional. The agent itself is intended to stay local-first and continue functioning offline. Example CLI output:

⬡ beacon 0.5.2 ● master running uptime 29d 14h

DEVICE bajszi-MINI-S amd64 Ubuntu 25.04

PROJECTS 2 healthy 0 warning 0 down

  ● beaconinfra        1/1 checks passing
  ● mestertkeresek     1/1 checks passing

TUNNELS

  ● homeassistant      connected

[amjadfatmi1]

Wait, so the agent keeps state without the control plane? How do you handle conflicts if you toggle between local CLI and cloud management without split-brain?

[matebajusz]

I have an AI edited demo video to show how it works: https://www.youtube.com/watch?v=DIJJnyiKZdE