KasmVNC VS terraform

Not exactly the same thing, but I had good experience with KasmVNC.

Despite having VNC in its name, it isn't fully compliant with the VNC protocol and doesn't support regular VNC clients. Instead, it exposes a web client that you can access to connect to the machine. It also felt surprisingly snappy and nice to use compared to my previous experiences with regular VNC.

https://github.com/kasmtech/KasmVNC

- KasmVNC is a standalone open source project that powers the container steaming portion of workspaces - meaning the rendering of the container GUI environment and the keyboard/mouse interaction. KasmVNC can be used in containers, VMs or hardware. It is GPL2. https://github.com/kasmtech/KasmVNC

The rendering for container sessions is powered by our independent open-source project KasmVNC . Here is a video on some of the improvements to the streaming tech we've made in recent months. It shows an example of how performant it can be

- https://github.com/kasmtech/KasmVNC

Our bread and butter is container streaming, which allows you to instantly provision Linux desktop environments and Gui applications. But we also support remote access to any other machine you may have that are running our open-source project KasmVNC, or SSH, RDP, and traditional VNC.

I'm running Kasmvnc (https://github.com/kasmtech/KasmVNC) on KDE-Neon at the moment.

Kasm expects that it's container images are running KasmVNC . You can see that's one of the steps when we build the "core" images which all of the other images are based on. I see that Docker-OSX can support running a VNC server, but that would need to be swapped with KasmVNC . Without digging in, I'm not sure what the level of effort would be. At glance I can see there are tricks with X11/Display, and its not immediately clear what the interplay is with kvm's vnc capabilities if any.

All of the Workspaces Images (e.g Chrome , CentOS) utilize KasmVNC for the browser based rendering of the container. In the latest version for KasmVNC we added the underpinnings for WebRTC UDP transport. Its not fully plumbed into the full Workspaces platform yet, but its usable in KasmVNC standalone.

We publish example ansible playbooks , terraform projects , and STIG hardening scripts. While not suitable for all deployment, hopefully it at least shows a bit about the posture of the organization.

But we have a lot of other options all the way up to a distributed auto-scaling multi-region, multi-cloud environment - all self-hostable in your own VPCs. We have ansible, and terraform projects to help with some of that.

In those scenarios ansible and terraform projects are what they prefer.

We have ansible and terraform projects to help you with the multi-server install if you want

If deploying to one our supported cloud providers (AWS, DigitalOcean, OracleCloud) then you can leverage our Auto-Scaling feature which scales the Agent compute nodes up and down based on user load and admin preferences. (https://kasmweb.com/docs/latest/guide/zones/aws_autoscaling.html#) . Example terraform projects are available for reference of initial cloud deploys: https://github.com/kasmtech/terraform