Skip to content

Architecture

How the eight tatara components fit together, how data flows through the system, and the key design decisions that shape the platform.

  • Data & Control Flow

    From GitHub webhook to merged PR: request paths, state transitions, and the full lifecycle of a task.

    Data Flow

  • Identity & OIDC

    Keycloak realm, OIDC clients, token validation, and the agent pod authentication flow.

    Identity & OIDC

  • Memory Architecture

    LightRAG + Neo4j + Postgres: how the knowledge graph is built, queried, and kept durable.

    Memory Architecture

  • Agent Execution

    How the operator spawns and drives Claude Code wrapper pods, and how turns flow.

    Agent Execution

  • CI/CD & Deploy Model

    tatara-helmfile, component CI, ARC runners, and why kubectl set-image is forbidden.

    CI/CD & Deploy

Component overview

graph LR
    A[GitHub / GitLab] -->|HMAC webhook| B[tatara-operator]
    B -->|spawns| C[tatara-claude-code-wrapper pod]
    C -->|MCP stdio| D[tatara-cli]
    D -->|REST + OIDC| E[tatara-memory]
    E --> F[(LightRAG)]
    E --> G[(Neo4j)]
    E --> H[(CNPG Postgres)]
    B -->|ingest Jobs| I[tatara-memory-repo-ingester]
    I -->|REST| E
    J[Grafana alerts] -->|alert webhook| B
    K[tatara-observability] -->|terraform apply| J
    L[Component repo CI] -->|builds images+charts| M[Harbor OCI]
    M -->|helmfile pulls| N[tatara-helmfile]
    N -->|GitOps deploy| B
    C -->|chat rooms| O[tatara-chat]

For per-component detail, see the Components section.