Exports
Alerts
New rule
Recent
AI backend
Two roles, configured separately. Compiling a rule happens once and only ever sees the sentence you typed. Adjudicating happens per event and sees a cropped image from your camera — so a site that cannot let footage leave can run that one locally while still compiling in the cloud.
These settings are managed by your provider. You can see which model is in use and what it is costing, but only they can change the backend or the spend cap.
Spend cap
At the cap, degrade pauses only the rules that need a model. Rules built from zones, timing and size keep alerting — an alerting system that goes silent is worse than one that gets simpler, because silence looks the same as nothing happening.
Usage
| Day | Backend | Calls | In | Out | Cost | Errors |
|---|
Team
Who can sign in, and what they may do. Viewer watches. Operator also exports and fetches from cameras. Admin changes cameras and rules. Owner additionally manages people.
Add someone
| Name | Role | Last signed in |
|---|
Sites
Each site needs its own bridge. Adding one gives you a token to put in it.
Customers
Creating a customer makes a tenant, its first site, and the bridge token for it. You manage their AI backend and spend cap; they cannot raise it.
| Customer | Cameras | Storage | AI spend |
|---|
Fleet & storage
Recording health, measured bitrate and storage caps. Click a value to change it.
Bridges
Find cameras on the network
| Camera | Device | Address | State | Measured | 30-day | Used | Cap (GB) | When full | Keep | Mode | Detect | SD card |
|---|