HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
Bajusz15
beacon
Go2025–2026
Bajusz15 / beacon

beacon

Open-source agent for secure remote access, monitoring, and deploys across home-lab and self-hosted machines like Raspberry Pi, N100, or any Linux server. Open web based TTY or tunnel Home Assistant and other local services securely without opening ports.

2Distinct people
5Mentions
0Explicit recommenders
21GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Open-source agent for secure remote access, monitoring, and deploys across home-lab and self-hosted machines like Raspberry Pi, N100, or any Linux server. Open web based TTY or tunnel Home Assistant and other local services securely without opening ports.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 3:56:07 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by month5 dated mentions

Observed mentions: 2025-09-26 18:48:39 UTC to 2026-05-28 14:12:32 UTC.

0122025-09-01 00:00:00 UTC to 2025-10-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 commentsSep 20252025-10-01 00:00:00 UTC to 2025-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-11-01 00:00:00 UTC to 2025-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2025-12-01 00:00:00 UTC to 2026-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-01 00:00:00 UTC to 2026-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJan 20262026-02-01 00:00:00 UTC to 2026-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-01 00:00:00 UTC to 2026-04-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-04-01 00:00:00 UTC to 2026-05-01 00:00:00 UTC (exclusive): 2 mentions; 1 submissions, 1 comments2026-05-01 00:00:00 UTC to 2026-06-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsMay 2026

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Sep 20252025-09-01 00:00:00 UTC2025-10-01 00:00:00 UTC211
Oct 20252025-10-01 00:00:00 UTC2025-11-01 00:00:00 UTC000
Nov 20252025-11-01 00:00:00 UTC2025-12-01 00:00:00 UTC000
Dec 20252025-12-01 00:00:00 UTC2026-01-01 00:00:00 UTC000
Jan 20262026-01-01 00:00:00 UTC2026-02-01 00:00:00 UTC000
Feb 20262026-02-01 00:00:00 UTC2026-03-01 00:00:00 UTC000
Mar 20262026-03-01 00:00:00 UTC2026-04-01 00:00:00 UTC000
Apr 20262026-04-01 00:00:00 UTC2026-05-01 00:00:00 UTC211
May 20262026-05-01 00:00:00 UTC2026-06-01 00:00:00 UTC110

What Hacker News says

5 sources

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

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 ● beaconin
Read the rest
fra 1/1 checks passing ● mestertkeresek 1/1 checks passing TUNNELS ● homeassistant connected
7 points · Open discussion
I've been hosting one of my side projects on AWS. The project actually did quite well for a while, generating a few thousand euros per month. Then COVID hit, regulations changed, and the problem it solved basically disappeared overnight. Revenue dropped to zero, the startup credits I received held out for quite some time, after that I kept the project running, paying out of pocket, thinking maybe it would recover. The hosting costs were reasonable for my salary. Then one day, after ignoring a few AWS emails, I got hit with a charge on my card that was orders of magnitude higher than usual. "WTF?" I logged in immediately to investigate. No DDoS. No misconfiguration. Then I checked the billing page: *RDS PostgreSQL “legacy fee” — ~€200* for March Apparently, I hadn’t upgraded from Postgres 13 to 16. That was it. I had been paying ~€25/month
Read the rest
for RDS, and suddenly there’s a €200 charge for essentially… not upgrading. That was the moment it clicked for me: Why am I running this in the cloud? I had a spare Raspberry Pi at home. For my use case, I just needed something that runs reliably. So I moved everything to self-hosting. And immediately ran into a different set of problems: Deployments were manual (SSH → pull → restart). Debugging required logging into the machine every time. Monitoring (Prometheus/Grafana) was too heavy for small devices. So I started building a small agent for myself. It began as a deployment tool, but gradually evolved into something more: - deploy apps from GitHub or Docker automatically - self-healing processes with restart logic - system metrics + lightweight monitoring - *heartbeats so I know if a device/service is actually alive* - *log forwarding so I don’t have to SSH in to debug* - reverse tunnels (I use it for Home Assistant instead of Nabu Casa) - remote terminal access from the browser I named it Beacon. It’s open source, and I’ve been running it for the last ~8 months. Everything runs locally on the device (Pi, mini PC, etc.) but there is an optional beaconinfra.dev integration — mainly for monitoring, Home Assistant (or other local app) tunnel, and remote access. I host beaconinfra myself too, and since then I moved away from the Pi to an N100. Repo: https://github.com/Bajusz15/beacon
In Show HN: Remote Access for Home Assistant Without Nabu Casa

Show HN: Beacon – Lightweight deployment and monitoring for self hosters

Hi HN, I've been hosting my side project on AWS, like any developer who is also a hustler would. I was paying an okay price for not managing infrastructure at all. I moved everything to AWS Ligthsail after my startup credits run out. My project was not making me much money, so I financed it all by myself. Then one day, after some ignored spam AWS emails, I got a huge bill. 700% increase from previous period. WTF?? I said to myself while I logged into the dashboard to look at what the issue is. No DDOS, misconfiguration, nothing unusual. I log into the root account to look at the billing page, and I see it: RDS PostgreSQLl legacy fee ~200 EUR because I was running Postgres 13 in 2025. I was baffled. I paid monthly 25 eur (with 27% tax) for the smallest RDS instance, then I see this monster fee for something I think should cost maybe 2 EU
Read the rest
R. I mean AWS just has to run it in a different environment. For 200 I could buy them a new server to run it for me. I thought to myself, I have a spare Raspberry Pi 3, I will just host it on that. Then my journey on self hosting started, I decided to cut ties with AWS or any cloud provider. I faced many challenges, particularly due to resource constraints with the tiny 1GB ram and slow storage. Then to solve my own problems I made Beacon, and I'm sharing it now to help others who face similar challenges. Beacon solves a problem for self-hosters (or if you host on bare metal), IoT homelab users. It's an open-source agent that makes it easy to deploy apps and monitor devices (like Raspberry Pi) without the overhead of traditional tooling. Forget bloated stacks like Jenkins, Opensearch, Grafana, or Datadog. Beacon is a single ~15 MB Go binary that: * Automatically deploys new releases from Git tags * Monitors endpoints, ports, and system metrics with custom commands * Forwards logs from files, Docker, and commands Note: Beacon is currently in Beta development — APIs, configs, and features may change as it evolves. Feedback and contributions are welcome!
3 points · Open discussion
Beacon solves a problem for self-hosters, homelab users. It's an open-source agent that makes it easy to deploy apps and monitor devices (like Raspberry Pi) without the overhead of traditional tooling. Forget bloated stacks like Jenkins, Opensearch, Grafana, or Datadog — Beacon is a single ~15 MB Go binary that: * Automatically deploys new releases from Git tags * Monitors endpoints, ports, and system metrics with custom commands * Forwards logs from files, Docker, and commands Note: Beacon is currently in Beta — APIs, configs, and features may change as it evolves. Feedback and contributions are welcome! Source: https://github.com/Bajusz15/beacon
In [dead]

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.