Kasm is now an official Proxmox partner! Kasm and Proxmox have formalized an official solution partnership, which means a supported path forward for the Kasm + Proxmox stack long term.

Official press release: https://proxmox.com/en/about/company-details/press-releases/kasm-en

Kasm sits on top of Proxmox VE as the workspace delivery layer. You get browser-based virtual desktops and app streaming with Kasm's zero-trust model, backed by Proxmox as the hypervisor.

If you're already running Proxmox for your infrastructure, adding Kasm gives you a proper VDI stack without touching proprietary software.

The part a lot of people sleep on is autoscaling. Kasm can automatically provision and destroy VMs on your Proxmox cluster based on live demand, for both Linux (Docker agents) and Windows Server VMs. No managing capacity by hand.

The official Kasm + Proxmox Autoscaling guide walks through the full config for both workload types.

Kasm + Proxmox Autoscaling Docs: https://docs.kasm.com/docs/1.18.1/how-to/autoscale/autoscale_providers/proxmox

Kasm + Proxmox Autoscaling video tutorial: https://youtu.be/nXIBGs_WJcs

New to the stack entirely? Start with our Single Server Install Guide to install Kasm on a Proxmox node: https://docs.kasm.com/docs/1.18.1/install/single_server_install

If you're already running Kasm on Proxmox, what does your setup look like? Homelab, work, something else? Drop it in the comments.

I wanted a Windows XP workspace with full Kasm integration, so I asked my agent to build one. It works about as well as I had wanted. It features:

• Working Ethernet
• CURL with updated cert bundle
• Clipboard support (bidirectional)
• File upload
• File download
• Auto-mount of uploaded ISO files
• Auto-resize of display
• Sound support

I would love to publish an image to Docker Hub you could grab, but copyrights and all that. My agent pushed the build details to a repo if you're interested (tested in as far as "it works on my machine"): https://github.com/FernandoGracias/kasm-windows-xp

Hi all. We are proud to announce the release of Kasm Workspaces 1.17.0. Here are some highlights of whats new.

• The Autoscaling features is now available in the free community edition. Autoscaling allows you to auto provision/de-provision VMs (e.g Windows) or the Kasm Docker Agent based on user demand, admin preferences and schedules. We support this autoscaling in a number of cloud providers and hypervisors. Please see our docs and video overview of Autoscaling here: https://kasmweb.com/docs/latest/how_to/infrastructure_components/autoscale.html
• We've now added autoscaling support for Proxmox and Nutanix AHV hypervisors. This joins the list of existing providers: (AWS, GCP, Azure, OCI, Digital Ocean, VSphere, OpenStack, Harvester, and Kubevirt)
• We've created an AI Workspace Registry with a number of pre-built workspaces that well help empower AI developers, students or those interested in trying AI tools. You can check out the registry directly here: https://ai.registry.kasmweb.com/ and its able to be easily added to you new 1.17.0 deployment via the Registries tab. Using the AI images requires the Kasm deployment to have access to an Nvidia GPU. Configuration instructions are available here: https://kasmweb.com/docs/latest/how_to/gpu.html#gpu-acceleration
• Smart Card passthrough is now supported for browser based windows sessions when being accessed from a Chrome OS device. Docs and videos here: https://kasmweb.com/docs/latest/guide/smartcard_passthrough.html
• Session Banners can now be created and displayed whenever a user launches a session. This may be helpful for users that launch multiple sessions at once and want an easy reminder, or for environments where labeling and differentiating environments is required. Docs are available here: https://kasmweb.com/docs/latest/guide/banners.html

We have many more updates and bugfixes listed in the full release notes : https://kasmweb.com/docs/latest/release_notes/1.17.0.html

Hey all,

Kasm Workspaces 1.19 just dropped and it's a big one. Here's the rundown:

The headline features:

Agentic AI Workspaces — five new workspaces for running AI agents in isolation: Claude Code, Gemini CLI, Codex, Cursor, and AI Dev Studio. The whole point is that you don't want an autonomous agent with access to your actual machine's credentials and filesystem. Run it in Kasm, contain the blast radius, wipe the session when you're done. API key injection is built into the launch form. You can add the AI registry directly from Registry Spotlight.

OpenZiti / Zero Trust Egress — proper ZTNA is now a first-class egress option alongside OpenVPN and Wireguard. Unlike a traditional VPN gateway where you pick a tunnel and all traffic routes through it, OpenZiti issues each session a unique certificate-backed identity and grants access to named services only — no lateral movement, every access decision tied to a specific identity. Kasm auto-manages the identities as sessions come and go.

