Deployment options
An overview of deploying Nexus
This reference describes the underlying platform. Use a Nexus school release with its school membership, class policy, and cost controls. Installing a base engine alone does not add those controls. Some options require a separately licensed feature. The presence of a guide does not unlock that feature.
Hosted school access#
Use school.narb.cc for your school workspace. Nexus adds school membership, class policies, teacher review, approved models, and provider-cost controls to the underlying platform.
Personal access#
l.narb.cc provides a separate workspace for personal use. A personal account is not a school membership and does not grant teacher access.
Operator-managed deployments#
A Nexus school deployment needs the correct application release, configuration, database migrations, provider setup, and authorization controls. Arrange the supported release with the team. A generic platform installer does not add Nexus school controls.
The references cover Docker Compose, Kubernetes, infrastructure requirements, authentication, and updates. Treat commands as operator reference material until they have been checked against the release and environment you plan to run.
Resource planning#
A chat-only engine can use fewer services than a deployment that indexes connected sources. Background workers, search infrastructure, file storage, and model services change the resource requirements. Use the resourcing guide to understand those dependencies.
Licensed options#
Some authentication, permission-sync, analytics, and administration features require a separate license. Documentation does not imply they are included or enabled in a Nexus school account. Confirm the required options during rollout.