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

# Deploy the gateway

> Run the Tilde gateway as a Docker container in your own network, with PostgreSQL, ClickHouse, Langfuse, and an optional OpenTelemetry collector.

The gateway is the Tilde platform. It serves the UI, the management and ingress APIs, the agent runtime protocol, the inference gateway, and telemetry ingestion. You run it as a Docker container inside your own network, next to your databases and agents. Tilde does not host any part of it.

Deploy the gateway first. Every agent deployment mode depends on it.

![Tilde gateway deployed inside your on-prem environment, with infrastructure and agents on the left and ingress on the right](https://mintcdn.com/tilde-enterprise/o_HetdpYhTvJyVNO/images/gateway.drawio.svg?fit=max\&auto=format\&n=o_HetdpYhTvJyVNO\&q=85\&s=94f45a729377fc2dee46705eeb8b418c)

&#x20;*Click to zoom*

Everything inside the boundary stays private. Add the public ingress only when public chat providers such as Telnyx, WhatsApp, Slack, MS Teams, or AgentMail must deliver webhooks, or when external clients must reach chat routes. Expose only those paths.

## What the gateway depends on

| Dependency | Required | Purpose |
| - | - | - |
| PostgreSQL | Yes | Operational state. |
| ClickHouse | No | Log history. |
| Langfuse | No | Traces, sessions, and model analytics. Needs its own PostgreSQL, ClickHouse, Redis, and S3-compatible storage. |
| OpenTelemetry collector | No | Receives a copy of agent logs for your own observability backend. |
| S3-compatible storage | No | Attachments and avatars. |

Keep Langfuse's databases separate from Tilde's. See [Langfuse self-hosting](https://langfuse.com/self-hosting).

## Supported deployment methods

The gateway is a single Docker container, so it runs anywhere you run containers.

| Method | Examples |
| - | - |
| **Kubernetes** | Amazon EKS, Google GKE, Azure AKS, OpenShift, or your own cluster. |
| **Managed container services** | Amazon ECS and Fargate, Google Cloud Run, Azure Container Apps. |
| **Any Docker host** | A virtual machine or bare-metal server with Docker or another container runtime. |

> [!TIP]
>
> We recommend Kubernetes. It gives you rolling updates, health-based restarts, and secret management out of the box, and it runs the gateway and your agents side by side.

On every platform, run the gateway in a private network behind an HTTPS ingress or load balancer.

## Next steps

> [card] [Direct agents](https://enterprise-docs.trytilde.ai/deployment/direct-agents.md)
>
> The simplest way to connect an agent to the gateway.

> [card] [Network exposure](https://enterprise-docs.trytilde.ai/security/overview.md#network-exposure)
>
> Ports, routes, and what to expose publicly.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.