Family Controls — closed beta
- The thing the 1.0.26 changelog promised. A parent on one machine can hard-lock specific apps and websites on a child's machine, at any time, from anywhere. Cloud-synced rules, real-time push, anti-bypass enforcement on the child side.
- How it works. Parent signs up on their own machine, generates a 6-digit pairing code, enters it on the child's machine. From then on, the parent's dashboard shows the child's device with a live online dot, a block-now form (apps + domains), an audit log of what's happened, and an emergency-unblock button when something gets stuck.
- The threat model FocusLock can actually defend. Killing the daemon (auto-restart watchdog), editing the family-rule cache (HMAC-signed, tamper-detected), rebooting into Safe Mode (Windows registers the service to start there too), uninstalling via Settings → Apps (now requires explicit parent authorization with a 15-minute window from inside FocusLock), and — opt-in — renaming a blocked binary (Windows Firewall blocks per-EXE-path, macOS pfctl blocks per-IP when daemon's been offline > 5 minutes).
- The threat model FocusLock can't. A kid with administrator rights, a Linux USB boot, or BIOS access defeats all of this in minutes. The parent dashboard surfaces this directly — it now enumerates every local administrator account on the device by name with platform-specific instructions for demoting them. Nothing else FocusLock does matters until that step is done.
- Closed beta. Free during the beta, then ~$5/mo per family for the hosted cloud once it stabilizes. Single-device FocusLock stays free forever. The full backend is open-source under the same GPL repo, so anyone can self-host their own family server and stay free that way too. Beta details + setup guide →