Skip to main content
You build agents in the framework you already use and register them in the Agent Registry. From then on, the Tilde gateway sits between each agent and everything it touches. Chat messages, tool calls, LLM requests, logs, and traces all flow through one governed hub.

Agent Registry

Learn how agents connect to Tilde and what flows through the gateway.

What Tilde Enterprise gives you

Connections

Store encrypted credentials for chat, tool, and inference providers.

Tools

Give agents managed, custom, and proxied MCP tools.

Chat channels

Route messages from Slack, WhatsApp, email, and your own apps to agents.

Inference providers

Proxy LLM requests, keep provider keys out of agents, and enforce budgets.

IAM

Control what operators, agents, and end users can do.

Security

Encryption, short-lived tokens, middleware, audit data, and network exposure.

Sessions and traces

Review every conversation, run, tool call, and model call.

Deployment

Deploy the gateway and your agents on Kubernetes, ECS, or Lambda.

How the pieces fit

Tilde gateway deployed inside your on-prem environment, with infrastructure and agents on the left and ingress on the right
Click to zoom
The gateway is a single Docker container that you run next to your databases. Agents run as separate containers or Lambda functions and dial out to it. Users and chat providers reach agents only through the gateway’s ingress.

Where to start

1

Deploy the gateway

Follow Deploy the gateway to run Tilde with PostgreSQL and your identity provider.
2

Connect providers

3

Register an agent

Wrap your agent with the Tilde SDK and deploy it.
4

Automate releases

Register each release from your CI pipeline.