Self-hosting DBOS Conductor and the DBOS Console on infrastructure running containers requires a control plane, a web UI, and a dedicated database, according to documentation published on docs.dbos.dev. The deployment setup separates Conductor’s database from the system databases used by DBOS applications, managing workflows exclusively over WebSocket connections.
Container Architecture for Self-Hosted Conductor and DBOS Console
A self-hosted deployment consists of three core components running on standard container infrastructure. docs.dbos.dev reported that Conductor utilizes the dbosdev/conductor image on port 8090 to act as the primary control plane. The DBOS Console runs on the dbosdev/console image using port 8080 to provide the web user interface.
The third component requires a separate PostgreSQL database running version 16 on port 5432 to hold the registry of applications, users, and settings. docs.dbos.dev clarified that Conductor’s database never connects directly to user application databases, exchanging metadata and commands only through WebSocket connections.
Docker Compose Configuration for Local Development
Developers can trial self-hosted deployments locally using Docker Compose before moving to production Kubernetes environments. docs.dbos.dev outlined that testing requires a development license key obtained from the DBOS Console. Users must export this key as the DBOS_CONDUCTOR_LICENSE_KEY environment variable.
The local environment configuration defines a bridge network named dbos-network and a persistent volume for Postgres data. The configuration starts the PostgreSQL service with a health check, launches Conductor once the database is healthy, and subsequently initializes the console container. Administrators bring up the stack using the docker compose up command.
Applications Connect to Self-Hosted Conductor Using API Keys
Connecting applications to a self-hosted Conductor instance requires registering the application within the self-hosted DBOS Console to generate a specific API key. docs.dbos.dev noted that applications must point to a WebSocket URL, such as ws://localhost:8090/ for local setups or a secure wss:// URL behind a reverse proxy in production.
Developers configure their applications across multiple programming languages by passing the system database URL, conductor key, and conductor URL into the framework setup.
Production Licensing Requirements
While trial keys are available for evaluation and testing purposes, production deployments operate under distinct administrative constraints. docs.dbos.dev stated that a formal license agreement is required for production use, and operators must contact the sales team to obtain production licenses.
In comparison, alternative containerized platforms such as Appwrite handle self-hosting through manual Docker installations or marketplace templates while emphasizing full user control over data location and compliance configurations, as documented by Appwrite.
Frequently Asked Questions About Self-Hosting DBOS Conductor
What port does the DBOS Conductor control plane use by default?
The Conductor control plane listens on port 8090, while the DBOS Console web UI runs on port 8080, according to documentation from docs.dbos.dev.
Does Conductor share a database with user applications?
No, Conductor maintains its own separate PostgreSQL database to hold application registries, user accounts, and settings, communicating with user systems strictly via WebSockets, as reported by docs.dbos.dev.
How do developers obtain a license key for local testing?
Developers can acquire a trial license key directly from the DBOS Console and export it as an environment variable before launching Docker Compose, according to docs.dbos.dev.
Related reading