The latest release of each part of Guardian, and how to install it. Guardian watches a site's existing cameras
for the things that cause incidents, on the site's own hardware, and proves itself in shadow mode on your
footage before it is allowed to alarm.
Guardian runs on the site's own hardware and watches its existing cameras. Nothing
new on the poles, and footage stays on site unless your policy says otherwise.
CAM 01 · Gate
CAM 02 · Conveyor
CAM 03 · Car park
CAM 04 · Stockpile
CAM 05 · Workshop
CAM 06 · Loading
Latest releases
A site runs one Operations node, and may add Recognition and
Sage nodes. Each is released on its own. Every release is signed by Alphalogix, and a node
checks that signature before it installs anything, so a download that has been tampered with, or built by
somebody else, is refused. You can also check the file you downloaded against the
SHA-256 on its card.
Loading the latest releases…
How an upgrade flows
DownloadThe release for the node, here, on any computer.
CheckIts SHA-256 matches the card, if you want to be sure.
Add it to GuardianSettings → Software. Guardian checks it is genuine.
Every node upgradesOne at a time, each showing its progress. Any can go back.
Upgrading a node you already have
Operations node
Download the latest Guardian Operations release above. Any computer that can reach this
page will do; the node itself does not need the internet.
Sign in to Guardian as a site administrator and open Settings → Software.
Drop the file on Add a new version. Guardian checks it is genuine, shows what will
change, and asks you to confirm.
Watch it install, step by step. Alerting and playback pause for a few minutes; your own VMS keeps
recording throughout.
Recognition and Sage nodes
Download the release for that node above.
Add it on the Operations node's Settings → Software, the same way.
It is kept there for the nodes it is for.
On that node's card, press Upgrade. It fetches the release from the Operations node
over the site network, checks the signature itself, and installs. With several nodes,
Upgrade all does one at a time.
Each card shows its progress, and its new version when it is done.
Something wrong after an upgrade? Every node can go back to the version it ran before, from its card on the
Software screen.
Adding a new node
A new node is installed by your Guardian installer, who prepares the hardware, encrypts its disks and installs
the release. What your site provides, and what happens after:
Operations node
A server with an NVIDIA GPU, in a rack or cabinet with power and cooling.
A connection to the camera network, and one to the site's management network.
The cameras' addresses, and a read-only account on them or on your VMS.
Afterwards: a site administrator account, and your licence installed under
Settings → Licence.
A server with an NVIDIA GPU, on the same management network as the Operations node.
Afterwards: on the Operations node, Settings → Site → Nodes → Add a node finds it on
that network. Confirm it, and it joins the site.
Your licence must include recognition, and name the node.
Sage node
A server with a dedicated NVIDIA GPU for Review, on the same management network.
Afterwards: added from the Operations node's Nodes screen, the same way.
Your licence must include Sage, and name the node.
Check a download
Optional, and a good habit: before copying a release to site, check it is the file Alphalogix published. Run
this where you downloaded it, and compare the result with the SHA-256 on the release's card
above. If they differ, do not use the file; download it again. The node checks Alphalogix's signature itself
either way.
Use the name of the file you downloaded, with its version in place of <version>.
Support
If an install or upgrade does not go as it should, raise a ticket or call us. Guardian's own error screens
include a Copy details button: paste those details into your ticket so we can help straight
away.