Container Images

Release 3 platform binaries (Go services, workers, and the Python agent) are published to Docker Hub under the dendra organization. During development, Kubernetes deployments pin images by digest in dendra-k0s. The registry links below are the source for pulls and tags.

Web applications and documentation sites (main app, public site, docs site, RPC API docs, and similar) are hosted on Render as static or web services. They are not distributed as Docker images.

Release 3 Binaries

Image	Docker Hub	Binaries	Source repository
dendra/dendra-api-services	dendra-api-services	dendra-api-server, dendra-job-scheduler, dendra-mcp-server	dendra-api-services
dendra/dendra-job-workers	dendra-job-workers	dendra-backend-worker, dendra-extract-worker, dendra-load-worker, dendra-monitor-worker	dendra-job-workers
dendra/dendra-agent	dendra-agent	dendra-agent (Python / FastAPI)	dendra-agent

The API server, job scheduler, and MCP server share one image. Each Deployment selects the binary via container command. Worker binaries share the same job-workers image the same way. The agent is a separate Python image (not bundled with the Go services).

Note

Images include the application binaries only. MongoDB, NATS, InfluxDB, MinIO, LLM endpoints, and other backing services are deployed separately. See system design and dendra-k0s.

Deployment

The tahoe cluster (Release 3 dev environment on Jetstream2 k0s) references these images in resources/dendra/ manifests. Digests are updated there when rolling out a new build.

For local development, each source repository documents how to build images from its docker/ directory. See the Docker section in the dendra-api-services, dendra-job-workers, and dendra-agent READMEs.