Standalone sites
Each Argus site runs on its own. Detection, rules, alerts, clips, captions, Copilot and the dashboard all run on your site's hardware. None of it needs a connection to VoisX or to the internet.
One site, one database
Each site has its own site database, its own clip storage and its own accounts. Inside a site you can group cameras into organizations in the dashboard, but every account sees the whole site.
To run Argus at several locations, install a site at each location. Each site has its own dashboard and its own accounts.
The status link
The release includes an optional service, site-cloud-sync, that reports a site's status to a central control plane. It runs on every site, but stays idle until you give it a site key. Without one, the rest of the site works fully offline.
When it is on, the service:
- Checks the licence once when it starts.
- Every 5 minutes, sends a host name, the number of turned-on cameras and the Argus software version, and reads the site's configuration. The host name is the
site-cloud-synccontainer's own host name.
It never sends video, clips, captions, events or Copilot conversations.
If it can't reach the control plane, it logs a warning and sends the next report at the next interval. The rest of the site keeps working.
Turn on the status link
Turn it on only when VoisX gives you a control plane address and a site key for your site.
-
Add both values to
.env:.envCONTROL_PLANE_URL=<address from VoisX>
SITE_API_KEY=<site key from VoisX> -
Apply it and check the log:
docker compose up -d site-cloud-sync
docker compose logs -f site-cloud-syncIt sends its first report right after it starts, and the log shows
heartbeat ok.
Keep the site key secret. Anyone who has it can report status as your site. If you lose it, ask us for a new one.
To turn the link off again, set ENABLE_CLOUD_SYNC=false in .env and run docker compose up -d site-cloud-sync. The service then stays idle. If you set ENABLE_CLOUD_SYNC=true without a valid site key, the service refuses to start.