Install & Pair¶

Raven runs as a server (web dashboard + engine) that you reach from a browser and/or the REPL. Pick the install that fits your environment, then pair the device once to enable AI.

Which build?¶

You are…	Use
On macOS / Windows / non-Kali Linux	Pro Docker — the Kali toolchain is bundled, nothing else to install
On Kali with the toolchain already installed	`raven-server` bare binary — skip the ~3 GB image

Download both from the Downloads page at app.chamberdoorsecurity.com (signed in).

Docker (macOS / Windows / Linux)¶

# 1. Load the image (note the tag it prints)
gunzip -c raven-pro-*.tar.gz | docker load     # Windows: docker load -i raven-pro-amd64.tar.gz

# 2. Workspace + run (replace <image-tag> with the tag from step 1)
mkdir -p ~/raven/pentests ~/raven/auth
docker run -d --name raven-pro --restart unless-stopped \
  -p 8080:8080 \
  -v ~/raven/pentests:/home/raven/pentests \
  -v ~/raven/auth:/home/raven/.raven \
  --cap-add=NET_RAW --cap-add=NET_ADMIN \
  <image-tag>

The two volumes keep your engagement data and pairing token on the host, so they survive upgrades.
--cap-add=NET_RAW --cap-add=NET_ADMIN is needed for SYN scans.
On Linux, if you're scanning the LAN you're on, you can swap -p 8080:8080 for --network host.

Bare binary (Kali only)¶

Only recommended on Kali (or another host with nmap, nuclei, etc. installed natively) — on other distros tool-using features silently fail.

chmod +x raven-server-linux-*
sudo mv raven-server-linux-* /usr/local/bin/raven-server
mkdir -p ~/raven/pentests
raven-server start -p 8080 --no-browser

The binary binds 127.0.0.1 by default (single-user "trust localhost"). Browse http://localhost:8080 on the same machine.

Reaching it from another machine

If the server is on a VM or remote host, don't expose it — use an SSH tunnel:

ssh -L 8080:127.0.0.1:8080 user@host

then browse http://localhost:8080 locally. Running the binary inside a container/VM and hitting its bridge IP (e.g. 172.17.0.x) works but is fragile; prefer the tunnel or a port-mapped Docker run.

First-time pairing (enables AI)¶

Pairing connects this device to your Chamber Door account. One-time per machine.

Web UI: open the dashboard → click Pair this device → confirm at the URL it shows.

CLI:

raven-server auth login                          # bare binary
docker exec -it raven-pro raven-server auth login   # Docker

It prints a URL + code; open it, confirm, and the token is saved automatically.

Verify:

raven-server auth status        # or: docker exec raven-pro raven-server auth status

You should see chamberdoor (account-bound, rvn_pat_). AI features now work.

Privacy¶

Engagement data is anonymized on your machine before it's sent to the AI proxy — hosts, domains, emails, and usernames are replaced with placeholders, and the response is mapped back to your real data locally. Chamber Door never sees raw engagement content, only anonymized snippets + account metadata.

Updating¶

When a new release drops, the dashboard shows an update banner.

Docker: load the new tarball, docker stop raven-pro && docker rm raven-pro, re-run with the new tag. Your pentests/ + auth/ volumes survive.
Bare binary: re-download from the Downloads page, chmod +x, replace /usr/local/bin/raven-server, restart. Your ~/.raven/ pairing survives.