Run with Docker Compose

Use Compose when the agent should live in the same stack as your database or your other services.

Write the service

Save this as compose.yaml:

compose.yaml

services:
  cubit-agent:
    image: ghcr.io/usecubit/source-client:0.1.0
    restart: unless-stopped
    hostname: db-agent-1
    environment:
      CUBIT_API_URL: https://api.concatflow.com
      CUBIT_ENROLL_TOKEN: ${CUBIT_ENROLL_TOKEN}
      DATABASE_URL: ${DATABASE_URL}
    volumes:
      - cubit-agent:/data

volumes:
  cubit-agent:

No ports: section. The agent listens on nothing.

Put the secrets in .env

Next to compose.yaml, create .env and keep it out of version control:

.env

CUBIT_ENROLL_TOKEN=<your-token>
DATABASE_URL=postgresql://concatflow_reader:<password>@<host>:5432/app

If the database runs in the same Compose project, use its service name as <host>.

Start it

docker compose up -d
docker compose logs cubit-agent

Look for serving dataset in the logs.

After the first start, the agent reads its credentials from the cubit-agent volume and ignores CUBIT_ENROLL_TOKEN. You can remove the token from .env.

docker compose down -v deletes the volume, and the agent’s enrollment with it. Use docker compose down without -v to keep it.

⌘I

Embedded assistant

Private databases

Run with Docker Compose