When you unlock your PC from the phone, traffic spikes across relay and agent — here’s how Hazelink keeps control, files, and stats feeling instant.
Your phone never talks to a random open port on the internet. It reaches your PC through the nearest good path — local network when you’re home, or the Hazelink relay when you’re away — while accounts and pairing live in Firebase.
relay.hazelink.app · app.hazelink.app/pc/** · agent on 127.0.0.1:5000 (PC)
When you’re on the same Wi‑Fi, the phone tries your PC’s local agent address first. Away from home, traffic goes through the Hazelink relay so you don’t open ports on your router.
Hazelink is not one giant server. The PC agent, relay hub, Firebase Auth/Firestore, Cloud Functions (pairing, billing, wake), and Flutter clients each do one job. If billing is busy, remote control still runs.
Firebase Hosting and Cloud Functions scale up when many users pair or check out at once, then scale down when quiet. Your PC agent stays on your machine — we don’t rent a always-on box per user.
Games and apps catalogs, stats snapshots, and last-seen presence are cached so the home screen doesn’t wait on every network hop. The UI stays usable while the next refresh lands.
We don’t treat one flaky ping as “PC dead.” If live stats or recent last-seen say you’re online, Hazelink still opens control. The agent and relay reconnect when the link drops.
Short timeouts on LAN, longer on relay. If one base URL answers “offline,” the client tries the next. Same idea as quality that adapts — here the route adapts so actions keep completing.
You install one helper on Windows, pair with a code, and the stack picks the best route. You don’t configure CDN edges or scale groups — that’s on us. Your job is keeping the agent running (or using Wake when the PC is asleep).
Read the app guide → Open the app