Nobody is watching at 3am
The screens are on. The chair is empty. The recording is there for afterwards, which is not the same as noticing.
For security teams
Cameras that raise the job themselves, without the footage leaving
The camera services run on a machine inside your building, next to the cameras. You write the rules — what to watch for, when it counts, what happens next — and when one fires it opens a real service request against the right building. The footage stays where it was recorded.
- footage leaving the premises
- 0footage leaving the premises
- on-site machine per client
- 1on-site machine per client
- watching, including offline
- 24/7watching, including offline
- request raised per rule that fires
- 1request raised per rule that fires
Today
Why most camera systems end up as evidence, not prevention
A camera that only records is a camera you look at after something has already happened.
A detection goes nowhere
Something is flagged. It appears on a screen. No job is created, so nothing is assigned to anybody.
Footage has to leave the building to be useful
Cloud analysis means your residents' recordings are sitting somewhere you do not control, which is a conversation nobody wants to have.
The internet goes down and so does the system
The one night the link fails is the night you needed it.
Watching
Every camera on the local network, in one live view
Cameras are set up once and then watched from a single screen. Detection rules are set per camera with a confidence threshold you control, so a busy lobby and a quiet fire escape are not held to the same trigger.
- Live view of every camera on the local network
- Camera setup and configuration in the same place
- Detection rules per camera, with a confidence threshold
- An anomaly feed — what was detected, where, and when
- Sign-in restricted to super admins
app.360safeops.com/security
Rules
You decide what counts, and what happens next
A rule is three parts: what to watch for, the conditions under which it matters, and the action. The action can notify a person or a role — or open a real service request, assigned and tracked like any other job.
- Pick what to watch for, when it counts, and what follows
- Conditions on time of day, building or confidence
- Action: notify a named person or a whole role
- Action: raise a service request automatically
- Run history for every automation, step by step
app.360safeops.com/security/automations
On the premises
Built for a building, not for a data centre
Everything runs on a machine you can point at. If the link to the outside drops, detection carries on and the events queue until they can be sent — nothing is lost because the internet had a bad night.
- Footage never leaves the building
- Keeps working offline — events queue and send later
- Incidents land against the right building automatically
- One setup per client, across several premises
- Only the events you asked for ever travel to the portal
app.360safeops.com/security/anomalies
Step by step
From a camera noticing to somebody being sent
The point of the whole thing is the last step: a person with a job, not a clip in an archive.
- 01
The camera notices
A detection fires on the local machine, against a rule you wrote for that camera.
On the premises
- 02
The conditions are checked
Time of day, building, confidence threshold. If it does not meet the bar you set, nothing happens.
Your thresholds
- 03
A request is opened
Not an alert on a screen — a real service request, against the right building, with a reference number.
A real job
- 04
Somebody is assigned
It routes to security staff covering that building, gets timed like any other job, and closes with a record.
Tracked to close
Questions
What security teams ask first
If yours is not here, the FAQ page goes further — or just ask us directly.
Does any video leave our building?
No. The analysis runs on a machine inside your premises. What travels to the portal is the event — what was detected, where and when — and only for the rules you asked to be notified about.
What happens when the internet drops?
Detection carries on locally. Events queue on the on-site machine and are sent once the link is back, so an outage delays the notification rather than losing it.
Can we use our existing cameras?
The system watches cameras on the local network, so it depends on what you have — that is a question for the setup call rather than one we can answer honestly in the abstract.
Who can log in to the camera side?
Sign-in is restricted to super admins. The incidents it raises appear in the normal queue for the staff assigned to that building, without giving them access to the cameras themselves.
The same product, from another side
Start here
Talk to us about the on-site setup
Bring one building, its list of units and the services you already offer. We'll set the price list up with you, then you can watch a real request go all the way from a resident's tap to the invoice.
No card needed · Your data stays yours