Windows
DevelopmentExisting-display capture and multi-monitor enumeration have development evidence. Streaming, production driver signing, installer signing, and full device testing remain incomplete.
Consent stays in the room
Your screen.
Your say.
Remote display and control designed around a visible host, narrowly granted permissions, and an immediate way out—across the desk or across the internet.
Pre-release destination: account deployment is not verified and signup may be unavailable. No charge or entitlement is created here.
Studio desktop
HOST
Sharing is visible
Travel laptop
VIEWER
Direct · encrypted in transit
A deliberate connection
Three moments. No hidden fourth step.
- 01
Ask
The viewer names the exact display and permissions it needs. View is separate from input, audio, clipboard and files.
- 02
Approve
The host sees who is asking and can accept, narrow, reject or block the request. Browser sharing starts only from a local click.
- 03
Stay visible
The active host keeps a persistent indicator, duration, live permissions and a stop control for the entire session.
Capability, not wishful thinking
Built around what each platform truly permits.
Public operating-system APIs only. Missing signing credentials, hardware tests, or store approval remain visible blockers—not green checkmarks.
macOS
BlockedProduction distribution requires Apple hardware, signing, notarization, and platform testing; no production claim is made.
Linux
PlannedX11 and portal-based Wayland paths require implementation plus compositor-specific testing.
Android
PlannedViewer and explicit MediaProjection capture are planned; no hidden capture or accessibility-service misuse.
iPhone & iPad
BlockedViewer work is planned; ReplayKit host capture is view-only and needs Apple tooling, credentials, review, and physical-device evidence.
Web browser
DevelopmentA real same-browser WebRTC viewer lab exists. It does not prove two-device networking, TURN, or system-wide control.
Plans follow devices, not surveillance
Start with two enrolled devices.
Exact founding prices and limits come from one validated product catalog. Every plan remains pre-release and unavailable until local release and billing gates pass.
Free
$0No paid checkout
2devices
- 1 concurrent session
- Up to 1920 × 1080
- Up to 30 FPS where supported
Silver
$0.99/month equivalent$11.88 charged annually; annual-first founding contract
3devices
- 1 concurrent session
- Up to 1920 × 1080
- Up to 30 FPS where supported
Gold
$1.99/month equivalent$23.88 charged annually; annual-first founding contract
7devices
- 2 concurrent sessions
- Up to 2560 × 1440
- Up to 60 FPS where supported
Organization
$39.99/month$39.99 monthly or $399.90 annually
100devices
- 5 concurrent sessions
- Up to 3840 × 2160
- Up to 60 FPS where supported
Security starts with boundaries
The service coordinates. Your devices communicate.
The control plane may authorize a session and route signaling. It is not designed to keep or decrypt screen, audio, clipboard, file, chat or transient input content.
Report a security concern- 01Every controlled session stays visible on the host and can be stopped locally.
- 02Screen, audio, clipboard, files and transient input remain end-to-end between devices.
- 03Permissions are separate, explicit grants that can be paused or revoked during a session.
- 04Trusted access is off by default and must bind to a specific enrolled device key.
Downloads
Release packages are not available yet.
Unsigned, unnotarized, or hardware-untested builds are not presented as production software. Follow release notes in the repository for development artifacts and exact limitations.
Read project documentationWhy this approach
The safety model is visible before the first connection.
Screen view does not silently imply keyboard, files, clipboard, or audio.
Missing signing, APIs, hardware tests, or backend work remain named limitations.
The service is designed to authorize and signal, not become a screen-content store.