Component Interaction Map
A summary of the main relationships between CoreAI components.
The CoreAI services are designed to work as a connected layer rather than as isolated deployments.
Interaction View
Key Patterns
- The CoreAI Web Portal is the main user surface and consumes several backend services.
- The CoreAI API acts as the central orchestration layer for application logic, retrieval, and AI integrations.
- Temporal sits behind parts of the CoreAI API workflow layer, especially asynchronous chat and file-processing paths.
- Model Installer bridges the model registry and the Runtime inference layer.
- LiteLLM acts as the shared LLM gateway for multiple CoreAI services.
- OpenTelemetry and MLflow provide the visibility layer for AI behavior and service telemetry.
- Docling is primarily involved through Temporal-driven document-processing workflows, while Milvus is used both for ingestion outputs and later retrieval.