Solid framing around sovereign infrastructure — the "Cloud Tax"
argument is one most developers feel but rarely articulate this
clearly.
The container isolation point is exactly what we found critical
when building WAB (Web Agent Bridge). Agents interacting with
live websites need more than OS-level sandboxing — they need
governed execution boundaries too.
What ended up mattering most in production:
- child_process.fork() isolation with hard memory limits
- Deterministic event sourcing — replay from any checkpoint
when something fails at 3am - Queue backends: SQLite for local-first, Redis/BullMQ when
scaling - Governance Layer: permission boundaries, spend caps, kill
switch — so the agent literally cannot exceed what you
defined, even unsupervised
The Ollama integration was the piece that made it fully
sovereign — zero cloud dependency, agent runs entirely on
local metal with local inference.
Curious how you handle memory limits across concurrent
containers when running multiple automation scripts in parallel —
VRAM partitioning at the Docker level or further down?
github.com/abokenan444/web-agent-bridge