
# ARTEX
**Autonomous penetration testing that keeps its receipts.**
(upstream: [Autumn-27/ARTEX](https://github.com/Autumn-27), AGPL-3.0)
Self-hosted multi-agent offensive security. A planner explores, workers run real tools,
and every finding stays bound to the assets and HTTP traffic that prove it.
[](https://github.com/BaaRai/ARTEX/releases)
[](LICENSE)
[](https://github.com/BaaRai/ARTEX/actions/workflows/ci.yml)
[](go.mod)
[Quick start](#quick-start) · [Screenshots](#screenshots) · [How it works](#how-it-works) · [Install](#installation) · [Configuration](#configuration) · [Security](SECURITY.md)
---
ARTEX is a self-hosted, LLM-driven penetration testing platform. It is not a chat wrapper around
a scanner: a planner splits a goal into intents, workers execute them with real tools, and the
results are written back into **two linked graphs**: one for what you know about the target, one
for how the test is progressing. Every finding can carry the captured request and response that
justify it, and every autonomous action passes through scope rules, approval gates and budgets.
- **It explores, it doesn't chat.** Goal decomposition, intent dispatch, worker execution and
write-back form a closed loop that keeps advancing until the goal is proven.
- **Two graphs, one audit trail.** The shared asset graph says *what exists*; the per-task
exploration graph says *what was tried, what it produced, and why*. Anchors link the two.
- **Findings with evidence.** A recording MITM proxy and a browser extension capture real traffic;
findings, evidence quotes and retests are tied to the exact request/response.
- **Autonomy with brakes.** Human-in-the-loop approvals, argv-prefix rules, scope/deny gates,
token and turn budgets, a target noise governor, and prompt-injection framing on tool output.
- **Self-hosted and model-agnostic.** One Go binary with the Next.js UI embedded, PostgreSQL,
your own Anthropic/OpenAI-compatible endpoint, or a local Ollama.
---
## Quick start
```bash
git clone https://github.com/BaaRai/ARTEX.git
cd ARTEX
cp .env.example .env # set POSTGRES_PASSWORD (and optionally an LLM key)
docker compose up -d --build # builds from this checkout, starts PostgreSQL
```
Open **http://localhost:8787**. On the first visit `/setup` asks for the one-time setup token
printed at startup:
```bash
docker compose logs artex | grep "Setup token"
```
> There is no prebuilt Docker image to pull: the image is always built from your checkout.
> For all installation paths (script, binaries, source, release archives), see [Installation](#installation).
---
## Screenshots
| Tasks | Findings |
| :---: | :---: |
|  |  |
| Task execution: sessions and tool calls | Exploration graph |
| :---: | :---: |
|  |  |
| Asset coverage graph | Traffic recording |
| :---: | :---: |
|  |  |
| Human-in-the-loop chat | Interception approvals |
| :---: | :---: |
|  |  |