Products › RDP
Remote Desktop for Linux
Wayland-native RDP — server, clients, open-source foundations, and the research that informs the work
RDP on Linux, built for Wayland
RDP is the best-understood remote-desktop protocol in the industry — well-documented, multi-vendor, supported by every Windows install and most thin clients. On Linux, the story has been weaker. The dominant server (xrdp) is an X11-era bridge: good enough for legacy desktops, but it can’t run on Wayland, can’t use hardware encoding cleanly, and can’t share clipboard formats or files.
Lamco Development LLC’s RDP focus area is the alternative: an RDP server built for Wayland, open-source Rust foundations published for the whole ecosystem to use, and a growing set of client and automation tools. The anchor product is Lamco RDP Server; everything else in this focus area either builds toward it, alongside it, or on top of it.
RDP on Linux is separately a prerequisite for Proxmox integration and the upcoming VDI work — those are co-equal focus areas that reuse this foundation. See the Proxmox focus area for the VM-access integration story.
Legacy Linux RDP vs. Lamco RDP Server
X11 + xrdp (legacy stack)
- — Requires an X11 session; won’t run on modern Wayland-only distros
- — Software-only encoding, CPU-bound, no GPU path
- — Text-only clipboard; no file transfer, no image paste
- — No HDR, no 10-bit color, single monitor
- — Capture via X SHM — incompatible with Wayland security model
Lamco RDP Server (Wayland-native)
- — Runs natively on GNOME, KDE, sway, Hyprland, and every wlroots compositor
- — VA-API / NVENC hardware encoding; H.264, H.265, AV1
- — File clipboard via XDG Desktop Portal; image and text both work
- — 10-bit HDR, multi-monitor, per-output DPI
- — Capture via PipeWire screencast — the sanctioned Wayland path
How the pieces stack up
┌───────────────────────────────────────────────────────────────────┐
│ Application layer │
│ • Lamco RDP Server (BSL 1.1 → Apache-2.0 2029) │
│ • lamco-rdp-tools (CLI) (MIT/Apache-2.0, v1.1.1) │
│ • lamco-rdp-console (PVE) (coming soon — Proxmox focus) │
│ • lamco-qemu-rdp (per-VM) (coming soon — Proxmox focus) │
└─────┬─────────────────────────────────────────────────────────────┘
│
┌─────▼─────────────────────────────────────────────────────────────┐
│ Protocol layer — lamco-rdp meta-crate │
│ • lamco-rdp-input (scancode, coordinates) │
│ • lamco-clipboard-core (protocol-agnostic utilities) │
│ • lamco-rdp-clipboard (IronRDP CliprdrBackend) │
│ on top of: ironrdp-cliprdr, ironrdp-core (Devolutions) │
└─────┬─────────────────────────────────────────────────────────────┘
│
┌─────▼─────────────────────────────────────────────────────────────┐
│ Capture layer — lamco-wayland meta-crate │
│ • lamco-portal (XDG Desktop Portal) │
│ • lamco-pipewire (PipeWire capture + DMA-BUF) │
│ • lamco-video (frame pipeline, RDP bitmaps) │
└─────┬─────────────────────────────────────────────────────────────┘
│
┌─────▼─────────────────────────────────────────────────────────────┐
│ OS layer │
│ Wayland compositor · xdg-desktop-portal · PipeWire │
└───────────────────────────────────────────────────────────────────┘
Lamco RDP Server
Clients, automation, and tooling
lamco-rdp-tools
v1.1.1Two RDP command-line tools for Linux and Windows: rdpsee inspects a server (pre-auth scan, certificate, fingerprint, capabilities, screenshot) and rdpdo drives one, the way vncdotool drives VNC, with visual matching, audio verification, and CI output. The same team tests Lamco RDP Server with these tools, and they work against any standards-compliant RDP server. MIT OR Apache-2.0.
View product →
RDP GUI client
IN DEVELOPMENTA standard RDP desktop client. Primary role today: backbone for downstream releases (tools, console, tests). Later: may ship as a separately-released end-user client.
lamco-probe
IN DEVELOPMENTA diagnostic for the Wayland stack beneath remote desktop. It inspects the local substrate an RDP server runs on (EIS input injection, PipeWire capture, the XDG Desktop Portal, and the Wayland protocol extensions) and reports health, compatibility, and timing on a given compositor and version. Where rdpsee and rdpdo work over the RDP protocol against a server, lamco-probe looks at the layer underneath. A free companion, in development; dedicated page when it’s ready.
RDP test client
INTERNALPrivate integration-testing client used against the server in CI. Not a distributed product; mentioned for completeness.
Published Rust crate families
lamco-wayland
meta v0.6.3 · portal / pipewire / video
Wayland screen capture, XDG Portal integration, frame pipeline, and RDP bitmap conversion.
Browse crates →
lamco-rdp
meta v0.6.3 · input / clipboard-core / clipboard-rdp
RDP protocol extensions on top of IronRDP — input translation, clipboard interoperability, file transfer.
Browse crates →
How the work gets done
Why Wayland-native matters and how we talk to compositors
H.264, H.265, AV1 and the multi-codec story
10-bit, HDR, and getting color through RDP intact
Latency, framerate, and where the budgets go
How RDP endpoints announce themselves on a network
Multi-codec pipeline, capture timing, and ongoing research
Related focus areas & pages
Where the RDP foundation is integrated with Proxmox VE — browser console, per-VM RDP, host health.
The full set of published Lamco libraries — Rust crates, NetKit on Maven Central, Laminate.
Flatpak, Snap, native deb/rpm, source tarball — the distribution surface for the server.