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

# What is to11?

> What to11 is, who it's for, and how it fits your AI stack.

to11 puts an LLM gateway, inline security, and OpenTelemetry-native observability behind one hosted control plane. Route your model traffic through it and to11 traces, secures, and measures every call — without you wiring up a stack of separate tools.

It takes your app to eleven.

## Who it's for

**AI and platform engineers** who:

* Ship LLM-powered applications or agents to production
* Need observability over non-deterministic model behavior
* Want inline security — PII detection and blocklist matching applied in the request path, before anything reaches the provider
* Run more than one provider and want a single interface in front of them

## What you get

### Gateway

An LLM proxy between your application and your providers, adding under a millisecond of overhead. Cross-format routing — send OpenAI format, route to Anthropic, get OpenAI back — plus inline security and streaming. See [Deploy](/docs/deploy/overview).

### Observability

Point your SDK at the gateway and every call becomes an OpenTelemetry-native trace: model, tokens, latency, and optionally the prompt and completion. See [Instrument](/docs/instrument/overview) and [Observe](/docs/observe/overview).

### Evaluation

<Info>
  Coming soon — score and compare your application against recorded traces. See [Evaluate](/docs/evaluate/overview).
</Info>

## How it's organized

Everything nests into **Organization → Workspace → Project**. See [Core Concepts](/docs/get-started/concepts).

## Next steps

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/docs/get-started/quickstart">
    Send your first traced request.
  </Card>

  <Card title="Core concepts" icon="layers" href="/docs/get-started/concepts">
    How to11 is organized.
  </Card>
</CardGroup>