Core concepts

A quick glossary of the terms that appear throughout the docs and the console.

Workspace

A workspace is a boundary for access and organization. Roles and permissions are granted per workspace, so you decide who can see and change the projects inside it. Workspaces are how an organization keeps teams and environments separate without duplicating work.

Project

A project is the home for one agent across its entire lifecycle. It holds every build, the agent's endpoint, and its API key in one place. You create a project, point it at your code, and everything that follows hangs off it.

Build

A build is one versioned, retained image of your agent, produced from a specific commit or uploaded bundle. Because builds are kept, you can compare them, run evals against them, and roll back to an earlier one at any time. A build moves through the statuses RECEIVED → BUILDING → UPLOADING → UPLOADED (or FAILED).

Agent

An agent is your deployed program — a graph that Arai serves. You supply the graph; Arai wraps it with a serving layer, a checkpointer, and a long-term store. You interact with it in the built-in chat or over its API.

Endpoint & API key

Every agent is reachable at its own public endpoint and carries its own API key. The key authenticates external callers and can be rotated independently of the endpoint. See Endpoints & API keys for details.

Trace

A trace is the recorded execution of a single run — every step the agent took, with inputs and outputs. Traces power debugging, metrics, and the evals that Arai generates from past runs and replays on each new build.