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.
Release files for armorer 0.1.14
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| armorer-0.1.14.tar.gz | 470.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| armorer-0.1.14-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.0 MB
Release files / armorer-0.1.14.tar.gz
| Download URL | armorer-0.1.14.tar.gz |
|---|---|
| Size | 470.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
c2231fe648b7dd594e13b4bbff957e70815f8614e8069d6e3173c588a83c5d5f
|
|
BLAKE2b-256 checksum How to use checksums |
004e40dfdb8678c7db7f853a71ec2866589b06e927745cc3f81599f6cda068b2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 12, 2026.
Transparency logRelease files / armorer-0.1.14-py3-none-any.whl
| Download URL | armorer-0.1.14-py3-none-any.whl |
|---|---|
| Size | 537.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1afe8887c5b749a03fe733bca8436e0b5a37887ce5f9bc2b6c3d1aaede5b197a
|
|
BLAKE2b-256 checksum How to use checksums |
f4e00eae765c7e3f95e2449fc068ffe2fac6bca0dad775775f7bad7d4905e172
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 12, 2026.
Transparency log