Roadmap

Remora already covers the core of TeamViewer: ID and password access, unattended access, peer-to-peer connections with relay fallback, file transfer, clipboard and chat. These are the next steps, roughly in order of impact.

Security

• Device keys and ID ownership: each device gets a key pair, and the server binds its ID to the public key, so only the original device can claim it.
• Store the permanent password in the OS keychain instead of config.json.
• Two-factor authentication and a connection audit log.

Performance

• Hardware video encoding (NVENC, Quick Sync, VideoToolbox, VA-API) for smooth full-screen video.
• Faster capture through DXGI Desktop Duplication, ScreenCaptureKit and PipeWire.
• Partial texture updates in the viewer.

Connectivity

• IPv6 for direct connections (often no port forwarding needed).
• More connection candidates (several local and public addresses), so more NATs can be traversed.
• LAN discovery, listing Remora devices on your network.

Desktop integration

• A system service, for control at the login screen and over UAC prompts, including Ctrl+Alt+Del.
• Start with the OS, plus a tray icon.
• Audio forwarding.
• Privacy mode that blanks the host's physical monitor.

Collaboration and tools

• Session recording.
• Whiteboard and annotation overlay.
• Several viewers on one host.
• TCP port forwarding, a remote terminal, a remote file browser, and wake-on-LAN.

Platforms and packaging

• Wayland, Android and iOS clients, and a browser client.
• Installers, code signing, auto-update, and a Docker image for the server.