armorer 0.1.11

A secure installer for agentic applications.

Armorer Labs

Run any agent. Securely.

Website · Install · Docs for humans · Issues

Armorer is the local control plane for running AI agents with sandboxes, approvals, guardrails, credentials, logs, and runtime health in one place.

Star ArmorerLabs/Armorer if you want safer local agent runtimes to exist.

---

One Command

curl -fsSL https://armorerlabs.com/install | sh

Then open the local UI and install agents like OpenClaw through Armorer.

Use Your Agent

Set up Armorer from https://github.com/ArmorerLabs/Armorer on this machine.
Follow AGENTS.md and the repository instructions.
Install Armorer, verify Docker, start the local UI, then help me install and configure OpenClaw through Armorer.
Do not report success until the Armorer CLI works, the UI is reachable, and runtime health checks pass.

Why Armorer

Running agents directly	Running agents through Armorer Labs
Each agent has its own setup path	One local control plane
Credentials are easy to scatter	Guided credential handling
Risky actions are hard to review	Human approvals and guardrails
Logs live wherever the agent puts them	Jobs, runtime status, and audit trails
Local networking gets messy	Local-first with optional private remote access

What Exists Today

• Local agent runtime and UI.
• Docker sandbox orchestration for installed agents.
• Guided setup for providers, models, credentials, channels, and skills.
• OpenClaw and NanoClaw as first-class managed agents.
• Guardrails for suspicious inputs, leaked credentials, and risky actions.
• Jobs, logs, runtime health, and setup state in one operator surface.

Humans

Prefer doing it yourself instead of handing the repo to an agent?

Start here: HUMANS.md

Positioning

Armorer Labs is not another model provider. It is not a hosted agent platform. It is a self-hosted, local-first agent runtime layer for builders who want control, sandboxing, and security posture before they scale agent usage.