# jitsi/docker-jitsi-meet architecture

> Architecture diagram of the GitHub repository jitsi/docker-jitsi-meet, generated by GitDiagram from its file tree, README and a sample of source files (last updated 2026-08-30). It is an AI-made overview: check details against the source.

- Interactive diagram: https://gitdiagram.com/jitsi/docker-jitsi-meet
- Repository: https://github.com/jitsi/docker-jitsi-meet

## Overview

#### Purpose and Entry Points
This repository builds and composes Docker images for a self-hosted Jitsi Meet videoconferencing deployment. The primary operational entry point is `docker-compose.yml`; operators supply environment-specific settings from `env.example` and may generate credentials with `gen-passwords.sh`. Optional Compose overlays enable features such as recording, SIP, observability, and whiteboarding.

#### Image Foundation and Runtime Model
A layered image hierarchy centralizes OS and Java dependencies: `base/Dockerfile` provides the shared Debian-oriented base, while `base-java/Dockerfile` adds the Java runtime required by Jitsi backend services. Each service image adds packaged software, defaults, and an s6-overlay process graph. The s6 config-generation stage is a key boundary: container environment is rendered into runtime configuration before service startup.

#### Browser Client and Edge Proxy
The web container is the client-facing HTTPS endpoint and static Jitsi Meet host, with Nginx routing browser traffic and supporting TLS/ACME renewal and optional JAAS provisioning. Core paths: `web/Dockerfile`, `web/rootfs/defaults/meet.conf`, and `web/rootfs/etc/s6-overlay/scripts/nginx`. Browser clients connect here, then establish signaling and media sessions with the internal Jitsi services.

#### XMPP Signaling and Identity
Prosody is the XMPP control plane: it authenticates service identities, hosts conference/brewery/visitor domains, and coordinates room presence. Its startup graph includes configuration, SASL authentication, optional registration setup, then Prosody itself. Core paths: `prosody/Dockerfile`, `prosody/rootfs/defaults/prosody.cfg.lua`, and `prosody/rootfs/defaults/conf.d/jitsi-meet.cfg.lua`. This is the principal signaling boundary between clients and Jicofo/JVB/Jigasi/Jibri service accounts.

#### Conference Orchestration and Media
Jicofo allocates and manages conferences based on XMPP state; JVB transports and bridges real-time audio/video among participants. Both are JVM services configured from defaults and supervised by s6. Core paths: `jicofo/Dockerfile`, `jicofo/rootfs/defaults/jicofo.conf`, `jvb/Dockerfile`, and `jvb/rootfs/defaults/jvb.conf`. Control flow is broadly client/Web → Prosody → Jicofo, with Jicofo coordinating JVBs through brewery XMPP channels; media flows directly between endpoints and JVB over WebRTC.

#### Telephony, Recording, and Transcription Extensions
Jigasi connects SIP callers and transcription integrations to Jitsi conferences; Jibri provides browser-based recording/streaming, requiring Xorg, IceWM, PulseAudio, and Chromium before its Jibri process. Both may run an autoscaler sidecar. Core paths: `jigasi/Dockerfile`, `jigasi/rootfs/defaults/sip-communicator.properties`, `jibri/Dockerfile`, and `jibri/rootfs/etc/s6-overlay/s6-rc.d/40-jibri/run`. Feature overlays include `jigasi.yml`, `jibri.yml`, and `transcriber.yml`.

#### Observability and Optional Infrastructure
Compose overlays attach metrics, logs, traces, and RTC analytics without changing core images. Prometheus configuration is under `prometheus/prometheus.yml`; Grafana/Loki/OpenTelemetry assets are under `log-analyser/otel-collector-config.yaml` and `log-analyser/loki/conf/loki-config.yaml`; tracing uses Alloy and Tempo in `tracing/alloy/config.alloy` and `tracing/tempo/tempo.yaml`. RTCStats integration can depend on MongoDB and LocalStack definitions in `rtcstats/mongodb/mongodb.yml` and `rtcstats/localstack/localstack.yml`.

