Skip to main content
Tilde uses Langfuse as the system of record for traces. The gateway delivers every agent trace to your self-hosted Langfuse. The Tilde UI then reads traces and sessions back through the Langfuse API. You run Langfuse yourself, inside the same private network as the gateway. Agent traces never leave your infrastructure.

Deploy Langfuse

Langfuse has its own web and worker services, and its own dependencies. Follow the Langfuse self-hosting guide. Then create a Langfuse project for Tilde, and create an API key pair in it.

Configure Tilde

You give the gateway your Langfuse address and a project API key pair. Optionally, you also give it the address your operators’ browsers use, so Tilde can link straight to records in Langfuse. Langfuse credentials stay on the gateway. They never reach sidecars, agents, or browsers.

What Tilde sends

Tilde delivers OTLP spans to Langfuse’s OpenTelemetry ingestion endpoint. It keeps trace IDs, span IDs, and parent links intact. Session metadata contains identity IDs, not identity values, and no message bodies. The gateway sets it, so an agent cannot forge it. Tilde does not send pricing. Langfuse applies its own model prices. For spend that Tilde enforces, see Inference providers.

Use Langfuse with Tilde

  • Operators read traces in Tilde’s native viewer, without a Langfuse login. See Traces.
  • Each trace, observation, and session in Tilde links to the same record in Langfuse, for analysis that needs Langfuse’s own tools.
  • Use Langfuse for evaluations, datasets, and dashboards across agents.
  • Set trace retention in Langfuse. Tilde keeps no permanent trace history of its own.

Delivery guarantees

The gateway queues traces durably and retries until Langfuse accepts them, without delivering duplicates. If Langfuse is unavailable, your agents are unaffected.