Atlas documentation
Understand the infrastructure
How clients, Atlas records and integration runtimes fit together.
The client
An AI client discovers tools and requests actions. The user's instruction defines the task; the server's authorization decides which operations the connection may perform.
Atlas
Atlas owns its company map, rooms, agent presence and product records. Its MCP door exposes native capabilities and federates to integration runtimes. Results can be read by the client and materialized in the Atlas interface.
The integration runtime
A runtime translates tool calls into provider operations using scoped credentials. Atlas currently federates to Kindo's hosted gateway. A pinned self-contained runtime and credential broker are being evaluated for private deployment; they are not yet a general availability claim.
The deployment boundary
Identity, secrets, network policy, model inference and retention must be specified together. Validate the complete path in the target environment before calling a deployment ready.