Skip to content
PentAGI
Concepts

Architecture

The services PentAGI runs, how they talk to each other, and what is optional.

PentAGI is a set of Docker services. The core stack is enough to run flows; the knowledge graph and the observability stacks are optional add-ons.

System context

System context of PentAGI with its users, targets, LLM providers, search engines, monitoring and the update server

HTTPS

monitors

monitors

tests

queries

searches

reports

reports

checks for updates

Security engineer

PentAGI

Langfuse

Grafana

Target systems

LLM providers

Search engines

update.pentagi.com

Within two minutes of starting and then every three hours, PentAGI also checks update.pentagi.com for a newer build and sends a summary of the installation with the request; Update check lists what it contains and how to turn it off.

Services

GroupServicesCompose file
Corepentagi (Go backend with REST and GraphQL, React UI), pgvector (PostgreSQL with pgvector), pgexporter (PostgreSQL metrics), scraper (isolated browser)docker-compose.yml
Knowledge graphgraphiti, neo4jdocker-compose-graphiti.yml
LLM observabilitylangfuse-web, langfuse-worker, clickhouse, redis, minio, postgresdocker-compose-langfuse.yml
System observabilitygrafana, otel, victoriametrics, jaeger, clickstore, loki, node-exporter, cadvisordocker-compose-observability.yml

Tools never run inside the pentagi container itself: every flow gets its own sandbox container, built from an image picked for the flow's goal, such as Kali Linux.

Containers

Containers of the core stack and the optional knowledge graph

Knowledge graph

Core

HTTP/WS

telemetry

LLM traces

Web UI

Backend API

PostgreSQL + pgvector

Agents

Sandboxed tools

Isolated browser

Graphiti

Neo4j

OpenTelemetry

Langfuse

  • Backend API — Go, with REST and GraphQL and Bearer-token access for automation.
  • Vector store — PostgreSQL with pgvector keeps every command, output and embedding.
  • Agents — the multi-agent system that plans and executes the work; see Agents.
  • Sandbox — tool containers isolated from the host; in production they can live on a separate worker node.

Last updated on