Leostream expands remote desktop identity and automation

Remote desktop platforms have a difficult job.

They need to make access simple for the person trying to get work done, while giving IT teams enough control to manage identity, security, infrastructure, cost, and performance behind the scenes. Those requirements become even harder in organizations running a mixture of Windows and Linux systems, on-premises workstations, cloud instances, GPU-heavy applications, and multiple display protocols.

Leostream’s first major platform update of the year is aimed directly at that complexity.

Version 26.1 adds stronger identity-driven access, expanded infrastructure support, new DCV connection options, IPv6 compatibility, Proxmox integration, additional REST APIs, Linux domain joining, and AWS EC2 hibernation controls. Leostream’s official release notes confirm that version 26.1 is now available as an upgrade from the 2025 platform branch. 

This is not an update built around one flashy feature. It is a collection of practical changes for administrators managing remote desktops and high-performance workstations across increasingly mixed environments.

Identity takes a larger role in remote access

Passwordless access is one of the clearest improvements in Leostream 26.1.

The update extends certificate-based passwordless single sign-on to Windows Amazon DCV sessions for users who authenticate to the Leostream Connection Broker through a SAML-based identity provider. Once authenticated, users can launch supported DCV sessions without entering another password. 

For the end user, this removes another interruption between signing in and reaching the workstation.

For IT teams, the larger benefit is consistency. Authentication can remain tied to the organization’s identity provider instead of depending on users repeatedly entering desktop credentials or relying on shared account information.

This is especially useful in GPU-driven environments where engineers, designers, researchers, developers, and media teams may be connecting to expensive workstations throughout the day. Security cannot be treated casually, but it should not turn every connection into a series of unnecessary prompts.

The release announcement also lists support for OpenID Connect authentication. OIDC is built on OAuth 2.0 and gives organizations another standards-based option for connecting Leostream with modern identity providers and identity-first security environments.

Taken together, the SAML-based DCV workflow and OIDC support show where Leostream is placing its attention. The remote desktop is no longer the center of the security model. The user’s verified identity is.

DCV connections get another secure routing option

Leostream 26.1 also adds support for the Amazon DCV Connection Gateway.

Administrators can now configure protocol plans to route DCV connections through the DCV Connection Gateway instead of using the Leostream Gateway for those remote sessions. 

This gives organizations another way to design their DCV architecture.

Large environments are rarely built on one flat network. Workstations may be divided across data centers, cloud networks, security zones, departments, or customer environments. A connection gateway can help keep those resources behind controlled access layers rather than exposing every workstation directly.

Leostream still provides the brokering and policy decisions that determine which resources a user can reach. The new gateway option gives administrators more flexibility in how the final DCV session is routed.

That distinction is worth understanding. A connection broker sits between the user and the available computing resources, handling assignments, access rules, and connection decisions across the environment. The display protocol gateway then handles how the approved connection reaches the workstation.

The update gives IT teams more control over both parts of that process.

More freedom to choose infrastructure

Leostream has long presented its platform as vendor-neutral, and version 26.1 expands that approach with new Proxmox support.

Administrators can create Proxmox Centers that inventory virtual machines hosted in Proxmox, control their power states, and assign them through Leostream. The official release notes include one important limitation: provisioning new Proxmox virtual machines is not currently supported. 

Even with that limitation, the integration is useful.

Proxmox VE has become an increasingly visible option for organizations evaluating virtualization costs, licensing changes, and alternatives to larger proprietary platforms. Bringing existing Proxmox virtual machines into Leostream allows those resources to participate in the same access, assignment, and policy framework used for other desktops and workstations.

This does not turn Leostream into a Proxmox management replacement. It gives administrators a way to include Proxmox-hosted systems in a broader remote access environment.

That is a practical difference.

Many companies are not moving their entire infrastructure to one platform. They are building mixed environments and trying to manage them without forcing every workload into the same vendor’s ecosystem. Leostream’s own product positioning emphasizes hybrid and GPU-enabled environments where organizations may need several infrastructure and protocol options. 

