Velocize supports cloud, connected enterprise and isolated operating environments. Deployment selection connects hosting location with identity, information sensitivity, AI provider access, integration paths and operational responsibility. The right boundary covers the whole lifecycle, including backups, logs, exports and support access.
Compare deployments and their responsibilities
Select data location, AI routes, updates and operational ownership together. Review package and service scope alongside that deployment decision.
On narrow screens, scroll the table horizontally.
| Model | Environment | AI route | Responsibility |
|---|---|---|---|
| SaaS | Service-operated environment under the agreed hosting and data-location terms. | Approved model providers or an authorized private-model connection. | Service operation, support access, backups and recovery responsibilities are recorded in the service scope. |
| Private cloud | A selected private environment with controlled network and identity boundaries. | Private endpoints and provider routes permitted by the organization's policy. | The infrastructure operator and Velocize product-support responsibilities are assigned explicitly. |
| Connected on-premises | Customer infrastructure with approved external integration and update routes. | Local models or explicitly approved external providers. | Customer IT operates the environment; product support, updates and diagnostic sharing follow the agreement. |
| Isolated / offline | An isolated customer environment with controlled license, update and exchange packages. | Local or in-boundary models; an external AI provider is not required for the lifecycle workflow. | Agree offline update handling, authorized transfer, restoration and bounded support diagnostics. |
Cloud service and private enterprise environments
SaaS provides a service operating model, while private cloud and connected self-hosted deployment place infrastructure and integration boundaries within the enterprise context. Package scope and operating responsibilities are established together with the deployment model.
An enterprise assessment maps identity providers, network routes, repositories, delivery systems and external stakeholders. It also defines who owns upgrades, backup verification, incident response and the operating evidence required for acceptance.
Offline and air-gapped operation
Offline distribution supports enterprise environments in which external connectivity is restricted. Licensing, package exchange, software distribution and evidence transfer are treated as explicit operating processes. The selected model defines how updates and authorized review material cross the isolation boundary.
Local or private model use aligns AI execution with the same boundary. An isolated application environment must be assessed together with every model endpoint and supporting service that receives lifecycle data.
Residency extends beyond primary storage
Data location includes artifacts, search indexes, retained evidence, telemetry, recovery copies and external exports. Provider and model eligibility are evaluated against tenant and sensitivity policy. Retention and deletion requirements remain relevant when information is summarized, translated or delivered to an external party.
Define a data-flow map that identifies each processing destination and its owner. The deployment review can then evaluate the full information boundary and the controls used to enforce it.
Federation with accountable exchange
Federated and sovereign operating contexts preserve organizational boundaries while supporting authorized package exchange and baseline coordination. Participating organizations retain explicit responsibilities for their local state and for the material they share.
The deployment conversation starts with a representative lifecycle: source ingestion, approval, AI participation, release evidence and customer exchange. Walking that path reveals the network, identity and recovery decisions that belong in the operating agreement.