Supported Providers and Hypervisors
Thinfinity® Cloud Manager connects to a wide range of cloud platforms and on-premises hypervisors through a unified interface. Whether you are managing virtual desktops in a public cloud or running workloads on local infrastructure, Cloud Manager abstracts provider-specific complexity and exposes a consistent set of operations across all supported platforms.
This article lists all supported providers and hypervisors, along with the capabilities available for each.
Connecting to any provider requires a valid credential profile configured in Cloud Manager. See Credentials and the per-provider credential guides for full configuration requirements.
Cloud Providers
The following public cloud platforms are supported for both Managed VM and VDI/DaaS Model workflows. All listed providers support the same three connection modes — Public IP, Private IP, and Agent Id — explained in the Connection Modes Quick Reference section below.
| Provider | Instancing Modes | Terraform Support | Notes |
|---|---|---|---|
| AWS (EC2) | Managed VM, Session-Based Pool, Dedicated (1:1) | Built-in (General Purpose T2, Demanding Workflows T3, Graphic Performance P3) | Requires IAM credentials with EC2 permissions. Region must be specified per credential profile. |
| Microsoft Azure | Managed VM, Session-Based Pool, Dedicated (1:1) | Built-in (General Purpose BasV2, Demanding Workflows DasV5, Graphic Performance NVas_v4) | Service Principal authentication (subscription_id, tenant_id, client_id, client_secret). |
| Google Cloud Platform | Managed VM, Session-Based Pool, Dedicated (1:1) | Built-in (General Purpose E2, Demanding Workflows N2, Graphic Performance G2) | Requires a GCP service account JSON key with Compute Engine permissions. |
| IONOS Cloud | Managed VM, Session-Based Pool, Dedicated (1:1) | Built-in (Cubes, vCPU Server, Dedicated Cores Bare Metal) | Uses API token authentication. Datacenter ID and server location must be configured. |
| Oracle Cloud (OCI) | Managed VM, Session-Based Pool, Dedicated (1:1) | Built-in (Custom Image, General Purpose, Demanding Workflows, Graphic Performance) | Requires OCI API Key authentication: tenancy OCID, user OCID, fingerprint, and private key (with optional passphrase). |
Terraform support means Cloud Manager ships a built-in template for that provider. You can also supply a custom Terraform template for any provider that has a Terraform-compatible API. See Infrastructure as Code (IaC) with Terraform.
On-Premises Hypervisors
The following on-premises hypervisors are supported. Connectivity is typically handled through the Virtualization Agent installed on each host or cluster, which enables Agent Id-based connection routing without requiring a public IP. All listed hypervisors support Agent Id and Private IP as connection modes — see the Connection Modes Quick Reference section below for when each one applies.
| Hypervisor | Instancing Modes | Terraform Support | Notes |
|---|---|---|---|
| VMware ESXi / Horizon | Managed VM, Session-Based Pool, Dedicated (1:1) | Built-in (General Purpose, General Purpose Non-Persistent) | Requires vCenter or ESXi host credentials. Horizon integration uses the Horizon REST API. |
| Microsoft Hyper-V | Managed VM, Session-Based Pool, Dedicated (1:1) | Built-in (General Purpose) | Communicates with the Hyper-V host via WMI/PowerShell remoting. Requires WinRM access. |
| Proxmox VE | Managed VM, Session-Based Pool, Dedicated (1:1) | Built-in (General Purpose) | Uses the Proxmox REST API. Requires API token or root credentials with sufficient permissions. |
| Oracle KVM (oVirt / OLVM) | Managed VM, Session-Based Pool, Dedicated (1:1) | Custom templates only | Requires Oracle Linux Virtualization Manager (OLVM) or oVirt Engine URL, username, and password. Supports optional TLS verification with a custom CA bundle. |
| Verge.IO | Managed VM, Session-Based Pool, Dedicated (1:1) | Custom templates only | Uses the Verge.IO API (via the community verge-io/vergeio Terraform provider). Supports either traditional username/password or OIDC authentication. |
Public IP connectivity is not recommended for on-premises hypervisors unless the VM is explicitly exposed through a network perimeter device. In most on-prem deployments, Agent Id or Private IP is the appropriate connection mode.
Kubernetes
Cloud Manager also supports Kubernetes as a first-class provisioning target. Kubernetes integration follows a different model than VM-based providers — pods replace VMs as the unit of compute, and the cluster schedules and runs them.
| Platform | Compute resource | Template | Connection |
|---|---|---|---|
| Kubernetes | Pods, scheduled by the cluster | YAML configuration in the model editor’s K8S Configuration tab | Brokered through Thinfinity® Workspace to the assigned pod |
Kubernetes models do not use the Pool Mode, Power, Destroy, Deploy, or Versioning settings that apply to VM-based VDI/DaaS Models. Instead, Cloud Manager creates a pod on demand when a user connects and removes it after the model’s idle timeout, while the Kubernetes cluster schedules and runs it.
For details on the Kubernetes wizard flow and configuration, see VDI/DaaS Models — Types of Models.
Instancing Modes: Quick Reference
The following table clarifies what each instancing mode means in the context of provider support. For a full conceptual explanation, see Choosing a Compute Path and Pooling Strategies.
| Mode | Description | Applicable To |
|---|---|---|
| Managed VM | Cloud Manager connects to an existing, pre-provisioned VM. No automated lifecycle management. | All VM providers |
| Session-Based Pool | Cloud Manager provisions and manages a shared pool of VMs. Users are assigned to available instances at session start. | All VM providers |
| Dedicated (1:1) | Each user is assigned a dedicated VM. The VM is provisioned on first use and persists across sessions. | All VM providers |
| Kubernetes (Pods) | Cloud Manager brokers access to pods on a Kubernetes cluster, creating them on demand and removing them when idle. The cluster schedules and runs each pod. | Kubernetes only |
Connection Modes: Quick Reference
| Mode | Description | Typical Use Case |
|---|---|---|
| Public IP | Cloud Manager connects to the VM’s public IP address directly. | Cloud providers with internet-accessible VMs. |
| Private IP | Cloud Manager connects via the VM’s private IP, within the same network or through VPN/peering. | Cloud providers with private networking, or on-prem with routable internal IPs. |
| Agent Id | Cloud Manager routes the connection through the Virtualization Agent installed on the host. No IP routing required. | On-premises hypervisors; cloud VMs behind NAT or without public IPs. |
The available connection modes for a given VM depend on the provider and the network configuration of your environment. Connection mode is set at the model level in General Settings.
See Also