Quick Start¶

Get a server running, pair it, and run your first scan. This is the short path; Install & Pair has every platform and option.

1. Get a server running¶

Docker (most platforms):

gunzip -c raven-pro-*.tar.gz | docker load
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>

No license key

Single-user Raven Pro has no LICENSE_KEY — don't set one. Access is granted by pairing with your Chamber Door account in step 3. (If an older note told you to set LICENSE_KEY and the container restart-loops with "License validation failed", you're on an old image — pull the latest tarball.)

Bare binary (Kali — toolchain already installed):

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

2. Open the dashboard¶

Browse to http://localhost:8080. The server binds loopback by default; for a remote/VM host use an SSH tunnel:

ssh -L 8080:127.0.0.1:8080 user@host

3. Pair the device (enables AI)¶

Click Pair this device in the dashboard, or run:

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

Confirm in the browser at the printed URL. Pairing is one-time per machine; the token is saved under your mounted auth/ volume (or ~/.raven/).

4. Create an engagement and scan¶

In the web UI: New Engagement → name your client → run a module (e.g. an nmap profile) from Tools → Modules. Results auto-parse into hosts and findings.

5. Ask the AI¶

Tools → AI Analysis. Ask it to review your current engagement state and suggest next steps. Your data is anonymized before it's sent; the response comes back and is de-anonymized on your machine, so real host and IP names never leave the binary.

Next: CLI / REPL to drive all of this from the terminal, or AI Analysis for the advisor in depth.