Armorer – A secure local control plane to sandbox AI agents in Docker
Docker sandboxing for agents when most runners just trust whatever the LLM outputs.
Local control plane for running AI agents with sandboxes, approvals, guardrails, credentials, and runtime health.
Agents install their own sandbox via Docker, solving the dependency hell problem.
Developers running multiple AI coding agents locally
Docker Desktop · DevPod · GitHub Codespaces
I built Armorer because I was tired of two things: 1. The absolute "dependency hell" of setting up new AI agents (Codex, OpenClaw, etc.). 2. The security risk of giving powerful local agents broad access to my host machine.
Armorer is a secure local control plane that manages the lifecycle of your agents. It uses Docker for true process isolation and provides a unified UI/CLI for monitoring and job tracking.
One feature I’m particularly excited about: you can point an existing coding agent at the Armorer repo, and it will autonomously install and configure the entire stack for you securely.
Source: https://github.com/ArmorerLabs/Armorer Website: https://armorerlabs.com
I’d love to hear your thoughts on the architecture and how you're handling agent security locally.
Docker sandboxing for agents when most runners just trust whatever the LLM outputs.
Firecracker microVMs isolate coding agents so you can review before merging.
Replaying past sessions against stricter policies beats guessing rules before you know the risks.
170× denser than vanilla K8s by sharing one apiserver across thousands of isolated control planes.
OPA-based policy engine for AI agents blocking injection and tool abuse.
Portainer alternative keeping compose files on disk with outbound-only agent connectivity.