Docker deployment

CrestBid ships as a set of containers orchestrated by Docker Compose on a single host — the installer we run with you during onboarding sets all of this up. Understanding the layout helps operators manage, back up, and secure a deployment.

The services

• Application (UI + API) — the only published port, default 3000, localhost-bound by default
• Python orchestrator — local LLM inference (llama.cpp) and document pipelines
• Embedding server — local embedding models
• PostgreSQL with pgvector — all structured data and vectors, not reachable from the host network
• Redis — job queue, internal only
• License service — local license operations, internal only

Everything except the application port lives on a private internal network. After installation the platform operates with zero external network calls in its default configuration — it runs air-gapped.

Managing the deployment

Standard Docker Compose commands work from the install directory:

docker compose ps          # service status
docker compose logs -f app # follow application logs
docker compose down        # stop (data volumes are preserved)
docker compose up -d       # start again

Upgrading

Re-run your install command to move to the latest release, or pull the latest images and recreate the containers. Data volumes are preserved either way, and you can always verify exactly what’s running at /api/version.

Enterprise includes fully air-gapped on-premises deployment with pre-staged images and model files, custom packaging, and support. Contact sales for guidance.