DrowAI
Product Demo Use Cases Roadmap Docs View on GitHub

User guide

DrowAI user guide

Product documentation for installing DrowAI, setting up Runner services, and understanding the main workspaces. Use it as a practical reference before running the application or preparing a task workflow.

Setup

Installation

Download MD

Choose a DrowAI deployment or local development path and prepare its prerequisites.

Install with AI:

DrowAI has two Docker deployment models and a local contributor setup. All three use the same control-channel architecture: Management owns the UI, API, database, and task coordination, while a Runner starts the isolated Kali task containers and executes runtime work.

Choose the path that matches where and why you are running DrowAI.

These paths are intended for evaluation, testing, and development. They are not hardened, internet-facing production configurations.

Docker deployment prerequisites

Standalone and Distributed hosts need:

  • A supported Linux installation on x86_64/amd64 or arm64/aarch64.
  • Docker Engine with the Docker Compose v2 plugin.
  • Permission to access the Docker daemon.
  • Internet access while images and dependencies are downloaded.

Check Docker before continuing:

docker --version
docker compose version
docker info

The Management host also needs Git to download the DrowAI repository. A Distributed Runner host does not need the full repository; it receives a self-contained package from Management.

You do not create a .env file, database, JWT secret, encryption key, or Runner token. DrowAI generates and stores deployment secrets during startup and the browser setup wizard.

Choose a path

Use Standalone installation when evaluating DrowAI on one Linux host.

Use Distributed installation when Management and Runner services should run on separate Linux hosts.

Use Local development when contributing to DrowAI or testing the backend, managed Runner, and frontend together from a source checkout.

Use Installation troubleshooting after a setup starts but the UI, Runner registration, or Runner readiness does not behave as expected.

Image preview