#### Delivery
Images are published to GitHub Container Registry, with stable and daily unstable release workflows. Build/release automation is rooted in `.github/workflows/ci.yml`, `.github/workflows/release-stable.yml`, and `release.sh`.

Main entry points: [`docker-compose.yml`](https://github.com/jitsi/docker-jitsi-meet/blob/master/docker-compose.yml) (Docker Compose), [`prosody/Dockerfile`](https://github.com/jitsi/docker-jitsi-meet/blob/master/prosody/Dockerfile) (Prosody), [`web/Dockerfile`](https://github.com/jitsi/docker-jitsi-meet/blob/master/web/Dockerfile) (Web / Nginx), [`jicofo/Dockerfile`](https://github.com/jitsi/docker-jitsi-meet/blob/master/jicofo/Dockerfile) (Jicofo)

## Diagram (Mermaid)

```mermaid
flowchart TD

subgraph group_images["Image stack"]
  node_base["Base image<br/>Docker image"]
  node_base_java["Java base image<br/>Docker image"]
  node_config_render{{"s6 config rendering<br/>runtime stage"}}
end

subgraph group_core["Conference core"]
  node_web["Web / Nginx<br/>edge service"]
  node_browser(("Browser clients<br/>external client"))
  node_prosody["Prosody<br/>XMPP control plane"]
  node_jicofo["Jicofo<br/>conference controller"]
  node_jvb["JVB<br/>media bridge"]
end

subgraph group_extensions["Optional media services"]
  node_jigasi["Jigasi<br/>SIP/transcription gateway"]
  node_jibri["Jibri<br/>recording service"]
  node_feature_overlays["Feature overlays<br/>Compose overlays<br/>[jigasi.yml]"]
end

subgraph group_observability["Observability"]
  node_metrics["Prometheus<br/>metrics collector<br/>[prometheus.yml]"]
  node_logs["OTel / Loki<br/>log pipeline"]
  node_traces["Alloy / Tempo<br/>trace pipeline<br/>[config.alloy]"]
  node_rtcstats[("RTCStats infrastructure<br/>analytics dependencies<br/>[mongodb.yml]")]
end

subgraph group_delivery["Delivery"]
  node_ci["CI and releases<br/>GitHub Actions<br/>[ci.yml]"]
  node_registry[("GitHub Container Registry")]
end

node_compose["Docker Compose<br/>deployment entrypoint<br/>[docker-compose.yml]"]
node_env["Operator environment<br/>deployment settings<br/>[env.example]"]

node_env -->|"configures"| node_compose
node_compose -->|"runs"| node_web
node_compose -->|"runs"| node_prosody
node_compose -->|"runs"| node_jicofo
node_compose -->|"runs"| node_jvb
node_feature_overlays -.->|"extends"| node_compose
node_base -->|"foundation for"| node_base_java
node_base -->|"foundation for"| node_web
node_base_java -->|"image layer"| node_prosody
node_base_java -->|"image layer"| node_jicofo
node_base_java -->|"image layer"| node_jvb
node_config_render -->|"configures before start"| node_web
node_config_render -->|"configures before start"| node_prosody
node_config_render -->|"configures before start"| node_jicofo
node_config_render -->|"configures before start"| node_jvb
node_browser -->|"HTTPS client"| node_web
node_web -->|"signaling"| node_prosody
node_web -->|"WebRTC media"| node_jvb
node_prosody -->|"XMPP conference state"| node_jicofo
node_jicofo -->|"brewery XMPP control"| node_jvb
node_prosody -->|"service identity"| node_jigasi
node_prosody -->|"service identity"| node_jibri
node_compose -.->|"optional attachment"| node_metrics
node_compose -.->|"optional attachment"| node_logs
node_compose -.->|"optional attachment"| node_traces
node_compose -.->|"optional attachment"| node_rtcstats
node_ci -->|"publishes images"| node_registry
node_registry -->|"supplies images"| node_compose

click node_compose "https://github.com/jitsi/docker-jitsi-meet/blob/master/docker-compose.yml"
click node_env "https://github.com/jitsi/docker-jitsi-meet/blob/master/env.example"
click node_base "https://github.com/jitsi/docker-jitsi-meet/blob/master/base/Dockerfile"
click node_base_java "https://github.com/jitsi/docker-jitsi-meet/blob/master/base-java/Dockerfile"
click node_web "https://github.com/jitsi/docker-jitsi-meet/blob/master/web/Dockerfile"
click node_prosody "https://github.com/jitsi/docker-jitsi-meet/blob/master/prosody/Dockerfile"
click node_jicofo "https://github.com/jitsi/docker-jitsi-meet/blob/master/jicofo/Dockerfile"
click node_jvb "https://github.com/jitsi/docker-jitsi-meet/blob/master/jvb/Dockerfile"
click node_jigasi "https://github.com/jitsi/docker-jitsi-meet/blob/master/jigasi/Dockerfile"
click node_jibri "https://github.com/jitsi/docker-jitsi-meet/blob/master/jibri/Dockerfile"
click node_feature_overlays "https://github.com/jitsi/docker-jitsi-meet/blob/master/jigasi.yml"
click node_metrics "https://github.com/jitsi/docker-jitsi-meet/blob/master/prometheus/prometheus.yml"
click node_logs "https://github.com/jitsi/docker-jitsi-meet/blob/master/log-analyser/otel-collector-config.yaml"
click node_traces "https://github.com/jitsi/docker-jitsi-meet/blob/master/tracing/alloy/config.alloy"
click node_rtcstats "https://github.com/jitsi/docker-jitsi-meet/blob/master/rtcstats/mongodb/mongodb.yml"
click node_ci "https://github.com/jitsi/docker-jitsi-meet/blob/master/.github/workflows/ci.yml"

classDef toneNeutral fill:#f8fafc,stroke:#334155,stroke-width:1.5px,color:#0f172a
classDef toneBlue fill:#dbeafe,stroke:#2563eb,stroke-width:1.5px,color:#172554
classDef toneAmber fill:#fef3c7,stroke:#d97706,stroke-width:1.5px,color:#78350f
classDef toneMint fill:#dcfce7,stroke:#16a34a,stroke-width:1.5px,color:#14532d
classDef toneRose fill:#ffe4e6,stroke:#e11d48,stroke-width:1.5px,color:#881337
classDef toneIndigo fill:#e0e7ff,stroke:#4f46e5,stroke-width:1.5px,color:#312e81
classDef toneTeal fill:#ccfbf1,stroke:#0f766e,stroke-width:1.5px,color:#134e4a
class node_base,node_base_java,node_config_render toneBlue
class node_web,node_browser,node_prosody,node_jicofo,node_jvb toneAmber
class node_jigasi,node_jibri,node_feature_overlays toneMint
class node_metrics,node_logs,node_traces,node_rtcstats toneRose
class node_ci,node_registry toneIndigo
class node_compose,node_env toneNeutral
```

## Components

### Image stack

Layered service images and runtime configuration.

- [Base image](https://github.com/jitsi/docker-jitsi-meet/blob/master/base/Dockerfile): Docker image · Shared Debian-oriented image foundation. · `base/Dockerfile`
- [Java base image](https://github.com/jitsi/docker-jitsi-meet/blob/master/base-java/Dockerfile): Docker image · Shared JVM foundation for backend services. · `base-java/Dockerfile`
- **s6 config rendering**: runtime stage · Renders container environment into runtime configuration before startup.

### Conference core

Client delivery, signaling, orchestration, and media.

- [Web / Nginx](https://github.com/jitsi/docker-jitsi-meet/blob/master/web/Dockerfile): edge service · Serves Jitsi Meet, HTTPS, routing, and optional ACME/JAAS. · `web/Dockerfile`
- **Browser clients**: external client
- [Prosody](https://github.com/jitsi/docker-jitsi-meet/blob/master/prosody/Dockerfile): XMPP control plane · Authenticates service identities and hosts conference domains. · `prosody/Dockerfile`
- [Jicofo](https://github.com/jitsi/docker-jitsi-meet/blob/master/jicofo/Dockerfile): conference controller · Allocates and manages conferences from XMPP state. · `jicofo/Dockerfile`
- [JVB](https://github.com/jitsi/docker-jitsi-meet/blob/master/jvb/Dockerfile): media bridge · Bridges real-time WebRTC audio and video. · `jvb/Dockerfile`

### Optional media services

Telephony, recording, and transcription overlays.

- [Jigasi](https://github.com/jitsi/docker-jitsi-meet/blob/master/jigasi/Dockerfile): SIP/transcription gateway · Connects SIP callers and transcription integrations. · `jigasi/Dockerfile`
- [Jibri](https://github.com/jitsi/docker-jitsi-meet/blob/master/jibri/Dockerfile): recording service · Runs Chromium-based recording and streaming. · `jibri/Dockerfile`
- [Feature overlays](https://github.com/jitsi/docker-jitsi-meet/blob/master/jigasi.yml): Compose overlays · Enables Jigasi, Jibri, and transcription services. · `jigasi.yml`

### Observability

Optional metrics, logs, traces, and RTC analytics.

- [Prometheus](https://github.com/jitsi/docker-jitsi-meet/blob/master/prometheus/prometheus.yml): metrics collector · `prometheus/prometheus.yml`
- [OTel / Loki](https://github.com/jitsi/docker-jitsi-meet/blob/master/log-analyser/otel-collector-config.yaml): log pipeline · `log-analyser/otel-collector-config.yaml`
- [Alloy / Tempo](https://github.com/jitsi/docker-jitsi-meet/blob/master/tracing/alloy/config.alloy): trace pipeline · `tracing/alloy/config.alloy`
- [RTCStats infrastructure](https://github.com/jitsi/docker-jitsi-meet/blob/master/rtcstats/mongodb/mongodb.yml): analytics dependencies · Optional MongoDB and LocalStack-backed RTC analytics. · `rtcstats/mongodb/mongodb.yml`

### Delivery

CI builds and publishes container images.

- [CI and releases](https://github.com/jitsi/docker-jitsi-meet/blob/master/.github/workflows/ci.yml): GitHub Actions · Builds stable and daily unstable images. · `.github/workflows/ci.yml`
- **GitHub Container Registry**: container registry

### Other components

- [Docker Compose](https://github.com/jitsi/docker-jitsi-meet/blob/master/docker-compose.yml): deployment entrypoint · Selects core services and optional feature overlays. · `docker-compose.yml`
- [Operator environment](https://github.com/jitsi/docker-jitsi-meet/blob/master/env.example): deployment settings · Environment-specific settings and generated credentials. · `env.example`

## Connections

- Operator environment → Docker Compose: configures
- Docker Compose → Web / Nginx: runs
- Docker Compose → Prosody: runs
- Docker Compose → Jicofo: runs
- Docker Compose → JVB: runs
- Feature overlays → Docker Compose: extends
- Base image → Java base image: foundation for
- Base image → Web / Nginx: foundation for
- Java base image → Prosody: image layer
- Java base image → Jicofo: image layer
- Java base image → JVB: image layer
- s6 config rendering → Web / Nginx: configures before start
- s6 config rendering → Prosody: configures before start
- s6 config rendering → Jicofo: configures before start
- s6 config rendering → JVB: configures before start
- Browser clients → Web / Nginx: HTTPS client
- Web / Nginx → Prosody: signaling
- Web / Nginx → JVB: WebRTC media
- Prosody → Jicofo: XMPP conference state
- Jicofo → JVB: brewery XMPP control
- Prosody → Jigasi: service identity
- Prosody → Jibri: service identity
- Docker Compose → Prometheus: optional attachment
- Docker Compose → OTel / Loki: optional attachment
- Docker Compose → Alloy / Tempo: optional attachment
- Docker Compose → RTCStats infrastructure: optional attachment
- CI and releases → GitHub Container Registry: publishes images
- GitHub Container Registry → Docker Compose: supplies images
