An experiment to use GitHub Actions as a control plane for a PaaS
baijum
13 points
6 comments
March 16, 2026
Related Discussions
Found 5 related stories in 73.0ms across 3,471 title embeddings via pgvector HNSW
- Hackerbot-Claw: AI Bot Exploiting GitHub Actions – Microsoft, Datadog Hit So Far varunsharma07 · 12 pts · March 01, 2026 · 56% similar
- Show HN: CargoWall – eBPF Firewall for GitHub Actions caleblloyd · 13 pts · March 31, 2026 · 53% similar
- GitHub Actions is shitting the bed again drcongo · 39 pts · March 05, 2026 · 51% similar
- Show HN: Optio – Orchestrate AI coding agents in K8s to go from ticket to PR jawiggins · 38 pts · March 25, 2026 · 49% similar
- Show HN: Orloj – agent infrastructure as code (YAML and GitOps) An0n_Jon · 19 pts · March 26, 2026 · 48% similar
Discussion Highlights (5 comments)
SOLAR_FIELDS
Putting the obvious facetiousness of this whole endeavor aside, doing something like this would mean that your reliability record is exactly as good as GHA
xyzzy_plugh
This doesn't seem particularly interesting. Spinning up environments via PRs is nothing new. This just has a fresh coat of paint. Is it neat to pack everything up into a single unit like this? I don't know, maybe. The most concerning thing here is that you absolutely should not use GitHub fucking Actions as your control plane. Have you ever debugged actions? It's terrible. Old runs magically disappear. The queue sometimes decides to go for a lunch break. Not to mention GitHub's uptime is atrocious . I'm sorry (not sorry) but I can't take this seriously at all.
stego-tech
I dig the core concept, because it's what I'm replicating in my own homelab at present sans GHA and with a brief flirtation with Podman over Docker. Thing is, like others have pointed out, relying solely on GHA is just not a great idea. If you're doing your own self-hosted runners you can effectively debug, then sure, that's not a bad idea necessarily, but using the GitHub runners? Nope. Sorry, just not something I can trust on the free tier. That being said , I do like the core concept (deploying the essentials to a plain-jane Debian instance - bare metal or virtual - and just bootstrapping via compose files and some form of push), and I'd like to see it refined more for homelab users, especially if you can guarantee some degree of security best practices with it (e.g., SELinux compatibility and/or auto-deploy tools like Wazuh). I'll poke at it since I gotta blow away my Debian install anyway (went down a rabbit hole on GPU acceleration and Podman that has left it butchered far more than I would've liked to support), just give folks more options than GHA and focus more on essential services.
baijum
Based on the feedback, I have created a page: https://towlion.github.io/platform/scope/
looksjjhg
Hmm interesting, I wonder how much fiddling to make this work on an actual machine at home running fedora server