An underserved corner of remote support

Remote-support tools for desktops are a crowded market: Splashtop, TeamViewer, AnyDesk, ConnectWise, RustDesk, and plenty of others. Mobile support is different. iPhone and Android screen sharing usually arrives as one feature inside a much broader remote-management suite, often with pricing and operational overhead built for an MSP rather than an internal IT team.

If you're an IT team supporting a mobile fleet at your own company, the available tooling can cost more than the problem is worth or solve a different shape of operation. AnchorGrid exists for that gap: focused iPhone and Android support that fits next to the help desk and desktop tools you already use.

Browser-only technician view. The technician opens a tab and pastes in a code. No desktop app, no installer, no “please update the agent first.” The viewer is a React page with WebRTC under it; that's the entire surface area to support.

Consent at the moment. Every session starts with the end-user reading a 9-digit code aloud. There is no silent-observer mode and no unattended-access flow. That puts a ceiling on what the product can do, and it's the right ceiling for support.

Direct LAN when possible. If both ends of a session are on the same network, AnchorGrid transparently uses a peer-to-peer path: single-digit-millisecond RTT instead of the ~75ms typical of a relayed connection. Falls back to the relay when strict firewalls or carrier-grade NAT demand it. The technician sees which path they're on in real time.

Customer-controlled support access. AnchorGrid staff cannot view your workspace without a grant you explicitly created. Grants expire automatically, never exceed 90 days, and every notification email includes a no-auth one-click revoke link. This is the Meraki / Verkada / Salesforce model, applied here because it's the right model.

Solo project, built by Alex Thompson. Based in Memphis, Tennessee. I work in IT and remote-support tooling is the territory I know.

Some of the architecture is documented openly: the iPhone ReplayKit pipeline, the Android MediaProjection path, bare WebRTC without an SFU or room layer, and a two-tier reconnection state machine covering ICE restart through a full WebSocket and peer rebuild. If you're curious about the technical posture, just ask.

Already shipped: Microsoft 365 SSO (per-tenant Azure apps with DNS-verified domains and just-in-time provisioning), TOTP 2FA with recovery codes, the in-app audit log with CSV export, customer- controlled support-access grants, TURN relay for strict-NAT networks.

Short term: Google Workspace SSO, Stripe self-serve billing, deeper audit-log exports, a free personal tier for individual / home-support use.

Medium term: broader device coverage, session recording with explicit consent, and richer annotation tools in the technician's view.

Long term: whatever real customers actually need. Roadmap follows demand. If you have a concrete ask, the contact page is the way to put it on the list.