Version 26.1 gives those organizations another choice.

IPv6 and Linux receive important updates

IPv6 support may not be the most exciting feature on the list, but it is one of the more important infrastructure changes.

Leostream 26.1 adds full support for desktops using IPv6 addresses. The release notes state that version 26.1 of all Leostream components is required, including the Gateway, Connect clients, and Agents. 

That requirement means administrators should treat IPv6 adoption as a coordinated platform upgrade rather than updating only the Connection Broker and expecting every existing component to work automatically.

For enterprises, government agencies, service providers, and cloud-first organizations already moving toward IPv6, native platform support removes the need to design around an IPv4-only remote access layer.

Linux environments also receive a useful identity improvement.

Leostream pools can now join Linux desktops to an Active Directory domain, provided the system is running the required version of the Leostream Agent for Linux. 

This helps organizations apply a more consistent identity model across mixed Windows and Linux environments. Engineering, research, semiconductor, energy, media, and software development teams often rely on Linux workstations while the broader company manages users and policies through Active Directory.

Bringing those Linux systems into the same domain structure can simplify user assignments, authentication, and machine lifecycle management.

REST APIs push more administration into automation

Manual administration works until the environment becomes too large or too dynamic.

Leostream 26.1 expands its RESTful APIs to support listing, modifying, removing, releasing, and power-controlling desktop records in the Connection Broker. 

Those operations give administrators and DevOps teams more ways to connect Leostream with the systems already running the business.

A service desk could update desktop records through a ticketing workflow. A configuration management database could synchronize workstation metadata. An orchestration tool could power systems on or off based on schedules, project demand, or user assignments. A custom portal could expose approved self-service actions without requiring users to enter the full Leostream administrator interface.

The practical value is not simply that an API exists.

The value comes from removing repetitive steps and allowing desktop management to become part of a larger automated workflow. When remote access infrastructure grows across several clouds, hypervisors, and physical workstations, manual record updates become both slow and error-prone.

The new APIs give teams more room to build around that problem.

AWS hibernation balances continuity and resource use

AWS support also receives a useful operational update.

Leostream can now provision supported AWS EC2 instances with hibernation enabled and place compatible instances into hibernation through its power-control features. 

Hibernation preserves the instance’s in-memory state rather than forcing the user to close applications and rebuild the entire working environment after a complete shutdown.

This can be helpful for users working with large development environments, complex engineering applications, media projects, simulations, or datasets that take time to reopen. The workstation can be placed into a lower-activity state while retaining more of the user’s session than a normal shutdown would allow.

It is not a universal answer for every cloud desktop. Organizations still need to consider instance compatibility, storage, security, application behavior, and their own AWS cost model.

But for supported workloads, hibernation creates another useful middle ground between leaving an expensive instance running and forcing the user to start over.

A broader update for hybrid and GPU-heavy environments as Leostream expands remote desktop identity and automation

Leostream CEO Karen Gondoly described version 26.1 as an update focused on identity-driven access while expanding infrastructure choices for hybrid and GPU-focused environments.

That is a fair summary of the release.

The identity improvements reduce credential friction and add another modern authentication path. DCV Connection Gateway support provides more architectural freedom. IPv6 prepares the platform for newer network environments. Linux domain joining helps standardize mixed operating systems. Proxmox support adds another virtualization option. REST APIs extend automation, while AWS hibernation gives cloud administrators another way to manage session continuity and resource use.

None of those features completely changes remote desktop computing on its own.

Together, they address the work that usually determines whether a remote access platform remains useful as an organization grows: authentication, interoperability, automation, network readiness, and operational control.

Leostream 26.1 feels less like a cosmetic release and more like infrastructure maintenance done in the right direction. It gives administrators more ways to connect the identity systems, clouds, hypervisors, protocols, and workstations they already have instead of demanding that everything be replaced with one tightly controlled stack.

For organizations running specialized applications and expensive GPU resources, that flexibility may be the most valuable feature of all.