Chat is an entry point, not a boundary
Switch models, continue context, and retain visible state for every turn inside the same workspace.
PRODUCT / WORKSPACE
One workspace, full control.
Aivory places multi-model chat, knowledge, tool calling, and deployment policy on one observable path. Begin with one machine, then split into a full stack when you are ready.
THE WORKSPACE MODEL
Let complex capabilities work along one path.
From model selection to the final answer, every layer maps to a real configuration and state.
Knowledge and files retain their sources
Document parsing, vector retrieval, and citations can be inspected, so answers do not become an opaque black box.
Tools obey your policy
Search, MCP, and the sandbox are explicitly configured by administrators, with clear permissions and execution boundaries.
DEPLOYMENT / CHOOSE YOUR EDGE
Start lean, upgrade whenever you need.
Start with one server, suited to a personal workspace or demonstration.
Application dataSQLite
VectorsEmbedded SQLite
DependenciesOne app container
STACK / WORKSPACE FLOW
Split a request into observable layers.
Drag the top layer, or select any layer to bring it forward.
Current layer: Retrieve relevant context
WORKSPACE / REQUEST PATH
Run a workspace request path.
- 01ModelWaiting for the prior step
- 02ContextWaiting for the prior step
- 03ToolsWaiting for the prior step
- 04AnswerWaiting for the prior step
›Run it to observe Model → Context → Tools → Answer.