Skip to content

Compose profiles

ADK provides several compose profiles to run specific groups of services. Use docker compose --profile <profile> up to start a subset.

Available profiles:

  • workflow — Workflow stack for automation: includes n8n, n8n-runner, qdrant, clickstack and required dependencies (postgres, redis, clickhouse).

  • public — Public tunnel connector: cloudflare service (for exposing services via a tunnel provider).

  • ai — Local AI runtime: ollama (local model runtime).

  • clickstack — Observability UI and OTLP collector: clickstack plus required clickhouse.

  • veam — Virtual tEAM stack: paperclip and its dependencies (Postgres).

  • reflex — Python web app runner: reflex service (backend API and export tooling).

  • discord — Discord worker/bot: discord service.

  • signal — Signal REST API service: signal (useful with n8n nodes that integrate with Signal).

  • odoo — Odoo stack: odoo plus postgres.

  • all — Start all services.

Notes: - Profiles control which services are created by docker compose and are useful to limit resource usage during local development. - For deployment, use the deploy/compose/compose.yml (it intentionally avoids binding ports to the host; access should be via reverse proxy or tunnel).