This view zooms one level into the TalkIDE platform: which deployable units run, where they run, and how they talk to each other. “Container” is the C4 term — a runnable thing with its own lifecycle (process, pod, managed service). It is not specific to Docker.

For the physical DigitalOcean topology (clusters, ports, pools, volumes) see the dedicated infrastructure.md page.

flowchart TB
    Browser["End user's browser"]

    subgraph cp["K8s namespace: talkide (control-plane)"]
        FE["TalkIDE FE<br/>Vue 3 · Vite · nginx"]
        BE["TalkIDE BE<br/>Kotlin · Spring Boot · JVM 21<br/>incl. gateway-proxy"]
    end

    subgraph tenant["K8s namespace: {tenant}-{env} (per tenant-environment)"]
        WORKER["talkide-worker<br/>Node/TS · Anthropic Agent SDK<br/>(LIVE since 2026-05-21)"]
        UAPP["User-app pod<br/>Spring Boot + Vue static<br/>same-origin single pod"]
        JOBS["Ephemeral Jobs<br/>Kaniko image build · gradle build/test"]
    end

    subgraph do["DigitalOcean managed services"]
        PGA["Managed PG — cluster A<br/>talkide-prod-pg (control-plane)"]
        PGB["Managed PG — cluster B<br/>talkide-dataplane-pg (data-plane)"]
        SPACES["DO Spaces<br/>talkide-prod-space"]
        REG["Container Registry"]
    end

    NFS["NFS server pod<br/>per-project working tree + .git/"]

    Browser -->|"HTTPS"| FE
    Browser -->|"REST + SSE"| BE
    Browser -->|"{slug}/{uuid}.talkide.app"| UAPP

    FE -->|"/api"| BE
    BE -->|"control-plane DB (PgBouncer)"| PGA
    BE -->|"K8s API · provision"| WORKER
    BE -->|"K8s API · provision"| UAPP
    WORKER -->|"agent calls via gateway-proxy"| BE
    WORKER -->|"dispatch"| JOBS
    WORKER -->|"working tree"| NFS
    BE -->|"working tree"| NFS
    JOBS -->|"push image"| REG
    UAPP -->|"per-app schema (PgBouncer SCRAM)"| PGB
    UAPP -->|"uploads / generated"| SPACES

Containers in the TalkIDE platform namespace (talkide)

Containers per tenant-environment namespace (<tenant>-<env>)

DEV and PROD are two parallel deployments per project: preview (<uuid>) re-deploys with every build; published (<slug>) only on explicit Publish by the user. See cross-cutting-flows.md § Deploy lifecycle and ADR-022. Under ADR-026 these become explicit first-class Environments.

Managed services (DigitalOcean)

Cross-cutting concerns by container