The governed runtime door

Run the whole agent platform through one clear boundary.

Arbora is the process the operator runs. It authenticates MCP, REST, A2A, browser, terminal, desktop, and messaging requests; composes the agent and graph services behind them; and supervises the connector fleet from one serving lifecycle.

Start Arbora See how it fits

One request path, five deliberately separate authorities.

<p class="site-card__title">Try it</p>
<p class="site-card__body">
  Install the bundled runtime, generate a local profile, validate it, and
  register the MCP launcher with Codex.
</p>
<a href="get-started/">Open the quick start →</a>

<p class="site-card__title">Understand it</p>
<p class="site-card__body">
  Follow a request from client to Arbora, agent control plane, durable
  graph, and connector service without blurring ownership.
</p>
<a href="architecture/">Explore the architecture →</a>

<p class="site-card__title">Operate it</p>
<p class="site-card__body">
  Configure local or network transports, validate authority, inspect
  readiness, and run the release canary.
</p>
<a href="deployment/">Use the deployment guide →</a>

What Arbora owns

Arbora owns Process lifecycle, MCP and REST composition, unary A2A, request policy, fleet supervision, and optional WebUI hosting.

Arbora delegates Agent decisions to agent-utilities, durable state and reasoning to epistemic-graph, source effects to connector services, and presentation to Agent WebUI.

Arbora does not copy those authorities. It binds their public contracts into one identity-aware application surface and reports unavailable authority explicitly.

Follow one request

1. Enter through one door An MCP, REST, A2A, or WebUI request reaches the Arbora serving process.
2. Establish authority Arbora verifies identity, tenant, requested action, and the applicable policy.
3. Route to the owner Agent work reaches agent-utilities; graph work reaches epistemic-graph; source work reaches an admitted connector.
4. Return evidence The caller receives a transport-specific response backed by the same governed result and provenance.

Choose the right room

If the operator must…	Go to…
Run MCP, REST, A2A, WebUI, or fleet supervision	Arbora — the operator are here
Build agents, workflows, evaluations, or skills	agent-utilities
Store, query, reason over, or prove durable knowledge	epistemic-graph
Build and certify a source connector	agent-connector-sdk
Use the platform in a browser	Agent WebUI

The capability status is the exact account of the surfaces shipped by this package.

Specification delivery

Open the specification delivery dashboard for current specification status, delivery timelines, velocity and burndown, and open pull request and issue snapshots. It refreshes with each main-branch push. Unknown completion dates and unavailable history are labeled explicitly; individual requirements and pull requests do not count as completed specifications.

Planned run observation

ARBORA-OPS-R021.4 defines planned run reads and served acceptance. The specification does not establish runtime availability.