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

# Pipecat Enterprise

> Run Pipecat Cloud agents in your own Kubernetes cluster with Pipecat Enterprise: what stays managed, what you operate, what leaves your cluster.

export const cliMinVersion = "1.2.0";

export const offeringName = "Pipecat Enterprise";

export const hostedName = "Daily-hosted regions";

export const productNameSingular = "self-hosted region";

**{offeringName}** is Pipecat Cloud with your agents running on infrastructure you own. You get it by registering a {productNameSingular}.

A {productNameSingular} is a Pipecat Cloud region that runs in a Kubernetes cluster you operate. Pipecat Cloud remains the control plane: you deploy agents, start sessions, and read logs and session records exactly as you do for {hostedName}, while your agents execute on your infrastructure — in your network, next to your data.

The `pipecat cloud` CLI, the REST API, the Python SDK, and the agent image format are identical to {hostedName}; the [introduction](/pipecat-cloud/introduction#start-on-cloud-grow-into-enterprise) lists what carries over, and the Fundamentals and Guides cover them for both. The pages in this group cover only what you operate: the cluster, the region package, and the data that stays inside it.

<Note>
  {offeringName} is enabled per organization. To get started, [contact
  sales](https://www.daily.co/contact/sales).
</Note>

## What changes

| Area                | {hostedName}                             | Self-hosted regions                                                                                                          |
| ------------------- | ---------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
| Where agents run    | Daily's infrastructure                   | Your Kubernetes cluster                                                                                                      |
| Secrets             | Uploaded to Pipecat Cloud as secret sets | Created by you in your cluster and [referenced](/pipecat-cloud/enterprise/secrets) by name — values never leave your cluster |
| Agent sizing        | Fixed agent profiles                     | [Explicit CPU and memory, or your own profiles](/pipecat-cloud/enterprise/sizing)                                            |
| CPU architecture    | `arm64`                                  | Whatever your nodes provide; you [declare](/pipecat-cloud/enterprise/sizing#architecture) `amd64`, `arm64`, or both          |
| WebSocket endpoint  | `wss://api.pipecat.daily.co/ws/…`        | A public endpoint [you expose](/pipecat-cloud/enterprise/websockets) and register                                            |
| Agent logs          | Stored by Pipecat Cloud                  | Stored in [your own log store](/pipecat-cloud/enterprise/logs), optional and off by default                                  |
| Supporting services | Managed                                  | You provide a broker and, optionally, a log store; the package bundles development-grade versions of both                    |
| Scaling ceiling     | Your organization's replica limit        | No platform-imposed ceiling — your cluster's capacity                                                                        |
| Billing             | Per agent-minute by profile              | Per your enterprise agreement; agent-minutes in self-hosted regions are not metered by profile                               |

## How your region connects

The region package installs a small set of platform components into your cluster alongside your agents. One of them, the **region agent**, opens an outbound, mutually authenticated TLS connection to Pipecat Cloud and keeps it open. Everything the control plane does in your region — creating deployments, starting sessions, querying logs — travels over that connection. Nothing connects inbound to your cluster, and the certificates involved are issued during enrollment and renewed automatically. Session traffic — WebSocket and telephony audio — goes straight to your region and never touches the control plane. The [architecture page](/pipecat-cloud/enterprise/architecture) walks through both planes.

## What leaves your cluster

Running a {productNameSingular} keeps your data in your region while giving Pipecat Cloud enough to manage it:

* **Always:** session records and per-session metrics (start and end times, outcome, CPU and memory usage), and the region's own health — connected agents, component versions, certificate expiry.
* **By default, on request:** a read-only diagnostic snapshot of the platform components, which Daily support can pull when you ask for help. It never includes secret values or your agents' logs.
* **Only when you enable it:** agent log lines, and only when someone in your organization queries them.
* **Never, to the control plane:** session audio or media, secret values, environment variables, or the contents of your configuration. Daily WebRTC sessions carry media over Daily's WebRTC infrastructure, as they do in every region.

The full breakdown is on [What Pipecat Cloud Can See](/pipecat-cloud/enterprise/what-daily-can-see).

## Getting started

<Steps>
  <Step title="Get enabled">
    {offeringName} is enabled per organization by Daily. [Contact
    sales](https://www.daily.co/contact/sales) to get started.
  </Step>

  <Step title="Prepare a cluster">
    Check the [requirements](/pipecat-cloud/enterprise/requirements) — a
    conforming Kubernetes cluster, two platform prerequisites, and outbound
    network access.
  </Step>

  <Step title="Register and install">
    Follow [Set up a region](/pipecat-cloud/enterprise/setup): register the
    region, mint an enrollment token, and install the region package with Helm.
    You'll need `pipecatcloud` {cliMinVersion} or later.
  </Step>

  <Step title="Deploy an agent">
    Deploy to the new region exactly as you would to any other, and start a
    session.
  </Step>
</Steps>