Connect a real picture.
Then connect your workspace.

Get the compatible bridge

Windows 10/11 x64. Read the publisher and signing information shown with the release. If an executable is unsigned or blocked, ask your administrator to review it. Do not turn off security protections.

1. Add cameras or recorder channels

1. Install and open the Windows Camera Bridge. If it requests the media engine, review the named dependency and licence before installing it.
2. Use local discovery or add a device. For an individual camera, enter its supported local interface and credentials. For a DVR/NVR, select the recorder and its channels, then test each picture.
3. Check the actual device model, firmware and enabled protocols. Own-brand XMEye/iCSee devices and Hikvision, Dahua or Jovision models may expose different interfaces. ONVIF discovery, a generic RTSP pattern or a brand name alone is not proof that a stream or feature works.
4. Confirm a decoded frame. An untested, disconnected, unsupported or P2P/cloud-only device must remain unavailable until an appropriate local protocol or vendor connector works.

Live viewing, PTZ, recording search and playback are separate capabilities. The app shows only the capabilities the bridge confirms for that selected channel. Recorder results are restricted to the channel’s verified source identity.

2. Choose a secure connection

Browser on the same Windows PC: use the bridge’s loopback address, normally http://127.0.0.1:8090. Loopback never sends a pairing token across the network.

Browser on another PC or phone: enable the bridge’s HTTPS LAN listener. Use its displayed HTTPS address and verify its certificate fingerprint with the bridge operator. Follow the supported certificate trust setup; never change a LAN URL to HTTP or disable certificate validation.

The browser may request local-network access. Allow it only for your shop bridge. A camera or NVR’s own internet address is not the bridge address. Do not forward camera ports to the public internet.

3. Pair the correct business and branch

1. Open Cameras & evidence while signed in to the intended business and branch.
2. Choose Show / copy workspace details. In the Windows bridge, select Pair workspace and paste those details.
3. Choose the permitted cameras and whether to allow camera control. Copy the generated workspace token into the web page, enter the bridge address and press Connect cameras.
4. Confirm the channel names and their state. The pairing token stays only in that tab’s memory. Reloading, leaving the page, signing out or switching business/branch requires pairing again. Revoke old grants in the Windows bridge when access is no longer needed.

4. View, review and reconnect

Select a camera channel and press Start live view. Authenticated JPEG frames advance at the bridge’s confirmed preview rate. A stopped or stale stream is not shown as live. Use PTZ only where advertised, and search actual recorder history where the device supports it. Replay sessions cover up to ten minutes at a time and need a first decoded frame before playback appears.

For local snapshots and evidence, the owner unlocks the existing Privacy Vault with its passphrase. Local motion can be matched to completed receipts in the same branch. It does not prove theft or identify a person. Retention is 1–90 days with a 200-entry snapshot cap; event deduplication receipts remain after deletion.

After installation, restarting the bridge, changing channels or correcting a certificate, return to the page and press Recheck connection. If not yet paired, enter the new workspace token and connect. If event history has expired, the page pauses and asks you to acknowledge the gap; it never silently claims a complete timeline.