Skip to main content
Leamout Self-Hosted runs the communications runtime on customer-controlled infrastructure. It does not install a local copy of the Leamout marketing site or hosted customer console. The local runtime executes the control API, workers, SIP signaling, media handling, durable storage, and coordination needed for communications. Carrier connections, trunks, numbers, calls, recordings, conferences, and webhook execution remain local runtime state. The current production-runtime tooling packages and operates the stack through the leamout CLI. Docker Compose is the current orchestration mechanism underneath the CLI, but normal operator workflows should use the CLI rather than editing individual component containers.

​
Current implementation

The CLI currently supports initialization, runtime lifecycle commands, local diagnostics, offline license verification/installation, backups, restores, and staged runtime updates.
Hosted activation, automatic TLS/network validation, and the complete fleet-management/check-in experience are not yet implemented by the current init flow. The CLI explicitly reports those items as pending Self-Hosted Production v0.1 work.