r/ComputerSecurity • u/4ppd3ck • 10h ago
I built a local-first app launcher in Go (single executable, no Electron) and it now runs my privacy dashboard, watchdog, and disk tools
I got tired of every tool wanting an account, a cloud dashboard and a background service, so I wrote my own launcher. It's Go, standard library only, and in release form it's one executable that carries every app inside it and opens its own window.
The idea: an app is just a folder with a json manifest next to its entrypoint. Drop the folder in, it gets a card on one dashboard. Go apps compile on first start, Python apps get a venv, static pages get hosted in-process. The import button takes archives, DMGs, portable binaries, AppImages, git repos or plain URLs, and generates a manifest if there isn't one. Everything gets scanned before it lands, and apps bind to loopback only unless you explicitly flip one to Wi-Fi sharing.
A few tools I built on top of it:
- wTower: live view of which apps use the camera/mic and which are talking to the internet, with blocking
- wHawk: a host watchdog that checks for RATs, rogue listeners and persistence every 15 seconds and never makes an internet connection itself
- wLens: GitHub search that looks for actual runnable installers in releases and counts real downloads instead of stars
- wGauge: a disk space explorer with sunburst/treemap views
- wPurge: a cleanup/uninstaller where everything goes to the trash and every session is restorable
- wGrid: a local intel feed of known provider IP ranges the other two consume
Everything stays on the machine, nothing phones home. Happy to go into the architecture in the comments — the constraint I set myself was stdlib-only, no Electron, no Node.