v1.0.0 RELEASED · ARCH & LINUX NATIVE

Deterministic Microsecond Latency.
Zero-Copy Safe Rust.

An open-source high-performance remote desktop subsystem engineered with strict hardware buffer invariants, sub-frame pacing, AV1/HEVC zero-copy encoding, and end-to-end Noise Protocol encryption.

$ curl -sSL https://yet-another-remote-desktop.com/install.sh | bash
≤ 15.0 ms Glass-to-Glass LAN Target
480 μs Software Pipeline Overhead
0 Pixel Copy GPU VRAM Invariant
114 ADRs Architectural Specifications
HARDWARE ARCHITECTURE

Zero-Copy GPU Dataflow Invariant

Frames never touch CPU memory. Pixel data remains in GPU VRAM from capture through network packetization.

Hardware Memory Highway & Data Flow
STAGE 01 SELECTED
HOST GPU VRAM DOMAIN PCIe VRAM Isolated
01 DRM KMS Scanout
≤ 2.0 ms
02 DMA-BUF Bridge
0 μs (DMA)
03 HW ASIC Encoder
≤ 3.5 ms
NETWORK TRANSPORT Sub-Frame Slices
04 Sub-Frame Pacer & AEAD
≤ 0.5 ms
05 Unreliable Network Ring
RTT / 2
CLIENT GPU WORKSTATION WebCodecs Swapchain
06 WebCodecs GPU Raster
≤ 1.5 ms
BYPASS VERIFIED Host CPU & System RAM: 0 Bytes Copied
Invariant: Direct GPU Framebuffer -> DMA-BUF -> NVENC ASIC
STAGE 01

DRM KMS Scanout

≤ 2.0 ms Budget
Kernel FFI / Driver Interface drmModeGetFB2() / drmPrimeHandleToFD()
Input Buffer Descriptor Hardware CRTC Framebuffer (VRAM)
Output Zero-Copy Handle DMA-BUF File Descriptor (dmabuf_fd)
Zero-Copy Invariant Guarantee Zero compositor blitting; direct primary scanout plane acquisition.

Accesses active kernel framebuffer memory directly from the display controller scanout plane. Captures atomic hardware vblank interrupts without copying through X11, Wayland, or desktop window compositors.

CODEBASE DOCUMENTATION

Technical Architecture Wiki

Comprehensive reference documentation for every crate, wire protocol specification, and platform driver.

ARCHITECTURE yard-core

Zero-Copy Buffer & Safety Invariants

The 5 immutable system rules: zero CPU pixel copy, microsecond budgets, compiler safety, and fault isolation.

ENGINEERING GOVERNANCE

Architecture Decision Records (ADRs)

Complete database of all 114 traceable engineering decisions governing the YARD engine.

114 / 114 Documented
/
EMPIRICAL MEASUREMENTS

Microsecond Latency Benchmarks

Measured across 1,000 continuous software pipeline iterations and transport loss cycles.

YARD Zero-Copy Engine Zero Lookahead
480 μs (0.48 ms p50)
Software Pipeline Overhead 491 μs p99

Direct DMA-BUF to NVENC/VA-API pipeline with zero CPU pixel copies.

Traditional Remote Desktop (VNC / RDP) CPU Buffering
35,000 μs (35.0 ms)
Software Pipeline Overhead 65,000 μs p99

Frame grabbing via CPU memory buffers, software scaling, and TCP head-of-line blocking.

Software Pipeline Latency Distribution (Microseconds, 120Hz)

1000 Continuous Iterations
Software Pipeline Stage p50 (μs) p95 (μs) p99 (μs) Max (μs) Design Budget Ceiling
CPU Slicing & Dispatch 0 μs 0 μs 0 μs 6 μs ≤ 100 μs
Noise AEAD Cryptography 478 μs 485 μs 488 μs 681 μs ≤ 1000 μs
Pacer & Jitter Reassembly 1 μs 2 μs 3 μs 9 μs ≤ 1500 μs
Total Software Pipeline 480 μs 487 μs 491 μs 1568 μs ≤ 2600 μs
DEPLOYMENT & INTEGRATION

Self-Hosting & Linux Quickstart

Deploy YARD natively as a systemd service or integrate the WebCodecs player into your homelab dashboard.

Arch Linux / AUR / Automated Script 
# 1. Download and run automated Linux installer
curl -sSL https://yet-another-remote-desktop.com/install.sh | bash

# 2. Verify systemd streaming daemon status
systemctl status yard-host.service