Remote Access & PAM

A migration that shipped every release

A big-bang rewrite of a codebase this size was never on the table: too much risk, too long without shipping. Instead, the team used Avalonia’s native embedding to host Avalonia views inside the existing WinForms application, then migrated thousands of views across one at a time. Users kept getting releases on schedule while the UI changed underneath them. Each migrated view retired a piece of the old stack, and the WinForms shell shrank as the Avalonia surface grew.

From half to all of it in four months

The first half was the slow half. By late April 2026 the team announced 50% of RDM’s Windows UI converted; by 20 August it was 100%, with the patterns, themes, and custom controls built in the first half carrying the second at pace. Every DevExpress component is gone, with Avalonia’s TreeDataGrid taking over the data-heavy grids RDM is known for. What remains of WinForms is a thin host layer around the Avalonia UI, and removing it is, in the team’s words, only a matter of time.

Partnership

Backing the framework they build on

Devolutions didn’t just adopt Avalonia; they funded it. In June 2025 they committed $3 million over three years to Avalonia’s open-source development, an infrastructure investment in the framework their flagship now runs on. That sponsorship let Avalonia double its team, open-source previously paid features like Wayland support and the WebView control, and make the IDE extensions free. The improvements their migration leaned on were, in part, improvements they made possible for every Avalonia developer.