Architecture
A high-level map of AverQel's chat, documents, memory, providers, integrations, and security boundaries.
Frontend surfaces
Dashboard pages, grounded queries, DeepSpace chat, documents, memory, settings, MCP, and documentation are separate product surfaces.
Backend services
Backend services handle authentication, retrieval, answer generation, safe tool execution, memory, providers, and integrations.
Persistence
PostgreSQL stores tenant-scoped conversations, messages, memory, provider configuration, and integration state.
MCP boundary
MCP discovery, authorization, catalog, and remote tool execution remain isolated from the normal chat and memory surfaces.
How a request moves
- The frontend sends a tenant-authenticated chat or query request.
- The backend loads scoped history and relevant document or memory context.
- The selected provider generates the answer, with permitted tools available when needed.
- The result streams to the frontend and is persisted as conversation history.
Safety boundaries
Authentication, tenant isolation, encrypted secrets, provider policy, approval checks, and MCP authorization remain backend responsibilities. Removing the orchestration and IDE-style surfaces does not weaken those boundaries.