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 — The top-level tenant. Members, roles, and API keys live here. See Organizations.
  • Workspace — Groups related projects under one organization. Workspaces can be renamed and archived. See Workspaces.
  • Project — Where the work happens: the prompts and skills you publish, the environments they publish to, and the sessions your coding agents upload. See Projects.

Prompts: chat prompts and skills

A project holds prompts, and a prompt is one of two kinds, chosen when it is created:
  • Chat prompt — a template of messages, variables, tools, and model settings. You author it in the dashboard, and your application renders it at runtime with an SDK and sends the result to a model. See Prompt management.
  • Skill — a folder of files a coding agent reads. You write it as files and store it with the to11 CLI, and the CLI installs it on every machine that follows the project. The dashboard reads skills but does not edit them. See What a skill is.
Both kinds share one version model: every change is a new, immutable version, and the prompt’s one label, latest, always points at the newest version. Rendering a chat prompt serves latest. A machine receives a skill’s latest too, unless its configuration holds the skill at a version.

Environments

An environment is a named slot in a project, such as prod or staging, that the project’s prompts and skills publish to. Every project starts with two, prod and staging. See Environments.

Sessions

A session is one run of a coding agent, uploaded as its transcript. The to11 CLI sends the Claude Code sessions you run to a project, either when you run to11 session sync or automatically after each response, and the dashboard shows them on the project’s Sessions page. See Sessions.

People and API keys

People sign in to the dashboard and the CLI as themselves, and what they can do comes from the roles they hold on the organization, a workspace, or a project. Machines, such as an application server or a CI job, use an API key scoped to the permissions they need.

How the pieces fit

The SDK and the CLI both talk to the to11 API at https://api.to11.ai. Your application sends the rendered prompt to a model with your own provider client and provider key; to11 is not in that request.

Next steps

Quickstart

Create a project and use it from the SDK and the CLI.

Platform

Manage your organization, members, and access.