No longer call it Cameyo, but Cameyo by Google.
Alongside this rebranding, the messaging around the product is evolving. It now places greater emphasis on integrations with the Chrome ecosystem.
We weren’t starting from zero in this area. By mid-2024, when Google announced it would acquire Cameyo, some connections were already in place—primarily with ChromeOS (integration with the local file system, clipboard management, delivering apps as PWAs, etc.).
The idea of a unified experience within Chrome Enterprise is now foregrounded. The virtualized desktop applications via Cameyo would benefit, on one hand, from the same security context as SaaS (URL filtering, DLP, threat protection…), and on the other, from the same AI layer, via Gemini for Chrome.
Linux Virtualization Less Prominent Under the Google Era
Apart from a few references to Google, Cameyo’s website has remained largely as it was before the acquisition.
Among the promises at the time was the ability to virtualize Linux applications and internal web apps without needing a Windows Server license.
Within Google’s fold, this possibility isn’t ruled out, but it is far less highlighted, even in online support resources.
The licensing model also hasn’t changed (per-user subscription), but the minimum number of users has increased: 50 now, up from 25 previously (or even 15 on Cameyo’s self-hosted version).
The managed version is no longer deployable on Azure: Google Cloud is now the exclusive host. It is responsible for deploying the VMs and scaling them, but not for the software—including the OS—that runs on those VMs.
Integrations with Drive and the Google Workspace Directory
On GCP, a Cameyo server can operate across six capacity levels, varying in vCPU (1 to 16), RAM (3.75 to 60 GB), and networking (no Internet access on the first two levels). Clusters can be configured for autoscaling.
For self-hosted deployments, you should plan for at least 2 CPUs and 8 GB of RAM, with Windows Server 2019 as the minimum (Windows Server 2025 is not yet supported).
Additional integrations with the Google ecosystem have been established for user authentication (SSO with a Google account) and permission configuration (Google Workspace directory). Drive has also been integrated directly into sessions (file explorer and dedicated dialog windows).
Cameyo does not support applications that require direct access to local peripherals (webcams, printers…). Nor those that rely on system-level features (screen recording, file compression…).
