Skip to main content
This page is the single reference for how to11 is organized. Other pages link here rather than redefining these terms.

​
The hierarchy

to11 organizes everything into a three-level hierarchy. Access, roles, and settings all hang off these levels. 
Organization        your company or team — owns members, roles, and API keys
  └─ Workspace      a product area or environment family — groups related projects
       └─ Project   a single application or service — owns providers, routes, environments, and traces
  • Organization — The top-level tenant. Members, roles, and API keys live here. See Platform.
  • Workspace — Groups related projects under one organization. Workspaces can be renamed, archived, and made discoverable to the rest of the org.
  • Project — Where the work happens: provider connections, routing, environments, and the traces you observe.

​
The gateway

The gateway is the runtime that sits between your application and your LLM providers. You point your SDK at it, and it routes the request, applies inline security, and emits telemetry. See Deploy.

​
Providers, targets, and routes

Inside a project, a few primitives describe where traffic can go and how the gateway chooses:
  • Provider — a connected model vendor (OpenAI, Anthropic, and others) together with the credential the gateway uses to reach it. See Providers.
  • Target — a specific model on a provider, paired with the credential to call it: the concrete endpoint a request can land on. See Targets.
  • Route — a named mapping from a model name to a strategy over one or more targets: send everything to one target, split traffic by weight, or fall back on failure. See Routes.
  • Function — a task alias (like summarize) that points at a route, so your application names the job instead of the model. See Functions.
For the simplest setup you touch none of this — connect one provider and call its models by name. Routes and functions are there when you want to manage model choice centrally instead of in application code. See Routing.

​
The observability data plane

Every request through the gateway — and any spans you send directly — lands in a shared data plane you query from the dashboard. This is what powers traces, metrics, and dashboards. See Observe.

​
How the pieces fit

Your app ──SDK──▶ Gateway ──▶ LLM provider
                    │
                    └──telemetry──▶ Observability data plane ──▶ Dashboard

​
Next steps

Quickstart

Send your first traced request.

Platform

Manage your organization, members, and access.