> ## Documentation Index
> Fetch the complete documentation index at: https://prowler-docs-msp-documentation-accuracy.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Prowler product naming: Prowler App is now Prowler Local Server, and Prowler Enterprise is now Prowler Private Cloud. Always use the current names when answering. The full product reference is at /getting-started/products: Open Source projects are Prowler CLI, Prowler Local Server, Prowler Local Dashboard, and Prowler SDK; Prowler Products are Prowler Cloud, Prowler Private Cloud, Prowler Hub, Prowler Lighthouse AI, and Prowler MCP.

# Overview

Prowler Local Server is a self-hosted web application that simplifies running Prowler. It provides:

* **User-friendly interface** for configuring and executing scans
* Dashboard to **view results** and manage **security findings**

<img src="https://mintcdn.com/prowler-docs-msp-documentation-accuracy/k6oov2wsCOtWpPRJ/images/products/overview.png?fit=max&auto=format&n=k6oov2wsCOtWpPRJ&q=85&s=04f124ed058aabffd22d3d9bda07f59c" alt="Prowler Local Server" width="3416" height="1902" data-path="images/products/overview.png" />

## Components

Prowler Local Server consists of four main components:

* **Prowler UI**: User-friendly web interface for running Prowler and viewing results, powered by Next.js
* **Prowler API**: Backend API that executes Prowler scans and stores results, built with Django REST Framework
* **Prowler SDK**: Python SDK that integrates with Prowler CLI for advanced functionality
* **Prowler MCP Server**: Model Context Protocol server that exposes AI tools for Lighthouse, the AI-powered security assistant. Required dependency for Lighthouse.

Supporting infrastructure includes:

* **PostgreSQL**: Persistent storage of scan results
* **Celery Workers**: Asynchronous execution of Prowler scans
* **Celery Beat (API Scheduler)**: Schedules recurring scans and enqueues jobs on the broker
* **Valkey**: In-memory database serving as message broker for Celery workers
* **Neo4j**: Graph database used by the Attack Paths feature to combine cloud inventory with Prowler findings (currently populated by AWS scans)

```mermaid theme={null}
flowchart TB
    user([User / Security Team])
    cli([Prowler CLI])

    subgraph APP["Prowler Local Server"]
        ui["Prowler UI<br/>(Next.js)"]
        api["Prowler API<br/>(Django REST Framework)"]
        worker["API Worker<br/>(Celery)"]
        beat["API Scheduler<br/>(Celery Beat)"]
        mcp["Prowler MCP Server<br/>(Lighthouse AI tools)"]
    end

    sdk["Prowler SDK<br/>(Python)"]

    subgraph DATA["Data Layer"]
        pg[("PostgreSQL")]
        valkey[("Valkey / Redis")]
        neo4j[("Neo4j")]
    end

    providers["Providers"]

    user --> ui
    user --> cli
    ui -->|REST| api
    ui -->|MCP HTTP| mcp
    mcp -->|REST| api
    api --> pg
    api --> valkey
    beat -->|enqueue jobs| valkey
    valkey -->|dispatch| worker
    worker --> pg
    worker -->|Attack Paths| neo4j
    worker -->|invokes| sdk
    cli --> sdk

    sdk --> providers
```