Technical Guidebook

Simple System Walkthrough

A plain-language explanation of how AverQel handles one user request.

How it works

You type a request into chat or DeepSpace.
The backend validates your tenant, account, conversation, and provider scope.
DeepSpace answers through the shared grounded chat service and can use notes, memory, and document context.
The answer streams into the conversation and is saved to history.
The answer streams into the conversation and can be inserted into the note editor.

The short version

Chat is the product surface. Memory, documents, providers, and MCP integrations are separate capabilities that the chat can use when the request requires them.

Technical Guidebook

Simple System Walkthrough

A plain-language explanation of how AverQel handles one user request.

How it works

You type a request into chat or DeepSpace.
The backend validates your tenant, account, conversation, and provider scope.
DeepSpace answers through the shared grounded chat service and can use notes, memory, and document context.
The answer streams into the conversation and is saved to history.
The answer streams into the conversation and can be inserted into the note editor.

The short version

Chat is the product surface. Memory, documents, providers, and MCP integrations are separate capabilities that the chat can use when the request requires them.