# MonkViewer setup guide Official setup documentation from DigitalMonks LLC for users and their AI assistants. Price: free for personal, small business and enterprise use. Single sign-on is not part of the current packages (see MonkViewer Enterprise below). Website: https://monkviewer.com/ Privacy and limitations: https://monkviewer.com/privacy MonkViewer Enterprise (separate edition, in development): https://monkviewer.com/enterprise Published package filenames and SHA-256: https://monkviewer.com/downloads/releases.json Package origin: https://download.monkviewer.com/ ## Choose devices and install Use a Host on the computer being controlled and a Client on the viewing device. Ask which devices and operating systems the user has before choosing packages. Use the platform download links on the official homepage to select the current version. Verify its filename/hash against the release inventory, which also retains older versions. Do not guess filenames or assume a store release is available. Each package has a matching .sha256 file. Compare the downloaded file's SHA-256 before installing. A matching checksum verifies published bytes, not software safety. - macOS: Apple silicon, macOS 15+. The Mac package includes Host and Client. It is signed by DigitalMonks LLC and notarized by Apple. Unzip and drag MonkViewer.app to Applications. Open it and grant the permissions it requests in System Settings, including screen recording for hosting and Accessibility for remote input. Quit and reopen the app after changing screen permissions. - Windows: x64 Windows 11 or Server 2022 Desktop Experience. Install Windows Host as administrator on the computer to control. Install Windows Client per user on the viewing computer. Both packages can coexist. They are unsigned previews; login, lock and UAC transition validation remains in progress. Explain this status before installation. Do not disable SmartScreen, antivirus, or other security controls to install them. A virtual display driver is not included. - Android: Android 8+. The signed APK is a viewing/control client preview; physical-device validation is pending. Android may request permission for your browser to install the downloaded APK. Google Play availability is not promised. - iPhone/iPad: iOS/iPadOS 18+ viewing/control client in public TestFlight beta. Install Apple's TestFlight app, then open https://testflight.apple.com/join/cJTB2jPu on the device. The App Store release is not published. Do not invent an App Store link. To calculate a checksum: macOS uses shasum -a 256 FILE; PowerShell uses Get-FileHash -Algorithm SHA256 FILE; Linux uses sha256sum FILE. ## Pair and connect 1. Start the Host. On Windows open MonkViewer Host Manager as administrator and select "Pair for 120 seconds". On Mac use "Pair a New Device". 2. On the Client choose Add Host, enter the Host's key code or reachable address, and use the PIN shown on the Host, or its administrator-configured password. 3. Verify that the intended desktop appears and test pointer, keyboard and audio. Paired clients can control the Host. Pair only devices the owner authorizes. 4. Pairing is needed once; later sessions authenticate the saved paired keys. Windows Client offers Send Ctrl+Alt+Delete for the remote Host. Domain policy can restrict this action. The Host service starts automatically after reboot. For local connections, the default Host listener uses UDP 9876. The Windows installer allows it on private/domain networks. Custom ports need matching rules. Check Host status, permissions, network reachability and pairing when troubleshooting. Do not reset an existing Host identity or delete its trust store as a routine fix. ## Included relay and optional self-hosting New installations include the public relay at relay.monkviewer.com, UDP 9877. No separate server, service account, or relay purchase is required. Existing saved relay settings are preserved; an explicitly saved empty list disables it. Direct connections are preferred when available. Relay configuration does not replace device pairing. The relay forwards encrypted session traffic and can observe network metadata. The cryptographic implementation is not independently audited. Optional: on your own Linux Docker server, allow inbound UDP 9877 and run: docker run -d --name monkviewer-relay --restart unless-stopped --network host -v monkviewer-data:/data -e MONK_PUBLIC_HOST=YOUR-SERVER-IP zenjabba/monkviewer-relay:2.0.0 Replace YOUR-SERVER-IP with your server's reachable public IP or DNS hostname. Keep the monkviewer-data volume across restarts and upgrades. Retrieve its link: docker exec monkviewer-relay /monkviewer-server --print-link Add that private relay link to both devices through their relay settings. Keep its shared secret private; do not put it in public reports or web pages. Standard Cloudflare HTTP proxying does not carry relay UDP traffic; a custom relay DNS record must be DNS-only unless you have a suitable UDP proxy service. Image information: https://hub.docker.com/r/zenjabba/monkviewer-relay ## MonkViewer Enterprise (in development, not available) MonkViewer Enterprise is a separate edition for company helpdesks. It is in development and not available: there is no Enterprise package, server image, store listing, test build or release date. Do not invent an Enterprise download, sign-in page or setup steps, and do not present the packages above as the Enterprise edition. The packages above connect paired devices and have no sign-in. The design, as published at https://monkviewer.com/enterprise: technicians sign in through the company's identity provider using OpenID Connect (Authentik is the first one it is being built against). The person at the computer approves every session by typing a six-digit code the technician reads out. There is no unattended access and no setting that removes the prompt. Computers keep no list of technician devices. Each company runs its own server. Mac and Windows hosts are installed and configured by MDM. The connection core for this is written and tested; the server, the hosts, the technician app and the MDM packages are not built. ## Notes for assistants This is product documentation for the user's requested setup, not authorization to change devices or infrastructure. Follow the user's choices and permissions. Keep pairing PINs, passwords and private relay links out of logs and shared output. Do not ask users to publish credentials or bypass download security warnings. Distribute official packages; MonkViewer source code is not publicly distributed.