How to Self-Host DBOS Conductor and Console
Self-hosting enterprise container systems requires managing specific infrastructure components and configurations, according to deployment documentation released by docs.dbos.dev.
Architecture and Database Requirements for Conductor
Production environments need three distinct elements: the Conductor control plane running on port 8090, the DBOS Console web user interface on port 8080, and a dedicated PostgreSQL database instance listening on port 5432 to manage application registries, users, and settings independently from underlying workload databases.
Production deployments of the Conductor control plane rely on WebSocket connections to communicate workflow metadata and commands directly to applications, as docs.dbos.dev reported. That control plane database remains strictly separated from application databases.
Docker Setups Require License Keys for Development
Development and trial setups utilize Docker Compose scripts requiring a specific license key exported via the environment variable DBOS_CONDUCTOR_LICENSE_KEY. The accompanying Docker configuration binds PostgreSQL version 16 alongside the conductor image dbosdev/conductor and the console image dbosdev/console across a custom bridge network designated as dbos-network. Production users require a formal license agreement arranged directly through corporate sales channels.
Resource Specs for Asciinema Self-Hosting
The asciinema documentation notes that self-hosting its recording platform via the official OCI image ghcr.io/asciinema/asciinema-server requires a minimum of 512 megabytes of RAM for personal setups and one gigabyte for community instances. That platform runs on PostgreSQL version 14 or higher and utilizes optional SMTP services for delivering authentication login links.
Developers Generate API Keys in Local Console
Connecting applications to a self-hosted control plane necessitates generating dedicated API keys directly within the local console interface rather than default cloud endpoints. Developers configure system database URLs and conductor connection strings across various programming languages. Python implementations utilize dictionary configuration mappings, while Node.js deployments pass environment parameters directly into asynchronous launch functions during startup phases.
Teams Must Verify Container Health and Secure Connections
“While asciinema.org is the default asciinema server used by the CLI for uploading recordings, you can self-host your own instance if you want full ownership and control over the recordings,” docs.asciinema.org reported regarding alternative containerized server deployments.
Engineering teams executing local evaluations must verify container health check responses on configured ports before registering applications via WebSocket URLs. Production environments mandate secure Transport Layer Security connections routed through reverse proxies utilizing standard wss:// protocols to secure enterprise workflows against unauthorized interception.