> ## Documentation Index
> Fetch the complete documentation index at: https://docs.leamout.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Architecture

> Understand the product-level trust zones in a self-hosted Leamout runtime.

A self-hosted deployment runs the Leamout communications runtime on infrastructure you control.

At a product level, the runtime contains four responsibilities:

```text theme={null}
Leamout API and control services
            |
      durable runtime state
            |
 signaling and routing services
            |
       media services
            |
 carriers and communication clients
```

The implementation behind these responsibilities is intentionally not part of the public product contract and can evolve between releases.

## Trust zones

Plan the deployment around three network roles:

* **public signaling** for SIP and secure WebSocket ingress;
* **public media** for RTP and TURN traffic;
* **private control** for durable state, coordination, management, and internal runtime communication.

Only customer-facing interfaces required by your deployment should be reachable from untrusted networks. Internal state, coordination, and management interfaces stay private.