// REGULATED TEAMS
Self-hosted offensive security with privacy guardrails
Deploy inside your perimeter, block data-training LLM providers by default in production, and map findings to frameworks — mapping only, not certification.
Self-hosted deployment
Docker Compose stack: Postgres 16, Redis 7, vex-raptor API, and ARQ worker — on your infrastructure. Paid plans (Pilot and above) run entirely in your perimeter.
Data sovereignty & BYO-LLM
Self-hosted deployment with a privacy guard that blocks data-training LLM providers by default in production — pair with Ollama and disable external integrations for a fully closed perimeter. Eval runs on the hosted console; cloud LLM, threat intel, and OOB callbacks need explicit configuration and have different data boundaries.
Compliance mapping
Findings map to SOC 2 TSC, PCI-DSS v4, ISO 27001 Annex A, GDPR Art. 32, and OWASP API Top 10, with a per-control PASS/WARN/FAIL posture indicator based on detected violations — for audit prep and gap analysis. This is not a formal certification, attestation, or third-party audit opinion.
# docker-compose.yml services: postgres: image: postgres:16-alpine redis: image: redis:7-alpine vex-raptor: image: vex-raptor:latest ports: ["8000:8000"] worker: image: vex-raptor:latest command: arq src.arq_worker.WorkerSettings
Is mapping certification?
No. Compliance mapping groups findings by framework control and shows a PASS/WARN/FAIL posture indicator per control based on detected violations — useful for audit prep and gap analysis. It is not a formal certification, attestation, or third-party audit opinion, and Vex Raptor is not a certified auditor.