Security Cameras & NVR

View live RTSP camera feeds and manage your local Network Video Recorder (Frigate, Blue Iris, Shinobi) from anywhere without paying for proprietary cloud video subscriptions.

Frigate NVR RTSP Streams Zero Cloud Subscriptions Encrypted Remote Viewing

Reclaiming Video Privacy from Vendor Clouds

Commercial smart camera vendors require ongoing monthly cloud subscriptions to view high-definition feeds outside your home network. Worse, your private video footage is routed through third-party servers outside your control.

Local NVR systems—like Frigate, Blue Iris, or Scrypted—keep all video processing and AI object detection safely inside your local network. The only missing piece is a reliable way to connect your mobile client or laptop back to your home when your ISP changes your WAN IP address.

A stateless dynamic DNS hostname from XYZ.FRL bridges this gap with zero tracking and zero recurring costs.

Architecture & Security Warning

Never expose raw RTSP port 554 directly to the public internet. Standard RTSP often transmits credentials in cleartext and camera firmware vulnerabilities are frequently targeted by automated botnets.

The recommended architecture is:

  1. Option A (Most Secure): Connect via WireGuard VPN using your dynamic hostname as the VPN endpoint. Once connected to the tunnel, access your NVR dashboard on its local IP (e.g. http://192.168.1.50:5000).
  2. Option B (Direct Web UI): Expose the NVR web interface behind an authenticated reverse proxy (such as Caddy, Traefik, or an identity-aware gateway) with mandatory TLS encryption and strong Multi-Factor Authentication.

Step 1: Keep Your NVR Host Synced

On your NVR host machine (Ubuntu, Debian, or TrueNAS SCALE), set up an automated curl update job to synchronize your assigned XYZ.FRL hostname:

Terminal (Cron)
# Update dynamic DNS every 5 minutes
*/5 * * * * curl -fsS --user 'YOUR_USERNAME:YOUR_PASSWORD' 'https://xyz.frl/nic/update' >/dev/null 2>&1

Step 2: Connect Remote Apps via Dynamic Hostname

In your remote surveillance viewer app (e.g. Home Assistant companion app, IPCams, or VLC Player):

  • Set the server address to: <your-uuid>.xyz.frl
  • Use your reverse proxy's secure HTTPS port (typically 443).
  • Because XYZ.FRL provides a 60-second TTL, any ISP IP rotation recovers automatically without manual app reconfiguration.

Autonomous Vision AI Agents

Running local edge computer vision models with agents that analyze security events? Agents can use the remote MCP server to verify that the upstream external gateway is operational and publish alert notifications with authenticated dynamic links back to event snapshots.

✓ Copied to clipboard!