Start here (B2B customers)¶
This documentation is written for organizations that use Vex Raptor as a product: your team logs into the console, runs authorized pentests, and delivers reports to stakeholders. If you install and operate the platform yourself, skip to Self-host quickstart when you need infrastructure steps.
Who this is for¶
| You are… | Start with |
|---|---|
| Security engineer / pentester | First scan (tutorial) → Console guide |
| Org admin (users, keys, integrations) | For org admins |
| New teammate | Use the hosted console → Console tour |
Partners running many customer orgs (MSSP) have a separate path — we will expand that later; see Multi-org & MSSP if you already operate in that mode.
Your first week (recommended order)¶
- Access — Use the hosted console (login, sidebar, plan limits).
- Authorize targets — Verify domain ownership for external production URLs.
- Run work — First scan (tutorial), then Run scans (Pentest) as field reference.
- Deliver — Results & reports · Read a report.
- Govern — Responsible use · Plans & features.
What you can do in the console (by menu)¶
The Console guide mirrors the product sidebar:
- Home — Dashboard
- Test — Pentest, Internal exposure, Swarm (beta, plan-gated)
- Protect — Surface Monitor, Threat intelligence, CI Gate
- Prove — Reports, Compliance
- Administration — Organization, Integrations, Sense Fleet, branding, health, etc.
Not everything appears for every plan or role. Check the Availability box at the top of each guide and Plans & features.
What is not in the console (but exists in the product)¶
- Scheduled scans — API only (Scheduled scans (API)), Essential+ plan.
- Deep automation — API, Webhooks, CI Gate.
When something goes wrong¶
Language¶
Core customer pages are available in English and Spanish. Some advanced reference and operations pages may appear in English until translated.