Enterprise
Supervision for larger organisations
Supervision installs as one file per server, keeps every recording on hardware you control, and our team helps you roll it out across sites. This page covers how it is run across sites, how people sign in, and what we provide alongside the software.
Deployment options
All three options use the same software, an on-premise VMS that runs on your own servers. They differ in where the servers sit and whether anything leaves the building.
A single server on site
One server records every camera, checks each one every 10 seconds and runs AI search. The desktop app connects over the local network, encrypted with a certificate it pins on first use. Upgrading is replacing one file; a backup is a copied folder.
A server at each site
Each site keeps its own server and its own footage, so a slow link between buildings never affects recording. Operators open one desktop app and move between sites from it. Nothing is pooled in a central cloud.
Air-gapped, with no internet access
Where the network has no route out, Supervision still runs: discovery, recording, live view, playback and AI search all happen on the server in the room. Updates are brought in by hand, as a file, and applied by replacing the binary.
Running several sites
Each site runs its own Supervision server and records to its own disks. The link between buildings carries only what an operator asks to see, so a slow or broken connection between sites never interrupts recording at either end. Operators open one desktop app and move between sites from it.
Health is checked per site, every 10 seconds, with the reason when a camera drops. Roles and the audit log are kept per server, so a site manager can be an administrator of their own building and a viewer of another, and an export from any site is recorded where it happened.
To add a site, you install the server there, connect it to the cameras, and add its address to the app. There is no central database to size for the whole estate.
Sign-in and roles
Accounts carry a role, from owner down to viewer, and an audit log records camera changes, exports and user changes. For organisations that manage people centrally, sign-in can be handed to your directory: SAML 2.0, LDAP or Microsoft Entra ID, with directory groups mapped to Supervision roles so a leaver loses access when their account is disabled.
If an owner is ever locked out, someone with administrator access to the server machine runs a recovery command on it. We can't do this remotely.
| Role | What it can do |
|---|---|
| Owner | Everything, including server settings and other owners. Created at setup; recoverable from the host. |
| Admin | Add and change cameras, manage users, export footage, open and close incidents. |
| Manager | Watch live and recorded video, search, open and work incidents, export clips. |
| Viewer | Watch live and recorded video on the layouts they are given. No exports, no changes. |
Air-gapped sites
A Supervision server never needs an outbound connection. Discovery, recording, live view, playback and AI search all run on the machine in the room, including the model behind search. The desktop app talks to the server over the local network on port 8443, and to nothing else.
Updating an air-gapped server means carrying in the new release as a file, replacing the one binary, and restarting the service. If the new version fails to start, the previous one is put back. The desktop app's own updater is switched off on these installs.
| Default port | Used for |
|---|---|
| 8443 | HTTPS API and desktop app |
| 8554 | RTSP |
| 8888 | HLS |
| 8889 | WebRTC |
Pilots and support
Most customers start with a pilot on their own hardware with a handful of cameras. We help set up the server, add the cameras and NVRs, and agree with you in the first week what the pilot needs to show.
- A call. Thirty minutes on your cameras, recorders and network, and what you need to find in the footage.
- A pilot. Eight to sixteen cameras on a server you run, for as long as you need to trust it.
- Sizing. Disk, server and network figures for the full estate, in writing.
- Rollout. Site by site, with onboarding for each team that will use it.
After that, support hours, response times and onboarding for new sites are agreed per contract. We don't publish fixed support tiers. Tell us what you need and we'll put it in writing.
Procurement questions
- Where does footage live?
- On your servers, and only there. Nothing is sent to Bipolar Factory; we have no access to your cameras or recordings.
- Is there a cloud dependency?
- No. Recording, live view, playback and AI search run on your server. The desktop app checks for updates over the internet when it has one; an air-gapped deployment works without it.
- How is it licensed?
- Quoted per deployment, based on sites and cameras. There is no public price list. Ask us for a figure to take to procurement.
- Which platforms?
- A desktop app for macOS and Windows, with Linux in beta. The server is bundled with the app, and runs as a background service on the machine you choose. Mobile apps are coming.
- What about the cameras and NVRs we already have?
- Any camera or recorder that speaks ONVIF or RTSP. An NVR brings in every channel at once, with main and substream detected. Nothing needs replacing.
- How do we evaluate it?
- Fill in the form on the contact page and we email you the download links straight away. If you'd like a pilot on your own hardware with a handful of your cameras, reply to that email and we'll arrange it with you.
- Is Supervision STQC certified?
- No. STQC testing under MeitY's Essential Requirements applies to CCTV devices, not to the software that manages them, so no video management software is STQC certified. Supervision works with cameras that have been through that testing, from CP Plus, Sparsh, Matrix Comsec and Honeywell, and with Axis, Hanwha Vision, Bosch, Vivotek and i-PRO over ONVIF and RTSP. Certification is per model; check the STQC IoTSCS portal for the model you are buying. On request we provide a written mapping of the ER's control areas to Supervision's own security design, the list of supported OEMs, and the relevant sections of the operating manual. For a specific camera model, ask the OEM for its STQC test report and CRO registration number.