Your Lab.
Private AI.
Your Call.
ArgoBox is optimizing for homelabbers first.
One canonical stack. Approval-first agents. No blind trust.
Why Self-Host with ArgoBox
Your Hardware, Your Rules
Deploy on your own Proxmox, Docker, Unraid, or other approved targets. The point is control, not SaaS dependence.
Approval-First AI
Agents do not get blind shell trust. Mutations hit an approval queue, safe reads stay bounded, and everything is logged.
Built for Tinkerers
The stack is still hackable, but the public promise is one canonical homelab path first, not a grab bag of disconnected modules.
Real Operator Workflow
Hermes routes work, ArgoBox enforces policy, OpenClaw asks for actions, and you stay in control of privileged changes.
What Ships First
This is the current wedge, in plain terms.
The Stack
The control plane, runtime, and automation substrate being hardened first.
Approval queue, capability gating, and audit trail for agent actions
Decides what should execute, what stays read-only, and what needs approval
Requests actions through ArgoBox instead of receiving direct infrastructure trust
Canonical home automation layer for the homelab-first wedge
The real systems ArgoBox coordinates once you wire the adapters
Mesh access across nodes without exposing raw admin endpoints publicly
Try It Now
Real labs if you want them, but the main proof is a boring operator loop you can trust.
Ready to Ditch the Cloud?
Start with the supported path. Evaluate the trust boundary before you evaluate the breadth.