Deployment Models

NuQloud supports several operator-managed layouts.

Model	Typical use	Key consideration
Managed account server	Provider hosts many user accounts	Clear tenant policy, quotas, catalog, and support boundaries
Dedicated NuQloud instance	One organization controls a branded environment	Organization-specific identity, integrations, and operations
Docker with bundled HTTPS	A self-contained deployment	Coordinate certificates and exposed ports
Docker behind an external proxy	Existing Caddy, Nginx, Traefik, or managed edge	Preserve forwarded headers, trusted proxies, and no-SSL topology
Existing Nextcloud/hybrid adoption	NuQloud components join an existing environment	Inventory versions, paths, apps, ports, and ownership before changes
Shared Qortal node	Multiple instances use one managed node	Isolate credentials and validate API/QDN routing for every instance

Choose one topology and keep it consistent through recreation and upgrades. Do not switch between bundled and external proxy modes accidentally during a recovery.