O O O O Operations
Deploy, monitor, and manage infrastructure
Most teams have deployment scripts that only one person understands, secrets scattered across .env files and Slack messages, and infrastructure changes done manually via SSH with fingers crossed. When that person is on vacation, deployments stop.
SBX codifies operations into governed CLI commands with audit trails. Vault-managed secrets, single-command deployments with automatic health verification, a port registry that prevents conflicts, media pipelines for HLS processing, and database migrations that never run raw SQL directly. Deployment is one command — pre-flight build check, version bump, deploy trigger, health verification, and post-deploy retrospective all happen automatically.
Single-Command Production Deployment
The deploy pipeline is a deterministic sequence: pre-flight build verification confirms the project compiles and passes checks, the version is bumped according to semver, git state is validated to ensure a clean working tree on the correct branch, deployment triggers through the hosting API with the exact commit hash, a health check confirms HTTP 200 on the production URL, and a post-deploy retrospective logs the result. Every deployment is recorded with commit hash, branch name, timestamp, and outcome — success or rollback.
Infrastructure at a Glance
Docker services, applications, and databases are managed through sbx infra — provisioning new project databases, running health checks across the stack, and reporting status for every container and application process. No SSH sessions, no manual docker-compose invocations, no guessing whether postgres is actually running. Everything through governed commands that log what they do and fail loudly when something is wrong.
Port Allocation & Health
Every service gets an allocated port recorded in a central registry. When working in git worktrees, ports are automatically offset to prevent conflicts — each parallel workspace gets its own isolated port range. Health status is checked live against running processes, not assumed from configuration. If a service claims a port but nothing is listening, the registry reports it.
Operations Commands
The full operations surface — deployment, infrastructure, secrets, migrations, and media processing — accessible through governed CLI commands. Select a command below to see its usage and output.