> ## Documentation Index > Fetch the complete documentation index at: https://docs.d0pam1ne.blackhatethicalhacking.com/llms.txt > Use this file to discover all available pages before exploring further. # Free engine and Pro > What the open-source D0pam1ne engine gives you for free, and what D0pam1ne Pro adds on top. D0pam1ne comes in two parts. The **engine** is open source and free. **D0pam1ne Pro** is the multi-user web application built on top of it. You can run the engine on its own from the terminal, or run Pro to get the full workspace. ## The free engine The open-source engine is a complete reconnaissance and attack-planning toolchain, driven by the `d0pam1ne` CLI. For free, you get: > **Full recon pipeline** > > All fifteen [recon stages](/engine/recon-pipeline.md): subdomains, DNS, ports, services, live web, TLS, fingerprinting, screenshots, URLs, content, parameters and JavaScript secrets. > **Profiles and scope** > > The [fast, stealth, normal and deep profiles](/engine/profiles.md), and a strict [scope guard](/concepts/scope.md) with domains, wildcards, IPs, ranges and path-limited rules. > **The whole toolchain** > > One registry that installs and manages every recon tool, with `d0pam1ne doctor`, `tools install` and SecLists [wordlists](/tools/wordlists.md). > **Attack planning** > > `d0pam1ne attack` builds the in-scope target lists and the exact, tested commands for each [attack category](/attacks/categories.md), ready to run by hand. Nothing runs automatically. > **The full CLI** > > Projects, runs, results, pause and resume, export, the [complete CLI](/engine/cli-reference.md). > **Reports of a run** > > `d0pam1ne report` renders a one-page HTML summary of any run. ## What Pro adds D0pam1ne Pro wraps the engine in a multi-user web app and adds the orchestration and workflow a team needs: | Capability | Free engine | D0pam1ne Pro | | - | - | - | | Recon pipeline and tools | Yes | Yes | | Attack planning (targets and commands) | Yes | Yes | | **Automated attacks** (runs the tools, stage by stage) | Manual only | **Yes** | | **OSINT** (ASN, people, exposed assets, dorks, breach) | No | **Yes** | | **Evasive Mode** (adaptive pacing, Tor) | Recon pacing | **Full, recon and attacks** | | Web workspace, projects, triage, Needs Review | No | **Yes** | | Local AI (triage, drafting, assistant) | No | **Yes** | | Manual attacks (guided, per category) | Commands only | **Yes** | | Vulnerability intelligence (CVEs, exploits, KEV) | No | **Yes** | | Issues, AI triage and Needs Review | No | **Yes** | | Client reporting (PDF, interactive HTML) | Run summary only | **Yes** | | Retest reports (fixed vs still open) | No | **Yes** | | Multi-user, roles, 2FA, audit log | No | **Yes** | That table is the short version. Pro is a full workspace, and there is a lot in it. Here is the longer answer. ### The War Room Pro is a self-hosted, multi-user web app: the [Command Center](/concepts/command-center.md) holds every client and [project](/concepts/projects.md) in one view, and the whole team works the same engagement at once with roles, two-factor login and a full audit log. > **[Command Center](/concepts/command-center.md)** > > Every client, project and run in one place, with status and progress at a glance. > **[Projects and scope](/concepts/projects.md)** > > The same strict scope guard as the engine, managed visually, shared across the team. ### Project Data: everything recon and OSINT find, in one place Instead of folders of text, Pro files every finding into a live, searchable workspace that cross-links as it fills. > **[Hosts and services](/data/hosts-and-services.md)** > > Every in-scope host, its names, ports, services and technologies. > **[Attack-surface graph](/data/attack-surface.md)** > > The whole surface as a graph: how hosts, names and services connect. > **[Traffic log](/data/traffic.md)** > > Every request and response the platform made, kept for evidence. > **[Out of scope](/data/out-of-scope.md)** > > Everything seen but never probed, with the reason it was refused. ### Attacks that actually run The engine prepares the commands; Pro runs them for you, stage by stage, under a single intrusive opt-in, and paces them with Evasive Mode when recon saw a WAF. > **[Automated Attacks](/attacks/automated-attacks.md)** > > Pro runs each [attack category](/attacks/categories.md) against the in-scope targets recon found, filing findings as it goes. One of the most-loved parts of the platform. > **[Manual Attacks](/attacks/manual-attacks.md)** > > The guided, per-category workflow for the testing you want to drive yourself. > **[The Attack Equalizer](/attacks/attack-equalizer.md)** > > Tune intensity, categories and pacing like a mixing board before you run. > **[Evasive Mode, in full](/evasion/overview.md)** > > Adaptive pacing and Tor egress across both recon and attacks, not just recon. ### OSINT A whole phase the free engine does not have: map public exposure before you touch the target. > **[OSINT](/osint/overview.md)** > > ASNs, people and emails, exposed assets, search-engine dorks, email-security posture, breach and infostealer data. Alongside Automated Attacks, the part that gets the most love. ### Triage, intelligence and a local AI > **[Issues and Needs Review](/data/issues.md)** > > Findings flow into a triage queue; AI suggests a verdict and you confirm, edit or reject. Only verified issues reach the client. > **[Local AI](/ai/local-ai.md)** > > An on-device model via Ollama for triage, report drafting and the Ask AI assistant. No cloud, no account, no telemetry. > **[AI memory](/ai/ai-memory.md)** > > The assistant remembers the engagement's context so its help stays relevant. > **[Vulnerability intel](/vuln-intel/overview.md)** > > Look up CVEs, exploits, advisories and CISA KEV known-exploited status, built in. ### Client-ready reporting > **[Report Builder](/reporting/report-builder.md)** > > One branded house design, a full per-finding anatomy, across every format. > **[PDF and interactive HTML](/reporting/pdf-report.md)** > > A polished [PDF](/reporting/pdf-report.md) and a live [interactive HTML](/reporting/interactive-report.md) report from the same findings. > **[Retests](/reporting/retest.md)** > > Re-run against verified findings and show the client what was fixed and what still stands. ### Administration Everything a team running real engagements needs to run the platform itself. > **[Team, roles and 2FA](/admin/team.md)** > > Invite the team, set roles, require two-factor login. > **[Audit log](/admin/audit-log.md)** > > Who did what, when, across the whole platform. > **[Backups and storage](/admin/backups.md)** > > Scheduled [backups](/admin/backups.md) and [storage](/admin/resources.md) you control. > **[Updates, keys and time](/admin/updates.md)** > > In-app [updates](/admin/updates.md), [API keys](/admin/api-keys.md) and a [time tracker](/admin/time-tracker.md). > [!NOTE] > > The things that get the most love, Automated Attacks and OSINT, live in Pro. The free engine is where the recon power and the toolchain come from, and it stands on its own. Everything above runs on infrastructure you control, with the AI on your own machine. See the [Support the project](/support.md) page for how to help keep the free engine growing. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.