At Doliven Group, I participate in the modernization of our client organizations’ infrastructure, migrating them from legacy, proprietary Windows desktop clients to cloud-based platforms. To maximize endpoint stability and long-term fleet manageability, we pair this software migration with a transition to the Linux desktop as a core pillar of our modern Unified Endpoint Management (UEM) strategy. However, transitioning blue-collar SMB workforces off dedicated desktop software introduces an immediate operational hurdle. It is common knowledge (and consistently proven by human-computer interaction studies) that non-technical users struggle with browser tab management, regularly losing tasks beneath chaotic tab sprawl. When established muscle memory is broken in this manner, the resulting operational disruption costs companies substantial time and money.
This friction is intensified by how these users interact with their operating systems on a daily basis. The tenants’ employees’ workflows rely almost entirely on persistent window menus and context menus for basic operations like copying, pasting, and zooming, as keyboard shortcuts are practically absent from their computing habits. To bridge the gap between web platforms and desktop familiarity, we initially evaluated Progressive Web Apps (PWAs), but they proved far too temperamental for enterprise deployment. PWAs exhibit erratic taskbar integration—most severely on Linux due to StartupWMClass mismatches that break dock pinning, icon resolution, and window grouping, alongside occasional docking failures on Windows and macOS. Furthermore, standard PWAs integrate poorly with browser profile isolation, making them impractical for shared corporate workstations.
Turning to existing application naturalizers revealed that the open-source ecosystem lacked a viable enterprise solution. Pake is an exceptionally polished utility for individual consumers, but it is unsuited for enterprise administration: it provides zero UEM policy governance, omits traditional window menus entirely, and relies on Tauri rather than Electron, introducing subtle rendering and execution discrepancies on enterprise web applications built explicitly for Chromium. Conversely, Nativefier—the historical Electron-based alternative—has been abandoned for years, offers no centralized policy governance, and forces every application to bundle a discrete ~300 MB Electron binary. Deploying dozens of enterprise applications across an entire fleet using Nativefier would waste gigabytes of storage and impose unacceptable memory overhead.
To resolve these intersecting user-experience and administrative challenges, I architected Bosun. Bosun serves as both an application packager and a centralized runtime engine, transforming cloud platforms into standalone desktop applications powered by a single, shared Electron runtime. By sharing the core binary, individual applications deploy as lightweight, ~60 KB bundles, eliminating gigabytes of redundant dependencies and enabling instantaneous builds. Crucially, Bosun reinstates the full window menus and deterministic taskbar integration (StartupWMClass) necessary to ensure the transition to both cloud platforms and the Linux desktop is seamless. For system administrators, it provides an auditable, root-owned configuration layer, a background auto-rebuild daemon that automatically recompiles applications when configurations update, and granular policy controls managed through scriptable CLI and interactive TUI interfaces.
Beyond fulfilling Doliven’s enterprise mandate, I released Bosun as an open-source project to serve the wider ecosystem, including Linux power users seeking an efficient desktop runtime. Bosun introduces advanced capabilities absent in competing naturalizers, most notably robust, in-place profile isolation that allows users to switch instantaneously between multiple authenticated accounts within the same running application without destroying the window. By uniting strict enterprise UEM governance, lean resource consumption, and native desktop ergonomics, Bosun transformed what began as an internal migration utility into an adaptable, zero-duplication application ecosystem.