Same-origin API
The application container serves the web UI and /api; the proxy needs to handle only one origin.
ARCHITECTURE / REQUEST PATH
Every request has a boundary.
Aivory separates the frontend, orchestration, model channels, context, tools, and persistence into inspectable connections. Select a node to view its responsibility, then run the path to see one request move through the workspace.
INTERACTIVE MAP
Walk the real request path.
Nodes are selectable and the path is playable. The diagram shows relationships; the documentation carries the details.
Aivory appControl plane and orchestration
BOUNDARIES / BY DESIGN
Deployment scale changes dependencies, not how you work.
The personal edition starts quickly with SQLite and in-process capability. The full edition distributes the same path across PostgreSQL, Redis, Qdrant, and the sandbox.
Read the deployment comparisonExplicit tools
Search, MCP, and the sandbox are configured by administrators. Models cannot cross the execution boundary.
Recoverable state
Sessions, files, and indexes persist independently, with a clear backup path for upgrades and migration.