The core concepts behind the platform — how an agent is defined, how it acts, how it remembers, and how every action is made accountable. For a plain-language overview start with What is Olbrain Studio; for terms, see the glossary.
An agent on Olbrain Studio is a persistent actor with a defined purpose that can converse, run workflows, call tools, and act on triggers. Studio supports five agent types on one orchestration layer: Concierge (conversational), Operator (workflow), Analyst (research), Orchestrator (coordinates a fleet), and Copilot (assistive). Three runtimes — conversational, workflow, and research — are live.
An agent is defined by its brain — identity, tools, knowledge, channels, and guardrails — which compiles into a deployable system prompt and runtime configuration. The brain is generated from a BRD (a business-requirements document) that the platform produces during discovery, and it is versioned and immutable on publish, so a published agent behaves identically from turn one to turn ten thousand.
Work is expressed as workflows: directed graphs built from 37+ typed step executors — document AI, reasoning, integration, data ops, control flow, human gates, and outputs. Steps fan out per item and aggregate once. Workflows are bound to a specific agent at both definition and run time, so every audit event is attributable to that agent.
Agents reach external systems through tools, implemented as MCP tool servers, and through connectors. MCP has been used for external tool calls in production. Tools are how an agent does things in the world — query a system, file a record, trigger a downstream process — each call captured in the audit log.
Knowledge grounds an agent on enterprise data — documents and systems — so its answers and actions are grounded in your information. Knowledge is part of the agent brain and is governed under the same identity and audit model as everything else the agent does.
Agents and workflows start from triggers: a conversation, another agent, an external event, or a schedule. Triggers let agents act proactively and react to the systems around them, not only when a person prompts them.
The Agency Protocol gives each agent a persistent, governable identity — one accountable, exclusive actor — distinct from access-control identity (which only governs what an agent may touch). Because every decision and action traces to that one identity, the enterprise can attribute, verify, and answer for what its AI does. Identity is the property that makes an agent something the enterprise can be accountable for.
Persistent memory is provided by the Context Service: append-only, judge-gated memory scoped global → agent → session. At runtime an agent’s state — context, memory, history, and bindings — is compressed into a CS-packet that travels with each query to the model. The CS-packet is also the unit usage is metered in.
Every agent action is written to an immutable, append-only audit log and emits a signed, PII-free receipt. Detected PII is tokenized (deterministic encryption, Cloud-KMS envelope keys) before any payload reaches a language model. Lumen can replay any action and generate an audit packet on demand for InfoSec, Risk, or a regulator.
The fleet is governed from a single control plane at admin.olbrain.com: observability, policy enforcement, and lifecycle management, with every action attributable to a named agent. Agents run on Olbrain’s cloud — India-hosted (Google Cloud, Mumbai), DPDP-aligned, with tenant isolation and per-tenant key management — so no infrastructure is required from you. Security status is on the Trust page.