---
title: "Concepts"
description: "The words used throughout these docs, in one page."
canonical_url: "https://docs.oz0.ai/getting-started/concepts"
---
# Concepts

> The words used throughout these docs, in one page.

For: Readers looking up product terms.

Use this glossary when a page introduces an unfamiliar term. Start with server, node, edge, management, plugin, agent and job; the remaining entries describe how they connect.

## The fleet

Node
: A machine running `orchestrator-zero-node`: a laptop, a GPU box, a VM, a Raspberry Pi. It dials out to the edge, reports what it can do and runs the agents and tools of the plugins installed on it. A node runs an agent’s job.

Server
: The `orchestrator-zero` binary, also called `oz0`, running `server start`. By default one process runs management, edge and embedded Temporal together. The same binary can run selected roles separately. A **cluster** is one or more servers using the cluster's databases; Temporal can also run externally.

Edge
: The server role nodes and apps talk to for runtime work. It runs with management by default, or as a separate process of the same server binary. It proxies Temporal, serves the runtime API and the LLM gateway, hands out plugin artifacts and keeps a control stream open to every node.

Management
: The server role, called `manager` in `--roles`, that serves the console and holds the registry of nodes, the certificate authority, tenants, operators, secrets, plugins and usage. Operators reach it with the CLI.

Labels
: Key-value pairs on a node, such as `gpu=a100` or `zone=eu-north`. They decide which plugins a node gets and which agents may run on it.

Tenant
: An isolated environment for a team or customer, with its own nodes, plugins, secrets and Temporal namespace. Every cluster starts with the tenant `default`.

Operator
: A person or a script using an operator certificate with the CLI and APIs. Its role and permissions determine what it may manage.

## The work

Plugin
: A versioned, installable package of agents, tools or other parts. A plugin can be a full folder with a manifest or a supported single-file definition, such as a Markdown agent. See [What a plugin is](https://docs.oz0.ai/build/plugins/overview).

Kind
: The role of a plugin, recorded in its manifest’s `kind:`. A **connector plugin** (`connector`) connects to an outside system or agent runtime. A **capability plugin** (`capability`) supports a task or use case. A **policy plugin** (`policy`) provides hooks and checks for the organisation. A **plugin set** (`set`) installs a pinned combination of plugins. See [How to structure plugins](https://docs.oz0.ai/build/plugins/structure).

Workspace
: A tenant’s area for editing plugin files and saving revisions. See [Workspace](https://docs.oz0.ai/build/plugins/workspace).

Application
: What your users open, such as a portal or a chat app. It is never a plugin: it lives outside Orchestrator Zero and calls agents over the runtime API, AG-UI, MCP or a chat channel.

Tool
: A component that exposes actions an agent or flow can call. Plugin tools can use an MCP server or expose a flow. See [Tools](https://docs.oz0.ai/build/parts/tools).

Tool action (function)
: An operation exposed by a tool, addressed as `<tool>.<function>`, for example `oz0_github.get_pull_request`. The configuration and technical reference call these operations **functions**.

Tool call
: One invocation of a tool action with specific arguments, such as asking `oz0_github.get_pull_request` for a particular repository’s pull request.

Agent
: A definition in a plugin: instructions, a model, the tools it may use, limits and who it may delegate to. Its jobs use a queue pool selected by its required labels and the plugin's node selector. Compatible plugins can share a pool.

Model
: The AI model an agent calls to interpret input, choose an action or produce an answer. An agent can request a tenant’s model alias, such as `default`; see [Models and providers](https://docs.oz0.ai/spend/models-and-keys).

Skill
: A folder with a `SKILL.md`, in the Agent Skills format, that teaches an agent how and when to use something.

Task
: The work you want done, such as reviewing a pull request. One task may involve several jobs.

Job
: A tracked execution, such as running an agent or a flow, with its own ID, input, status, result and cost. A job runs as a Temporal workflow, and its ID is the workflow ID. Workflow history is durable; recovery of in-flight work depends on its execution mode. See [Jobs and durability](https://docs.oz0.ai/concepts/jobs).

Home node
: The node that picked a job up. The job's tools run there, so a job can use files and devices on that machine.

Delegation
: An agent handing a task to another agent with `oz.delegate`. The child is a job of its own, on any node that has that agent, and its cost counts toward the parent.

## The plumbing

Task queue
: A Temporal queue that nodes poll. `pool.<plugin>` (and `pool.<plugin>.<labels>`) for the jobs of a plugin's agents and flows, or with shared pools `pool.~<pair>` for every plugin's on the same nodes with the same labels, `node.<id>` for work that must run on one node, and `oz0.default` for everything else.

LLM gateway
: The part of the edge that handles model calls routed through the node's proxy. It adds the tenant's API key, enforces controls and records tokens and cost without translating the provider's API format. Remote harnesses can call their provider directly; see [model authentication](https://docs.oz0.ai/spend/models-and-keys/authentication).

Join token
: A one-time or reusable secret that lets a node join a tenant without an operator approving it. It also carries the hash of the cluster's CA, so the node can check the server before it sends anything.

Master key
: The cluster root key used to seal certificate authorities, payload keys and, without a separate secrets key, tenant secrets. Keep it apart from database backups. Losing a required key can make the stored data unrecoverable; see [what to back up](https://docs.oz0.ai/fleet/backups).


## Sitemap

See the full [sitemap](https://docs.oz0.ai/sitemap.md) for all pages.
