Skip to content
Tech News
← Back to articles

Show HN: Winpodx – run Windows apps on Linux as native windows

read original get Wine Windows Compatibility Layer → more articles
Why This Matters

Winpodx offers a streamlined way to run Windows applications natively on Linux by leveraging Windows containers and FreeRDP RemoteApp, eliminating complex setup processes and providing a seamless user experience. Its innovative approach reduces barriers for users and developers needing cross-platform compatibility, potentially transforming how Windows apps are accessed on Linux systems. As it is still in beta, this development signals a promising step toward more integrated and user-friendly cross-platform solutions in the tech industry.

Key Takeaways

Status: Beta winpodx is in active development (v0.3.0). v0.3.0 ships a redesigned host→guest pipeline — bearer-authed HTTP agent on 127.0.0.1:8765 is now the default command channel, with FreeRDP RemoteApp kept as fallback. App launches no longer flash a PowerShell window. New winpodx check CLI + GUI Health card surface live pod / RDP / agent / round-trip / disk state. First install still takes ~5-10 minutes (Windows VM ISO download + Sysprep + OEM apply); winpodx pod wait-ready --logs shows live progress. Please file issues at https://github.com/kernalix7/winpodx/issues if something breaks.

No full-screen RDP. Each Windows app becomes its own Linux window with its real icon — pinnable, alt-tabbable, file-associated. Drop into a full Windows desktop only when you actually want one ( winpodx app run desktop ).

winpodx runs a Windows container (via dockur/windows) in the background and presents Windows apps as native Linux applications through FreeRDP RemoteApp, while a bearer-authed HTTP agent inside the guest handles the host→guest command channel without flashing a PowerShell window. No manual VM setup, no ISO downloads, no registry editing. Near-zero external Python dependencies (stdlib only on Python 3.11+; one pure-Python tomli fallback on 3.9/3.10).

Why winpodx?

Existing tools for running Windows apps on Linux all have trade-offs:

winapps LinOffice winboat winpodx Core tech Any RDP-capable Windows host (cloud / physical / container) + FreeRDP dockur + FreeRDP dockur + FreeRDP dockur (Podman) + FreeRDP + HTTP guest agent Setup Manual (shell + config + RDP testing) One-liner script One-click GUI installer Zero-config (auto on first launch) Interface CLI only CLI only Electron GUI Qt6 GUI + CLI + tray App scope Any Windows app Office only Any Windows app Any Windows app Language Shell (86%) Shell + Python TypeScript / Vue / Go Python (100%) Runtime deps curl, dialog, git, netcat Podman, FreeRDP Electron, Docker/Podman, FreeRDP Python 3.9+, FreeRDP, Podman Auto suspend / resume No No Not documented Yes (idle timeout) Password rotation No No Not documented Yes (7-day, atomic) HiDPI auto-detect No No Not documented GNOME, KDE, Sway, Hyprland, Cinnamon, xrdb Sound default No No Yes (FreeRDP) Yes (FreeRDP) Printer redirection default No No Not documented Yes (FreeRDP) USB drive auto-mapping No No Smartcard passthrough Drive subfolders → drive letters via FileSystemWatcher Discovery (auto-scan installed apps) No No Yes Yes (Registry + Start Menu + UWP + choco/scoop) Multi-session RDP No No Not documented Yes (bundled rdprrap, up to 10) Offline / air-gapped install No No No Yes ( --source + --image-tar ) License MIT AGPL-3.0 MIT MIT

winboat is the closest peer in scope and was an inspiration. We focus on a different mix — stdlib-leaning Python + Qt6 instead of Electron, deeper auto-config (auto suspend, 7-day password rotation, multi-DE HiDPI), and an explicit air-gapped install path. Both projects build on dockur/windows; that ecosystem is bigger than any one app.

winpodx vs Wine

winpodx is not a Wine replacement. Wine translates Windows API calls; winpodx runs the actual Windows OS in a container. The two solve different problems and many users have both installed.

When you need... Use Older Win32 apps, indie games, lightweight utilities Wine / Bottles / Lutris GPU-accelerated games / 3D apps (DirectX 9 – 12) Wine — DXVK / VKD3D give near-native frame rates. winpodx has no GPU passthrough by default; QEMU CPU rendering is much slower. (GPU passthrough via VFIO is a manual bring-your-own setup — not yet packaged.) Microsoft 365 with full Outlook + Teams + OneDrive integration winpodx Adobe Creative Suite (Photoshop, Illustrator, Premiere, Lightroom) winpodx — but heavy GPU effects will be CPU-bound (see GPU row above) Anti-cheat games (Valorant, EAC, BattlEye) TBD — anti-cheats vary by VM-detection policy (Vanguard needs TPM 2.0 + no hypervisor, EAC mostly blocks VMs, VAC is lenient). Test before committing. DRM-heavy software / hardware dongle apps winpodx Apps that ship kernel-mode drivers (some VPNs, security suites) winpodx Banking / tax / government tools with regional certificates winpodx Visual Studio, WinUI 3 / WinRT, .NET features Wine hasn't caught up to winpodx IE-only legacy enterprise web apps winpodx Anything where "mostly works" isn't acceptable winpodx

... continue reading