DualOS
Join waitlist

A solo project · in development

Two computers.
One workspace.

Move Windows apps onto your Mac like they belong there. Keep the Windows interface, use your Mac display, and control both computers as one workspace.

Join the waitlistSee in action ↓
Windows app
Same app.Now in front of you.
Window shown on Windows PC.

Drag the title bar—or tap either screen—to move the window. The app keeps running on Windows.

The problem

Your other computer shouldn’t feel remote.

I like both operating systems for different reasons. What I don’t like is reaching for another keyboard, switching inputs, or trapping an entire desktop inside a remote-desktop window.

DualOS lets Windows and Mac share the same workspace. Move individual Windows apps onto your Mac display, control both computers with the same mouse and keyboard, and work across them without thinking about which machine you’re using.

Real prototype demo

This is the real build.

One take, two machines. A Windows app moves from the PC monitor to the MacBook while it keeps running on Windows.

Test it early →

Current state

A working prototype, not a launch-ready product.

I want to be clear about what exists and what still needs work. The labels below will change as I test more real setups.

Everything below runs on exactly one pair of machines — an RTX 5080 Windows 11 PC and an Apple Silicon Mac on the same network. Nothing has been tested on any other hardware yet.

Needed today: Windows 11 with an NVIDIA GPU, and an Apple Silicon Mac. AMD and Intel GPUs aren't supported yet.

Working

(I use these daily)

  • Use one keyboard and mouse across Windows and Mac
  • Open Windows app windows on the Mac
  • Drag Windows windows to the Mac — and back again
  • Control Windows apps with the MacBook keyboard and mouse
  • Copy and paste text and images between Windows and Mac
  • Connect over local Ethernet/LAN or Tailscale

Early

(Works when I try it, more testing is needed)

  • The real Windows Start menu, opened and clicked from the Mac
  • HEVC streaming at 3456×2144, 120 Hz target
  • Optional 10-bit 4:4:4 quality mode
  • Wi-Fi-only connections
  • Native Mac app windows on Windows
  • Multi-monitor and mixed-DPI setups

Not built yet

  • Audio streaming
  • File and disk sharing
  • Full Mac desktop control from Windows
  • AMD and Intel GPU support
  • Game mode for fullscreen games
  • Hardened first-time pairing

Security

Direct connections.

Your screen and your keystrokes go device to device. They travel directly between your PC and your Mac over your LAN or Tailscale, never through a server. Licences and updates talk to a server; your workspace traffic doesn't.

DualOS needs real privileges to work. It injects keyboard and mouse events, captures window contents, and installs a virtual display driver on Windows. On the Mac that means granting Accessibility and Screen Recording. The agent shows which permissions are active, and macOS lets you revoke either at any time.

Known weakness: first-time pairing. Today it sends the shared secret over plain HTTP on your local network — someone watching that network at that moment could capture it. The hardened replacement is designed but not built. Until it ships: pair only on a network you control.

How it's built →Website privacy notice →

FAQ

Short answers.

What is DualOS?+

DualOS makes a Windows PC and a Mac work as a single workspace. One keyboard and mouse control both machines, the clipboard is shared, and Windows application windows can be dragged onto the Mac desktop, where they sit alongside native Mac applications.

How does DualOS differ from Synergy or remote desktop software?+

Input-sharing tools such as Synergy move the pointer between machines; the applications stay where they are. Remote desktop software places an entire desktop inside a window. With DualOS you drag a live Windows application window across to the Mac the way you would between two monitors — it spans both screens mid-drag.

Does an application move between operating systems?+

No. It continues running on its original machine. DualOS brings the window and its controls to the other screen.

What latency should I expect?+

A median of just under 10 ms from capture on the Windows PC to display on the Mac, at 3456×2144 in 10-bit 4:4:4 HDR over wired Ethernet. Measured on a single hardware setup; checking it on others is what the first test group is for.
Full measurements →

What hardware is required?+

A Windows 11 PC with an NVIDIA GPU and an Apple Silicon Mac, both on the same local network, or connected over Tailscale. AMD and Intel GPUs are not supported yet.

Does it work away from home?+

Yes, over Tailscale. Latency then depends on the connection between the two machines.

What happens if the connection is interrupted?+

If the connection drops, DualOS is designed to return control to the local computer and release remotely held keys and mouse buttons. You can also force a local release with Control + Option + Shift + Esc on Mac, or Ctrl + Alt + Shift + Esc on Windows.

When will it be available?+

DualOS is a working prototype and is not yet available to download. Testing begins in small groups this autumn, and invitations follow the waitlist order among people whose hardware the current build supports.

What will it cost?+

$15 per month once the product is released. Early testing is free, and participants in the early test groups keep a reduced rate afterwards.

Who develops DualOS?+

One developer. The project has been in active development since June 2026.

Is DualOS the final product name?+

No. DualOS is a working codename; the released product will use a different name.

Waitlist

Follow the build.

I’ll send occasional, meaningful updates: the real demo, testing invitations and important progress. Not a weekly startup newsletter.

No spam and no sold data. Privacy notice.

Open problems

The hard parts.

I'm one person, and there are parts of this I can't take further alone. Some of what's open:

  • AMD and Intel encoder paths. Everything currently runs on NVENC.
  • Mixed-DPI setups — keeping a window the same size as it crosses between machines running at different scales.
  • Concurrent hardware encoder limits, and what to give up when a machine runs out of them.
  • Driver attestation and a signed installer.

If this is the kind of thing you work on, I'd like to talk.

Get in touch →