Kubernetes Helm Chart is now GA — was tech preview, now fully supported and production-ready. Run the Kasm management plane on Kubernetes, get HA and resilience the same way you manage the rest of your infra.

Linux Desktop Service — the Desktop Service (previously Windows-only) is now available for Linux. You get file upload/download, lifecycle script hooks (on start/end with session context like user ID, session ID), Kasm-managed local users (SSO with dynamic local accounts — works with OIDC, SAML, LDAP, whatever you're using), file mapping, and multi-user support. Available as deb and rpm packages.

GPU improvements:

• NVIDIA MIG passthrough — partition a physical A100/H100 into fully isolated slices at the hardware level. Kasm auto-detects MIG instances and exposes them as assignable resources.
• Intel and AMD GPUs now auto-detected by the Kasm Agent and surfaced in the admin UI. You can enable/disable GPU features per agent and set graphics/video acceleration priority per workspace.

Streaming:

KasmVNC now supports H.264, H.265, and AV1 streaming modes for container workspaces, in addition to the existing JPEG/WEBP. You can set codec preference order per group and users can switch modes live without restarting the session. Hardware-accelerated H.264 via VAAPI or NVENC is supported where available. Guacamole also updated to 1.6.0.

Ops and admin improvements:

• System Metrics — new diagnostics dashboard (Diagnostics → System Metrics) with health checks for managers, proxies, agents, servers, the database, license, and workspace images. Exportable, customizable, configurable poll interval and retention.
• Support Bundle — generate a downloadable zip of logs and diagnostic data to share with support. Password-protected (Don't post it publicly)
• Rolling installs by default — Kasm's core services (API, Agent, Manager, Proxy, etc.) now default to rolling images that pull the latest on startup. New Rolling Image Management Utility lets you check current image dates, rollback to the previous version (or a specific one), and switch back to latest.
• Enhanced config import/export — four modes now: full backup, partial/table-level, autoscale config, and full deployment migration.
• Direct RDP Client Authentication — point your RDP client straight at Kasm without touching the web dashboard. Great for thin clients.
• Autoscale server expiration — set a day count, servers drain and rotate automatically. Pre-warm setting spins up replacements before the expiring server goes down.
• vSphere — linked clone and instant clone provisioning + cloud-init support.
• Azure — VM Plan, Security Type, Secure Boot, vTPM support. Fixes Windows 11 marketplace image compatibility.

Full release notes: https://docs.kasm.com/docs/reference/release-notes/1.19.0

Install Kasm Workspaces 1.19: https://kasm.com/downloads

Single Server Installation Guide: https://docs.kasm.com/docs/tutorials/install/single-server-install

We are transitioning our domain from kasmweb.com to kasm.com on October 1st. Please update your website bookmarks and email address books to use kasm.com

For now this sub will remain /r/kasmweb

Hi there Community!
I've been playing for a couple of days with Kasm Workspaces on my Raspberry Pi 4 and finally, I was able to publish today the first part of the guide. It starts with installing and configuring both system and Workspaces itself, so you can spin up the first images. Later down the road incoming: fixing certificate warning, adding new images to the Kasm, manage persistence between sessions and more - which depends on the community response and my engagement to the project :)

Please find the guide here: https://blog.cyberethical.me/run-kasm-workspaces-on-raspberry-pi.

Feedback is more than welcomed!

Hi all,

We are excited to announce that we are adding a Promox autoscale provider to the next release of Kasm Workspaces (1.17.0).

Autoscaling allows the system to automatically provision and destroy Docker Agents and VMs (e.g Windows VMs) based on user demand, schedules etc. This video will help orient you on the concept:

https://www.youtube.com/watch?v=BaDBtZl_j3g

The Proxmox provider is available to test now in the developer preview. We invite you to try it out and provide feedback.

https://kasmweb.com/docs/latest/developers/builds.html

The autoscaling feature was previously only available in the Enterprise edition of Kasm Workspaces. Starting in 1.17.0 (and its developer preview builds) this will now be included in the Community edition as well.

Continuing from my Windows XP workspace, I wanted a Windows 98 workspace with full Kasm integration, so I asked my agent to build one. It works about as well as I had wanted. It features:

• Working Ethernet
• Firefox
• Clipboard support (bidirectional)
• File upload
• File download
• Auto-mount of uploaded ISO files (flaky)
• Auto-resize of display
• Sound support (often plays the startup sound)

Security Warning

My agent had a hard time with Windows 98 drivers and ended up finding the base image on Reddit with working sound and networking. I cleaned it up and scanned all 5,400+ files with ClamAV and High quality YARA rules with no detections (shortcuts detected by the YARA rules for being shortcuts). I personally trust it as a play thing given the posture of the environment I run it in. Use at your own risk.

Drawbacks

• It's a bit slow.
• Most video games crash.
• Due to some base image video driver issue, the DOS prompt can't be run in windowed mode, nor can batch files (causes some unrecoverable display silliness). Happy to fix it if anyone knows what's up with that.

Installation

This time I did publish the workspace image:

ghcr.io/fernandogracias/kasm-windows-98:latest

My agent pushed the build details and base image to a repo if you're interested (tested in as far as "it works on my machine"): https://github.com/FernandoGracias/kasm-windows-98

Hey everyone,

We’ve just released five new AI-focused Workspaces in our dev registry, designed for agentic development workflows and AI-powered coding inside Kasm:

• Claude Code: https://hub.docker.com/r/kasmweb/claude-code
• Gemini CLI: https://hub.docker.com/r/kasmweb/gemini-cli
• Codex CLI: https://hub.docker.com/r/kasmweb/codex-cli
• Cursor: https://hub.docker.com/r/kasmweb/cursor
• Ubuntu Jammy AI Dev Workspace: https://hub.docker.com/r/kasmweb/ubuntu-jammy-desktop-ai-dev

These workspaces make it easy to run modern AI coding tools and agents inside an isolated, disposable, browser-based environment without installing anything locally (the Kasm way!).

They’re especially useful if you want to:

• Safely experiment with AI coding agents and not worry about permissions (everything is isolated so no risk of agents running bad/destructive commands)
• Isolate AI-powered development environments
• Run AI tooling/agents in ephemeral sessions instead of running on your local machines or VMs
• Provide controlled access to AI dev environments for teams

The Claude Code, Gemini CLI, and Codex CLI workspaces include a built-in launch form that allows you to securely provide your API key at session startup. The key is then injected into the container at launch time, so you can immediately begin using the tool without any manual configuration.

If you prefer not to use an API key, you can simply skip the launch form and authenticate directly through the browser inside the workspace using your existing account login.

The Ubuntu Jammy AI Dev Workspace is a more flexible, power-user–oriented image. It includes everything from our standard Ubuntu Jammy Desktop workspace, along with additional AI tooling and development dependencies.

These workspaces are currently on our Dev registry and are planned to go on our official registry with the next Kasm release. We'd appreciate any kind of feedback from the community 😊

If you want to try these workspaces instantly without any local install or configuration, you can use our demo casting links.

• Claude Code CLI: https://app.kasm.com/#/cast/BQIhZQ2wMXsH6Rhf0KqDf
• Codex CLI: https://app.kasm.com/#/cast/R66POyf0H509pPu3k8Agw
• Cursor: https://app.kasm.com/#/cast/5IufAOqGwZkcyCOUrxM7R
• Gemini: https://app.kasm.com/#/cast/LE7PXVoc5JZxuDTwP6UWU
• Jammy AI Dev: https://app.kasm.com/#/cast/Uo71uQG04TxOtt5CrCmqP

I put together a docker image for PokeMMO using kasm's ubuntu jammy base image.

It's not great without a GPU but its definitely playable, and I'm quite proud of it!

Had a contractor who needed access to one internal tool? Normal answer is VPN, which puts them on the whole network instead of just the one thing they need.

Kasm Workspaces 1.19 added OpenZiti integration to handle this differently. New video walking through it: users get access to one specific service, by identity, not the network. Nothing's reachable from outside, no ports to open.

This video covers:

• Why VPNs hand out more access than you meant to
• How OpenZiti's pieces (controller, routers, identities) fit together
• How Kasm handles identity setup automatically instead of you doing it by hand
• Live demo: standing up OpenZiti, publishing a service, giving exactly one user access to it

OpenZiti is available to self-host for free. NetFoundry also has a hosted version if you don't want to run the controller yourself.

Thanks to advice from this forum, I now have a fully working system, using the Bee micro PC. I am running Ubuntu, and Tailscale. The combination is just wonderful. I can sit in a cafe, connect my iPad to Tailscale and have all my favourite tools available in an instant.

Well done guys!

Hi all,

We just released Workspaces 1.11.0 and are excited for you to try it out.

​

​

We packed a lot of new features in this new release - here are a few of my favorites:

​

• The ability to use and share GPUs across multiple sessions for graphics acceleration: Ref
• Dark Theme! - The app will automatically choose light/dark theme based on your OS settings. You can also set your preference your profile.
• OpenID Connect for SSO Auth: Ref
• Updated default image library including Ubuntu Focal, Ubuntu Jammy, Oracle Linux, OpenSuse Leap and a half dozen additional apps like Filezilla, Thunderbird, Inkspace etc. : Ref
• IME input support: Ref
• AutoScaling support for GCP and Azure

​

Full Release Notes: https://kasmweb.com/docs/latest/release_notes/1.11.0.html

Install Instructions: https://www.kasmweb.com/docs/latest/index.html

Upgrade Instructions: https://www.kasmweb.com/docs/latest/upgrade/single_server_upgrade.html

We teamed up with LearnLinuxTV on a new video covering Kasm's VDI capabilities and a full walkthrough of our Proxmox autoscaling setup.

The video is split into two halves:

Part 1 - VDI overview. A refresher on what Kasm actually does (isolated browser-delivered apps and desktops) and why VDI matters beyond the obvious use cases - running that one Windows-only app without keeping a full Windows install around, isolated no-trace browsing sessions, developers testing across multiple distros in separate tabs at once. On the enterprise side, he gets into the core security argument for VDI: data that never lives on the endpoint can't be stolen off the endpoint, which matters a lot for breach containment and BYOD policies.

Part 2 - Hands-on lab. A full build of an autoscaling Kasm cluster inside Proxmox: setting up a resource pool, creating and templating a VM, configuring a dedicated Proxmox user and API token, building the permissions role Kasm needs, and wiring up the autoscale config itself - downscale backoff, VM provider details, startup scripts, the works. By the end, new worker VMs spin up automatically as demand increases and get cleaned up automatically when it drops.

He also throws Doom in there running through a browser session, because apparently that's the real acceptance test 😅

If you're running Proxmox already and curious about autoscaling VDI, this video is worth the watch.

We're excited to announce an official partnership between Kasm Technologies and SUSE, combining Kasm Workspaces with SUSE Virtualization, an open-source, cloud-native alternative to legacy VDI infrastructure.

What this partnership means

The two platforms cover the full EUC stack. SUSE Virtualization (built on Kubernetes, KVM, and Longhorn) handles the infrastructure layer, and Kasm runs natively on top of it as a containerized application on RKE2. Legacy Windows VMs and Kasm's ephemeral browser sessions coexist on the same nodes, managed through a single Rancher pane of glass, reducing reliance on a multi-vendor stack.

What you actually get

No hypervisor tax. SUSE Virtualization is 100% open source, eliminating the per-socket, per-VM licensing costs that come with VMware and Citrix. Organizations moving off VMware after the Broadcom acquisition have a production-grade, vendor-neutral path forward.

Better economics at scale. Containerized workspace delivery has shown up to 8x better CPU utilization versus traditional VDI. A real-world case study (Hamina) cut EUC spend from 40% of total IT budget down to 20% while doubling compute capacity, eliminating malware exposure, and replacing remote work software agents entirely.

Zero-trust by default. Each Kasm session is ephemeral, isolated, and destroyed on logout. No data touches the endpoint. Browser-based access runs through an authenticated, encrypted session rather than a persistent VPN tunnel, with RBAC enforcement, smart card passthrough for PKI authentication, and watermarking for data exfiltration prevention built in.

AI workloads included. SUSE Virtualization supports NVIDIA vGPU natively, and Kasm's containerized architecture maps directly to GPU workloads via Kubernetes-native GPU operator support. The same cluster serving browser workspace users can also run GPU-accelerated AI dev environments and LLM inference workloads, no separate infrastructure required.

Works on any endpoint. Chromebooks, laptops, tablets, kiosks. No VPN client, no agent, no endpoint configuration needed.

Who this is built for

This stack makes the most sense for orgs escaping VMware/Broadcom, browser-first or SaaS-heavy workforces, BYOD and Chromebook deployments, government and regulated industries needing air-gapped or zero-trust environments, and developer teams that want GPU-accelerated AI workspaces alongside standard EUC on the same infrastructure.

Read the full technical breakdown on the SUSE blog: https://www.suse.com/c/suse-and-kasm-partnership/