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

# OSS, Cloud, and Enterprise

> Compare Tilde OSS, Tilde Cloud, and Tilde Enterprise: who runs the gateway, which features each edition includes, and how to choose.

Tilde comes in three editions. They share one gateway, one SDK, and one agent model, so an agent you build for one edition runs on the others unchanged.

* **Tilde OSS** is the open-source gateway and SDKs, under the Apache 2.0 license. You run it yourself. The source is in [trytilde/tilde](https://github.com/trytilde/tilde).
* **Tilde Cloud** is Tilde, hosted by us. You run only your agents.
* **Tilde Enterprise** is Tilde on-prem. You run the gateway in your own infrastructure, with the controls a larger organisation needs.

## Who runs what

| | Tilde OSS | Tilde Cloud | Tilde Enterprise |
| - | - | - | - |
| Gateway, UI, and APIs | You | Tilde | You, on-prem |
| PostgreSQL, ClickHouse, and object storage | You | Tilde | You, on-prem |
| Envelope encryption key | You | Tilde | You, in your KMS |
| Your agents | You | You | You |
| Where conversations and traces live | Your infrastructure | Tilde Cloud | Your infrastructure |

In every edition, agents dial out to the gateway and expose no endpoints. See [Agent Registry](/docs/agent-registry).

## Self-hosting Tilde OSS

Tilde is open source and freely available for anyone to host themselves. We include a Docker Compose file in the [tilde repository](https://github.com/trytilde/tilde), under an Apache 2.0 license, as guidance for self-hosting. Essentially, self-hosting Tilde means you run or purchase your own infrastructure, manage deployments, choose your own URLs to expose it on, and deal with any scaling issues yourself.

The self-hosted version is the same product we run on Tilde Cloud, though our infrastructure is very different to support production volume. All changes go through our standard CI/CD pipeline before they ship to Tilde Cloud and become available for self-hosted instances.

Because we don't manage self-hosted instances or provide paid support plans for them, we don't offer any sort of guarantees around Tilde working in certain ways on your infrastructure, and you assume all responsibility and risk for your use of the product and the stack.

Tilde is a complex product to run. The gateway depends on PostgreSQL, ClickHouse, S3-compatible storage, an OpenTelemetry collector, and a GitHub token, and each needs to be secured, backed up, monitored, and upgraded. For production, we recommend Tilde Cloud or Tilde Enterprise.

* Choose **Tilde Cloud** if you want Tilde to run the platform for you.
* Choose **Tilde Enterprise** if you must run Tilde on-prem. We support Enterprise deployments in your infrastructure.

## Feature comparison

Almost every feature is in all three editions. The differences are in how operators sign in and what they may do.

| Feature | Tilde OSS | Tilde Cloud | Tilde Enterprise |
| - | - | - | - |
| Hosted by Tilde | No | Yes | No |
| On-prem deployment | Self-hosted, at your own risk | No | Yes |
| 24/7 support | No | Yes | Yes |
| [Agent Registry](/docs/agent-registry), deployments, and [routing](/docs/routing) | Yes | Yes | Yes |
| [Framework integrations](/docs/frameworks/overview) | Yes | Yes | Yes |
| [Connections](/docs/connections) and [secret encryption](/docs/security/secret-encryption) | Yes | Yes | Yes |
| [Tools](/docs/tools/overview) | Yes | Yes | Yes |
| [Prompts](/docs/prompts/overview) | Yes | Yes | Yes |
| [Skills](/docs/skills/overview) | Yes | Yes | Yes |
| [Chat channels](/docs/chat-channels) | Yes | Yes | Yes |
| [Inference providers](/docs/inference-providers) and budgets | Yes | Yes | Yes |
| [Agent capabilities](/docs/iam#agent-capabilities) and [end-user access](/docs/iam#end-user-access) | Yes | Yes | Yes |
| [Security middleware](/docs/security/middleware) | Soon | Soon | Yes |
| [Sessions](/docs/sessions), [traces](/docs/traces), and [logs](/docs/integrations/opentelemetry) | Yes | Yes | Yes |
| [Direct](/docs/deployment/direct-agents) and [sidecar](/docs/deployment/sidecar-agents) agents | Yes | Yes | Yes |
| [Operator roles (RBAC)](/docs/operator-access#operator-roles) | No | Yes | Yes |
| [Management API keys](/docs/operator-access#management-api-keys) | No | Yes | Yes |
| [OIDC sign-in configuration](/docs/operator-access#sign-in-with-your-identity-provider) | No | Yes | Yes |
| [Sign in to tools with Tilde's OAuth apps](/docs/tools/management) | No | Yes | No |

Pages and sections that apply only to some editions carry a <span className="cloud-tag">CLOUD</span> or <span className="enterprise-tag">ENTERPRISE</span> tag. Everything without a tag is in every edition.

## How Tilde OSS differs

Tilde OSS has no operator roles, no management API keys, and no OIDC sign-in configuration. In practice:

* Every operator has full access to the installation. Restrict who can reach the Tilde UI.
* Your CI pipeline registers deployments with the agent's own deployment registration key, from the agent's **Capabilities** and **Deployment** tabs. See [Release agents from CI](/docs/deployment/ci-cd).
* Agent capabilities still apply in full. Agents act only within what you grant them.

## Choose an edition

| Choose | When |
| - | - |
| **Tilde OSS** | You want to evaluate Tilde, or contribute to it, and you are comfortable running and supporting it yourself. |
| **Tilde Cloud** | You want Tilde without running the gateway and its databases, and your data may live in Tilde's cloud. |
| **Tilde Enterprise** | Conversations, credentials, and traces must stay in your infrastructure, or you need role-based access for many teams. |