Deployment options
Run the platform hosted by CloudVision360 or privately on your own Kubernetes or Docker host.
Online version, always current: https://cloudvision360.com/docs/platform/deployment/
The platform runs the same way whether we host it or you do. Tenant isolation, secret handling and the audit trail are identical in both.
SaaS (hosted by CloudVision360)
The quickest path: sign in, connect your clouds, and start. We run the infrastructure, apply updates and keep the service available. Your data stays in a tenant-isolated database with row-level security.
Private deployment
Run the whole platform in your own environment when policy or regulation requires it:
- Docker Compose on a single Linux VM for smaller estates (and for running CloudVision360, ITOps360 and AgentVision360 side by side).
- Kubernetes manifests for larger or highly available deployments.
- PostgreSQL with row-level security per tenant as the datastore.
Private-deployment customers receive deployment runbooks, Terraform modules for cloud onboarding, and upgrade and rollback procedures with their workspace.
Scaling roles
A deployment can run as a single node or split by role — an API tier serving HTTP, worker nodes consuming scans (scale these horizontally), and exactly one scheduler replica — so large estates scan without slowing the interface.
Private AI
In a private deployment, the AI gateway can be pointed at self-hosted models so no customer data leaves your environment for an external provider. See Ask CloudVision and the AI gateway.