Architecture
An overview of BeeAI core concepts and architecture
This documentation is outdated. The platform is currently being upgraded to the latest version of ACP with major changes. Updated docs are expected in ~2 weeks. Apologies for the inconvenience.
Architecture
BeeAI enables a local-first experience, running all agents on your laptop for full data control and seamless integration with local inference engines like ollama.
The platform is made up of several core concepts as shown in the following diagram:
Agents
An agent is a container that communicates using the Agent Communication Protocol. Agents typically define a manifest that instructs BeeAI on how to run them and may include additional features like tools.
For details on registering agents, see agents.
BeeAI includes several built-in agents, see our agent catalog.
BeeAI Server
Explore the beeai-server source code.
BeeAI server manages agents, spawns/destroys agent processes, and provides a unified endpoint for routing requests and notifications between agents and clients.
It also manages agent configurations and environment variables and offers a simple REST API for agent communication and telemetry data forwarding to the Arize Phoenix OTEL backend.
BeeAI CLI and UI
These components offer interfaces for interacting with agents.
Agents can have custom input/output interfaces, but the platform provides standard UIs like chat and hands-off.
Use beeai run <name> or the graphical chat at localhost:8333 to interact with agents.
Python and TypeScript clients
You can use the ACP SDK to programmatically interact with the agents and integrate multiple agents into a workflow for your application.
Arize Phoenix
BeeAI integrates with Arize Phoenix, an open-source agent tracing tool. For more information see agent observability.