The Brain is not only for Neo's own repository. It runs as a service — point it at your content, and you get a memory-backed, cross-family engineering team operating over it.
The Agent OS is a Node.js infrastructure: Memory Core, Knowledge Base, the Native Edge Graph, the orchestrator, the Dream Pipeline, and the agent-to-agent substrate. Deploying it means standing those services up against your repositories and content, so the capabilities that maintain Neo in public — persistent memory, semantic code understanding, and reviewed multi-family work — operate on your side instead.
- A team that remembers your system — the Memory Core and Knowledge Base build durable, queryable understanding of your codebase and its history.
- Reviewed, not single-shot — the cross-family review process is part of the deployment, not an afterthought.
- Tenant-scoped ingestion — the Agent OS ingests from explicit sources with tenant identity and visibility boundaries, so what it learns is scoped to what you point it at.
flowchart LR
classDef src fill:#222,stroke:#f5a623,stroke-width:2px,color:#fff
classDef svc fill:#0f3460,stroke:#16c79a,stroke-width:2px,color:#fff
classDef team fill:#4a1942,stroke:#e74c3c,stroke-width:2px,color:#fff
Content["Your repos and content"]:::src
Services["Agent OS services: Memory, KB, Graph, DreamService"]:::svc
Team["Memory-backed cross-family team"]:::team
Content --> Services --> Team
This is capability framing, not a product offer: it describes what the architecture makes possible. See The Agent OS on Your Codebase for what is proven today versus what is still being shaped.
This page is the why and what. The end-to-end how — profiles, ingestion contracts, security boundaries, and the day-0 path — lives in the cloud-deployment guides:
- Cloud Deployment Overview — what cloud-native deployment means
- Day-0 Tutorial — the recommended first deployment path
- Tenant Ingestion Model — how content enters the Brain
- Security — tenant identity and visibility boundaries
- Deployment Cookbook — deployment profiles and operational recipes
- The Agent OS on Your Codebase — the capability and its honest boundaries
- The AI Engineering Team — what gets deployed
- Architecture Overview — the Agent OS topology