Skip to main content

​
Supported frameworks

You build agents in the framework you already use. Tilde provides a core SDK in TypeScript and Python, plus an adapter package for all major frameworks. See Framework integrations for how each one works, and which features it supports.
Tilde is framework agnostic. If your framework is not on this list, you can still use the core SDK today, and we can add an adapter for it.
Each adapter converts Tilde message history, tools, and skills into the framework’s own types, and registers the framework’s prompts at deploy time. The core SDK has one contract, run(context), and depends on no agent framework.

​
What the SDK does

The Tilde SDK wraps your agent and turns it into a deployable unit. You can ship it in two ways:
  • A standalone container that runs on any platform that supports Docker containers, such as Kubernetes or Amazon ECS.
  • An AWS Lambda function that the gateway invokes on demand.
Once you register the agent, Tilde acts as a secure proxy and central hub. Three kinds of data start flowing through it:

​
Agent lifecycle

Sequence of an agent connecting to the Tilde gateway, registering, receiving an invocation with a short-lived token, and proxying tool calls, LLM requests, and telemetry back through the gateway
Click to zoom
1

The agent connects out

On deployment, your agent exposes no endpoints. It opens a secure HTTP/2 stream to the Tilde gateway, or to its sidecar.
2

Tilde registers the deployment

When the stream is established, Tilde marks the deployment as connected. After the agent reports healthy, routing sends new conversations to it.
3

The gateway issues a token for each invocation

Every request to your agent reaches the gateway first. The gateway issues a short-lived, signed token and forwards the token and the request to the agent over the HTTP/2 stream.
4

The agent works through the gateway

The agent uses the token to proxy all tool calls and LLM inference requests, and to send OpenTelemetry logs and traces. The token lasts minutes, and the SDK renews it while the invocation is active.
5

Responses stream back

All responses stream back through the gateway to the end user.

​
Why Tilde works this way

The agent container never exposes an HTTP endpoint, so there is nothing on it to attack. The agent also holds no provider credentials. That leaves one place to govern IAM, security middleware, secrets, and budgets: the gateway. A policy change applies to every agent at once, whatever framework it uses.

​
Next steps

Deploy a direct agent

Connect your first agent to the gateway.

Release from CI

Register deployments from your pipeline.