System Description
High level view of Nexus components
Review the configuration and terms for the services your school actually uses.
How the workspace is organized#
Nexus has a web interface, an API service, background processing, a relational database, a document index, and file storage. Model providers and connected applications are separate services. The school API adds membership, class policy, conversation review, and usage controls.
Follow a request#
The client sends an authenticated request to its workspace. The server checks the account and resource access before retrieving context or calling a model. A school conversation also needs an allowed class context. Responses and citations return to the client.
Review the deployment#
Database credentials, storage encryption, network access, backups, and enabled providers depend on the deployed environment. Ask for the current architecture and configuration review when planning a school rollout.