System Architecture

A high-level overview of the **HITL** microservices architecture and data flow.

Design Philosophy

Air-Gap First

Every component is designed to run without internet access. Models are embedded locally.

Zero Trust

Strict mTLS communication between containers. No privileged containers by default.

Container Diagram

[ Browser ] <---> [ NGINX Reverse Proxy (TLS 1.3) ]
                           |
        +------------------+------------------+
        |                                     |
[ Next.js Frontend ]                [ Django REST API ]
                                              |
                                     (Celery Task Queue)
                                              |
                          +-------------------+-------------------+
                          |                   |                   |
                  [ Recon Agent ]     [ Exploit Agent ]    [ Report Agent ]
                          |                   |                   |
                          +---------+---------+-------------------+
                                    |
                            [ Redis / PostgreSQL ]
                                    |
                            [ Vector Database ]

Data Flow

  1. Initiation: User submits a target scope via the Dashboard.
  2. Orchestration: The Task Coordinator breaks the objective into atomic sub-tasks (e.g., "Scan Ports", "Crawl JS").
  3. Execution: Agents pick up tasks from RabbitMQ/Redis. The Recon Agent utilizes tools like Nmap/Nuclei.
  4. Analysis: Output is fed into the LLM Context Window. The **Logic Analyzer** looks for anomalies.
  5. Verification: If a potential vuln is found, the Exploit Agent spins up a sandbox to attempt a safe reproduction.
  6. Reporting: Verified findings are written to PostgreSQL and pushed to the frontend via WebSockets.