> ## 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.

# Introduction

> Build and operate programmable communications with control over runtime placement and carrier connectivity.

Leamout is a programmable communications control plane for building and operating voice, numbering, routing, and carrier-connected telecom products.

The platform separates two decisions that are often coupled by communications providers:

* **Where the communications runtime runs** — on your infrastructure or in Leamout Cloud.
* **Who provides carrier connectivity** — your carrier relationships through BYOC or Leamout-managed connectivity.

The communications model stays consistent across those delivery modes. Applications work with Leamout resources such as voice applications, calls, numbers, SIP domains, subscribers, carrier connections, and trunks instead of carrier-specific APIs.

## Current focus

The current implementation is strongest around self-hosted programmable voice and BYOC. It includes organization-scoped telecom resources, SIP carrier onboarding, inbound and outbound call routing, programmable call control, recordings, conferences, webhooks, SIP/WebRTC access, and short-lived TURN credentials.

<Note>
  Leamout also contains work toward managed connectivity and commercial primitives, but later roadmap areas such as full messaging, realtime AI media, multi-carrier orchestration, and production HA should not be treated as complete product surfaces yet.
</Note>

## Platform model

Leamout keeps the customer-facing control plane separate from communications execution:

```text theme={null}
Applications and API clients
            |
            v
      Leamout control plane
            |
     Communications resources
            |
     Routing and policy
            |
  Leamout communications runtime
            |
      Carrier networks
```

This separation lets Leamout preserve the same resource model across self-hosted and cloud runtimes while keeping BYOC and Leamout-managed connectivity as independent choices.

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/quickstart">
    Authenticate with an organization credential and create your first voice application.
  </Card>

  <Card title="Core concepts" icon="diagram-project" href="/concepts/core-concepts">
    Understand organizations, applications, connectivity, trunks, calls, and runtime placement.
  </Card>

  <Card title="Bring your own carrier" icon="tower-broadcast" href="/guides/connectivity/byoc">
    Configure a generic SIP carrier connection and route calls over your own provider.
  </Card>

  <Card title="Self-host Leamout" icon="server" href="/self-hosting/overview">
    Learn what runs on your infrastructure and how the current operator CLI works.
  </Card>
</CardGroup>