Remote desktop hub
Connect to your Macs and Windows PCs from anywhere.
No device preflight has been run in this session.
Route Priority
Local network
Use the direct LAN address when both devices are home.
Private mesh
Use a private 100.x address during development and testing.
Home relay
Fall back to the Windows server bridge when direct routes fail.
Relay Plan
- Host
- Windows Home Server
- Transport
- Outbound TLS tunnel
- Public ports
- None for raw RDP or VNC
- Status
- Local prototype ready, production tunnel next
Host Readiness
Agent status has not been refreshed in this session.
Windows RDP Checklist
- Windows edition is Pro, Enterprise, Education, or Server.
- Remote Desktop is enabled in Settings.
- The Windows account has a password or supported sign-in method.
- Firewall allows Remote Desktop on private networks.
- AllReach agent confirms TCP 3389 locally.
Mac Screen Sharing Checklist
- Screen Sharing or Remote Management is enabled.
- The correct user is allowed to control the Mac.
- VNC compatibility is enabled only if needed.
- Firewall allows screen sharing on trusted networks.
- AllReach agent confirms TCP 5900 locally.
Agent Pairing Commands
Generate a one-time code and copy the host command for Windows or Mac.
Agent Registry
0 pairedLocal History
Relay Activity
Not checked
Credential Storage
Prototype profiles are saved in browser local storage. Native builds should move credentials into Keychain on Apple platforms and Credential Manager on Windows.
Network Exposure
AllReach should avoid exposing RDP or VNC directly to the public internet. The relay should broker authenticated sessions over outbound encrypted tunnels.
Pairing
Each desktop agent should be paired with a one-time code, then pinned to the account and device identity before it accepts a session.
Audit Trail
Every connection should log device, route, protocol, start time, and result locally so the owner can spot unexpected access.
App Store Plan
Ship the iPhone and iPad app as a paid upfront App Store app. The App Store page handles the purchase, so the app itself does not need subscription screens or Lemon Squeezy checkout prompts.
Google Play Plan
Ship the Android app as a paid upfront Google Play app. Keep Lemon Squeezy checkout links out of the Play-distributed app for digital app access.
Lemon Squeezy Plan
Use Lemon Squeezy for the website, Windows app, and direct Mac distribution. Keep those checkout links out of mobile store builds unless a future store-approved policy path explicitly supports it.
Direct desktop activation is separate from mobile store purchases.
Monetization Rule
The App Store and Google Play builds should be fully useful after purchase. Entitlements are still useful for Lemon Squeezy desktop licenses, support grants, trials, and any future paid relay service, but v1 should not depend on in-app purchases.
Prototype API
During prototype work these point at local mock endpoints. Native builds should replace them with the relay/account service or local agent discovery.
Profiles
Export profiles for moving between test devices. The prototype export does not include passwords.