Skip to main content

Offline deployment preparation

Offline operation requires prepared local materials. Online one-click installation commands that download external dependencies cannot be reused unchanged in an isolated environment.

Both CSGHub CE and EE provide publicly available installation packages for self-service installation. You can also contact technical support. For an isolated environment, obtain the selected version and its dependencies in a connected environment first, then transfer them to your internal network.

Choose an installation method​

  • Docker installation: select the CE/EE configuration and image version.
  • Kubernetes installation: obtain the Chart and prepare matching configuration and images.
  • For assistance, provide your version, deployment method, hardware architecture and network conditions to technical support.

Public package availability and feature authorization are separate. If your EE installation requires a license, see license import. Use the checklist below for offline preparation and acceptance, and follow the selected version's installation instructions with internal resource addresses.

Prepare fixed application/component versions, charts and configuration, images and architecture/digests, internal registries, drivers/device plugins, storage, model weights/tokenizers, datasets, application packages, internal DNS/certificates/identity services and backups.

Local inference and asset operations require all dependencies to be available internally. Remote synchronization, commercial model APIs, external MCP tools, cloud checks and outbound application requests still need connectivity or internal replacements.

Without public connectivity, verify login, upload/download, deployment, model calls, tasks and restarts. Inspect unexpected external requests. Use deployment acceptance. Prepare target-version materials and verified backups again before upgrading; do not use an unpinned online update in an isolated environment.