Quick Start Guide
Thinfinity® Cloud Manager is integrated with Thinfinity® Workspace and can be up and running in minutes. This guide walks you through the most common starting points — connecting an existing virtual machine, deploying a new on-demand VDI pool from a built-in blueprint, and deploying Remote Browser Isolation on Kubernetes — so you can validate the end-to-end workflow before building out your full environment.
Cloud Manager supports a wide range of platforms: Amazon Web Services (EC2), Microsoft Azure, Google Cloud Platform, Oracle Cloud Infrastructure (OCI), IONOS Cloud, VMware (ESXi and Horizon), Microsoft Hyper-V, Proxmox VE, Oracle KVM (oVirt / OLVM), Verge.IO, and Kubernetes clusters. Tracks A and B use Oracle Cloud Infrastructure (OCI) as the example provider — Cybele Software has a strategic partnership with Oracle, and OCI is the recommended provider for new deployments. The underlying Cloud Manager workflow is identical across all supported VM-based providers; only the credential fields and provider-specific parameters differ. For a Kubernetes-based Remote Browser Isolation deployment, follow Track C — Deploy Remote Browser Isolation. For how the compute paths compare, see Choosing a Compute Path. For a side-by-side mapping of provider concepts, see Provider Concepts Map.
Choose the track that matches your situation.
| Track | Goal | Estimated time |
|---|---|---|
| Track A — Connect a Managed VM | Make an existing OCI Compute instance accessible to users through Thinfinity® Workspace | ~10 min |
| Track B — Deploy a VDI Pool | Deploy a new on-demand VDI pool on OCI and connect your first user | ~20 min |
| Track C — Deploy Remote Browser Isolation | Run an isolated browser on an existing Kubernetes cluster and connect your first user | ~15 min |
You can complete any of the three tracks independently. If you are new to Cloud Manager, start with Connect a Managed VM to validate your credentials and network configuration before moving to a full model deployment.
Common Prerequisites
All three tracks share the following prerequisites. Confirm each item before proceeding.
| Requirement | Details |
|---|---|
| Thinfinity Workspace | Version 8.5 or later, fully installed and operational. The Primary Broker, Web Manager, and at least one Secondary Broker must be online. |
| Cloud Manager enabled | The Cloud Manager module must be activated in Configuration Manager and the administrator account must have UI access. See Enable Cloud Manager. |
| Cloud Manager permissions | The administrator account requires at minimum: View + Manage on Instances, View + Create + Edit on Credentials, and View + Create + Edit on Models. See Cloud Manager Permissions. |
| Oracle Cloud account | An active OCI account with sufficient permissions to manage Compute instances. The Quick Start uses API Key authentication — the most universally applicable approach, since it works whether Cloud Manager runs on OCI, on a different cloud, on-premises, or in a hybrid setup. |
| Oracle Cloud Credentials • configured in Cloud Manager | See Step 5 in Oracle Cloud Credentials for the full credential setup guide. |
| Browser | Google Chrome, Microsoft Edge (Chromium), or Mozilla Firefox — latest release. |
The Oracle Cloud items above apply to Tracks A and B. Track C does not use a cloud provider — it requires an existing Kubernetes cluster and credential instead. See Track C prerequisites.
Tracks A and B use API Key authentication because it works in every deployment topology. If your Thinfinity Workspace server runs as an OCI Compute instance, you can also use Instance Principal authentication (keyless, identity-based) — see Oracle Cloud Credentials → Option B.