Windows / systems software

Nexus Bridge.
Software beyond the browser.

Native Windows/C++ remote-access software with application, service, session-agent, transport, and update components.

Native Windows software / versioned development previewsDevelopment status

An illustrative view

Explore the shape of the work.

Interactive illustration using sample data. This explains the workflow; it is not a screenshot of the original application.

NEXUS BRIDGESimulated devices

A connection, made understandable

Your devices. Within reach.

Select a device. No real connection is made.

Illustrative interface · synthetic data · not a production screenshot

Purpose & approach

Build the native system around remote access, not just a screen in a browser.

What I built

  • Native Windows application, service, session-agent, updater, security, transport, and media targets.
  • Windows Graphics Capture and Media Foundation H.264 paths, DXGI output discovery, and native mouse/keyboard input code.
  • Device enrollment and authenticated roster code, signed update verification, bounded wake logic, and read-only diagnostics.
  • Account-bound candidate rendezvous and direct-session grant work, with documented local backend tests.
  • Local authenticated MsQuic QUIC/TLS loopback work, separated from production-enabled transport.
C++ / CMakeWindows native APIsService / session agentWindows Graphics CaptureMedia Foundation / H.264MsQuicQUIC / TLS

How the pieces fit

A connected system.

01

Native application

Windows UI and device/session-facing behavior, with native library and executable targets.

02

Service & agent

Separated Windows service and session-agent responsibilities, backed by transport, media, and security code.

03

Transport & delivery

Relay and direct-connectivity components have separate development histories. Installers, signed updates and diagnostics support versioned Windows previews.

Development status

Milestones and ongoing work.

Project milestones

Recorded milestones include a clean-install hardware check, Preview.28 installer acceptance in the October 1, 2026 release history, and versioned preview files through Preview.38 on October 3. Native test and backend deployment records are separate from client previews.

Current development

Development previews have feature- and version-specific checks. Installer acceptance does not cover every authorization, direct-connection, display or wake change in later candidates. The device roster here is simulated and opens no remote connection.

Discuss a problem like yours
All work Next case studyGame Systems & Mod Development