Nox-Lumen MfgNox-Lumen Mfg

Deployment and operations overview

This chapter targets operations, IT, and security teams. If you’re evaluating from the business side, skim “Quick planning” first; if you operate the stack, walk the sections in order.

Quick planning

ProfileRecommendationWhy
Small teams / fast trialSaaS cloudZero infra to run
Large domestic enterprises / sensitive dataOn-premisesCode and data stay inside the perimeter
Multinational / strict data sovereigntyHybridcombo agent locally, shared services in cloud
Defense / government / classifiedDomestic-stack on-premAll-domestic CPUs, DBs, and LLMs

Details: Deployment plans.

Chapter map

Architecture cheat sheet

Rendering diagram…

Minimum hardware (reference)

FootprintNodesSpec / nodeNotes
Single-node sandbox18 vCPU / 32 GB RAM / 200 GB SSDPOC / demo
Small team (under 50)316 / 64 / 1 TB SSDSplit data vs app vs storage
Mid-market (50–500)5–1016 / 64 / 2 TB SSD + GPU if self-hosting LLMsHorizontally scale app tier
Large (>500)CustomCapacity planning engagement

Self-hosted LLM nodes depend on the model card—see Installation.

Upgrade / rollback

  • SaaS: platform-managed rolling upgrades
  • On-prem: quarterly stable trains + security hotfixes — supports in-place upgrade and one-click rollback
  • Rollback window: revert to prior build within ~24 h post-upgrade

FAQ

Q: Bring our own LLM? A: Yes—configure arbitrary OpenAI-compatible, Anthropic, domestic models (DeepSeek / Qwen / GLM / MiniMax), or self-hosted vLLM.

Q: Air-gapped data? A: On-prem + self-hosted LLM keeps code, data, models, and inference inside the customer network.

Q: SSO? A: OIDC / SAML 2.0—Azure AD, Okta, Feishu, WeCom, LDAP, etc.

On this page