> For the complete documentation index, see [llms.txt](https://docs.alpha-security.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.alpha-security.app/readme.md). # Introduction Alpha records everything you run during a pentest and turns it into structured, searchable data that your whole team can use. You keep working the way you always do. Prefix your commands with `al run` or start an `al shell` session, and Alpha captures the output in the background. No special flags, no extra files, nothing changes about how your tools behave. If the server goes down, runs queue locally and sync later. The server parses output from 30+ common tools (nmap, netexec, impacket, nuclei, and more) into hosts, services, credentials, identities, and findings. Everything links together into a graph that shows what's connected to what. For tools Alpha doesn't know yet, the raw output is still stored and searchable. ## Who it's for Alpha is built for pentesters and red teams. It works just as well for one person on a single Kali box as it does for a team sharing findings across an engagement. ## Core ideas * **Your workflow doesn't change.** Alpha captures what you already do. It never modifies your commands or adds to your on-disk footprint. * **Nothing gets lost.** Raw output is stored for every command, parsed or not. You can always go back and search it. * **Everything traces back to evidence.** Every host, credential, and finding in the graph links to the exact command output that found it. * **Credentials are handled carefully.** Secrets are masked by default. Revealing them is an explicit action that gets logged. No silent bulk export. ## What's included * A **collector** (`al`) that runs on your testing machine and captures tool output * A **server** that stores evidence, runs parsers, and serves the API * A **web UI** with a dashboard, entity browser, graph, findings board, and reports * **30+ parsers** covering recon, enumeration, exploitation, and credential cracking tools * **Report generation** to Markdown, PDF, or SysReptor ## Getting started The fastest way to try Alpha is with Docker Compose. See [Quick Start](/getting-started/quickstart.md). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.alpha-security.app/readme.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.