On-site hardware

CriticalVue Bridge

A small box at the site that watches your recorders from inside the network. No port forwarding, no public IP, no VPN: it only ever connects out.

The CriticalVue Bridge: a small, fanless box with the CriticalVue Bridge logo on its front

Port forwards are the weak spot

Monitoring a recorder from the cloud has meant opening the customer's network to the internet, and each opening breaks quietly: a new router, a changed public IP or a new internet provider, and the site goes red.

Many IT departments won't open those ports at all, and some sites end up needing a VPN tunnel just to be monitored.

Port forwarding: the site's router has ports opened to the internet, a public IP address to keep, and a DDNS name or VPN that can break. With the Bridge: nothing is opened on the site's router. The CriticalVue Bridge sits beside the recorders and connects out to CriticalVue.
How It Works

A Bridge watches from inside and connects out

Plug the Bridge in on the recorders' network and add it to your account with the code on its label. It looks for the recorders on its network (Dahua, Hikvision, Uniview, TVT and Avigilon) and lists what it finds, so adding one means picking it and entering its login. An Axxon server, or anything the search misses, is added by its address on the site's network.

The CriticalVue Bridge on a shelf in a network rack, beside the site's switches
How the CriticalVue Bridge connects: on the site's network it reads the recorders and cameras, then sends their status out through the site's firewall to CriticalVue over HTTPS port 443, outbound only, and on to your dashboard. Nothing comes in through the firewall.
Nothing comes in: the site's firewall needs no inbound rules, and the recorders never face the internet. Everything else works as it does today, from real-time status and snapshots to alerts and daily reports, and a site can mix recorders on a Bridge with recorders connected directly.

Two networks, kept apart

A Bridge with two network ports can watch recorders on two separate networks at once, one cable each, without joining them.

Two ports, kept apart: one CriticalVue Bridge, port 1 cabled to network A and its recorders, port 2 cabled to network B and its recorders, with no connection between network A and network B.

Keeps working offline

Keeps working offline: a timeline where the site's internet drops, the CriticalVue Bridge keeps checking the recorders and saves what it sees, and once the internet is back it sends everything with the real times.
If the internet drops, the Bridge keeps checking the recorders and sends what it saw once it's back, with the real times.
Why It Matters

Key Benefits

Nothing Inbound

No port forwards, no public IP, no VPN. The Bridge only connects out: to CriticalVue over HTTPS, plus DNS and its own updates.

Finds Your Recorders

It searches its own network the way the recorder makers' tools do and lists what it found, ready to add.

Sealed Passwords

Recorder passwords reach the Bridge sealed, so only that Bridge can open them. It never sends video streams or recordings.

Two Networks, Kept Apart

A Bridge with two ports can watch recorders on two separate networks at once without joining them.

Keeps Itself Up to Date

Signed software updates install by themselves, and an update that doesn't work is undone automatically.

A One-Page Sheet for IT

Exactly what the Bridge connects to and why, on one printable page for the site's IT team.

Monitor sites without opening their networks

The Bridge is bought once, in the CriticalVue store, by your organization's billing manager. It ships unclaimed, with its claim code on the label. Monitoring stays on your plan, and sites without a Bridge keep connecting directly.