Skip to main content
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
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

Keep Langfuse’s databases separate from Tilde’s. See Langfuse self-hosting.

Supported deployment methods

The gateway is a single Docker container, so it runs anywhere you run containers.
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

Direct agents

The simplest way to connect an agent to the gateway.

Network exposure

Ports, routes, and what to expose publicly.