Platform · CCTV · RTLS · robotics · counter-UAS
See. Know. Act. Protect. Comply.
One live 3D model of your facility: video analytics on the cameras you own, every tagged person and asset located, robots and drones tasked from the same picture, drones overhead tracked, and a person deciding every action. Each part says what it does today and carries its status. Screenshots are real captures on built-in demo data.

U1 · See
See
The CCTV cameras you already own become sensors: video analytics on your own servers, alert rules on what they see, and radar, RF and vessel feeds on the same picture.
What you do with it
- Run detection on the cameras you have, on your own servers
- See one track, not five alarms
- Know what is in the air and on the water
Modules
Camera analytics
RTSP ingest with on-premise object detection models. Classes, never identities: there is no face recognition.
AvailableRadar and air picture
ASTERIX Cat-048 and Cat-021 decoders, Cursor on Target for TAK.
AvailableVessel traffic
AIS from NMEA feeds, placed on the same picture.
Available
U2 · Know
Know
Every tagged person, vehicle and asset on a live 3D model of the site (RTLS): buildings and zones, who and what is where now, and where they were.
What you do with it
- See the whole site in 3D or on the plan
- Follow tracked people, vehicles and equipment
- Scrub back through a shift to see what happened
Modules
3D and plan views
Buildings, zones and assets in one model, in the browser.
AvailableLocation tags
A position API for any tag system, plus UWB and RFID vendor adapters that have run on simulated positions only.
In progressReplay
Replay tracked positions over a chosen time window.
AvailableSOS and evacuation roll call
A tag's SOS opens a man-down alert with a response timer, escalation and suggested responders; a muster counts tags at the assembly points. Run on simulated tags so far: your tag system has to send these events.
In progress3D model of the site
The lit 3D model shown on this site, with an exploded view and a plain clay mode.
Available
U3 · Act
Act
Security robots and drones tasked from the same model, inside authorisations a person approved: plan, rehearse, supervise and stop.
What you do with it
- Plan a patrol and check it is feasible
- Rehearse it on the simulator
- Stop an aircraft from the console
Modules
Mission planning and rehearsal
Feasibility check, schedule and a labelled rehearsal simulator.
AvailableAircraft control
Take off, return, go to, pause and emergency stop through a dock vendor's cloud interface. Tested against a simulated transport; no recorded flight yet.
In progressGround robots
Fleet records for quadruped and tracked robots: readiness, dock state, battery cycles, maintenance due. No live robot telemetry transport yet.
In progressSTANAG 4586 interface
A subset of data link interface messages, as an interoperability spike.
In progress
U4 · Protect
Protect
Drone detection for the facility (counter-UAS), the perimeter and the airspace on one picture, with a person in charge of every engagement.
What you do with it
- Detect a drone and see it cross the fence
- Raise the right alert to the right people
- Keep engagement decisions with authorised people
Modules
Counter-UAS detection and fusion
Detection and track fusion only. SiteOS does not drive effectors.
AvailableAlert rules and incidents
Rules on zones, people, equipment and sensors; incident records.
AvailableEngagement release controls
Two-person release and a rules-of-engagement gate on every engagement.
Available
U5 · Comply
Comply
Evidence of who did what and when, the export-control markings on your data, and the clocks your regulator sets.
What you do with it
- Show an auditor an untampered record
- Keep controlled data with cleared people
- Meet incident-reporting deadlines
Modules
Tamper-evident audit chain
Privileged and administrative actions, SHA-256 hash-chained and verifiable.
AvailableExport-control markings
ITAR, EAR, NOFORN and REL TO caveats enforced when data is read.
AvailableNIS2 and CER reporting clocks
Art. 23 deadlines with the evidence attached.
Planned
Integrations
Interfaces and their evidence
Open, published interfaces rather than a closed plug-in store. Each row says how far it has been tested.
- Simulated
- 7of 15 interfaces
Runs against a software simulator of the device or feed.
- Protocol-tested
- 10of 15 interfaces
Encoder or decoder covered by automated tests against the published message format. Not yet run against the vendor's hardware.
- Hardware-proven
- 0of 15 interfaces
Recorded, dated test against real hardware, with the vendor's consent to say so.
| Sensor or system | Interface | Simulated | Protocol-tested | Hardware-proven | Notes |
|---|---|---|---|---|---|
| Air surveillance radar | ASTERIX Cat-048, Cat-021 | Yes | Yes | No | Decoder tests. Cat-034 is in the SiteOS Defense suite and being merged. |
| Tactical picture (TAK) | Cursor on Target, XML over TCP and UDP | Yes | Yes | No | Send and receive tracks with TAK clients. |
| Drone RF detector | Vendor adapter over MQTT | Yes | Yes | No | Detections become tracks on the picture. |
| Maritime traffic | NMEA 0183 AIS (AIVDM 1, 2, 3, 5, 18, 24) | Yes | Yes | No | Vessel positions and static data. |
| Sensor networks | SAPIENT, JSON form | No | Yes | No | The binary encoding of BSI Flex 335 is planned. |
| UAS ground control | STANAG 4586, DLI messages 1, 20, 21, 101 | No | Yes | No | An interoperability spike. No conformance testing has been done. |
| Video metadata | MISB ST 0601 KLV | No | Yes | No | Decoder tests. Wiring to video ingest is in the SiteOS Defense suite and being merged. |
| Tactical data link messages | Link 16 J-series message parser | Yes | Yes | No | Message parsing only. No terminal or crypto integration. |
| Cameras | RTSP ingest, HLS playback | No | Yes | No | Has run against a live public camera stream. |
| Location tags | UWB and RFID vendor adapters, REST position push | Yes | No | No | Simulated positions. No vendor adapter tests yet. |
| Telemetry bus | MQTT | Yes | Yes | No | Generic topics for sensors and devices. |
| Industrial controllers | OPC UA (read-only), Modbus | Planned | Adapter code exists but the client libraries are not shipped, so nothing connects yet. | ||
| Camera control | ONVIF, not implemented | Planned | No ONVIF client yet. | ||
| Drone telemetry | MAVLink, not implemented | Planned | No MAVLink support yet. | ||
| Drone identification | Remote ID, not implemented | Planned | No Remote ID support yet. | ||
Hardware-proven: none yet. A hardware test bench is specified and not built. Rows move to that column only with a recorded, dated test and the vendor's consent to name it. If you run one of these sensors, a joint test at your site or ours is the fastest way to get there.
Common questions
What buyers ask first
Short answers, with the same statuses as the rest of this page.
Does SiteOS work with the cameras we already have?
Yes. That is where it starts. SiteOS takes RTSP video from the cameras already on your walls, runs object detection on your own servers and places each detection on the 3D model with the camera that saw it. It detects classes, such as a person, a vehicle or a missing hard hat, never identities. There is no face recognition.
Can it run on our own servers, or air-gapped?
On your own servers, yes: the backend and web app run as containers with Docker Compose, in your network and with your keys. An air-gapped install bundle and a no-egress mode are built and still in progress. We have not yet recorded an end-to-end air-gapped install, and will publish one when we do.
Does SiteOS take action on its own?
No. A person decides every action. Robots and drones act on a person's instruction or inside a standing authorisation a person approved, and an engagement needs two authorised people. SiteOS does not drive effectors and has no drone mitigation function.
Can SiteOS detect drones over our site?
It fuses radar (ASTERIX), RF detectors and cameras into one track per object on the model, with alerts to the right team. It detects, tracks and alerts; mitigation stays with the authorities allowed to use it. The interfaces are protocol-tested or simulated today, and none is hardware-proven yet.
Which RTLS location tags does it support?
Any tag system that can send positions to the SiteOS position API. The UWB and RFID vendor adapters have run on simulated positions only, so bring us your tag vendor and we will test it with you.
Which robots and drones can it task?
Drone missions can be planned and rehearsed today. Aircraft control through a dock vendor's cloud interface is tested against a simulated transport, with no recorded flight yet. Ground robots are fleet records for now: readiness, dock state, battery cycles and maintenance, without live telemetry.
Is SiteOS certified?
No. SiteOS holds no security certification and no audit report, and no penetration test has been run. The trust center lists the controls in the code, the gaps we know about and the programmes we have not started.
Who builds SiteOS?
ELEVEN22SPX, a defense technology company. SiteOS is developed by ELEVEN22SPX LTD in Cyprus (EU), and ELEVEN22SPX Inc., trading as ELEVEN22SPX USA, runs United States operations.
Where to next
- Critical facilitiesEnergy terminals, ports, airports, utilities, data centres and logistics: what SiteOS does for each.
- Run it on your serversOn-premises and air-gapped options, and the attestation your accreditor checks offline.
- Trust centerThe controls in the code, the gaps we know about and the certifications we do not hold yet.
See it on your facility
We show the platform on a model of your own site, with the cameras, tags and interfaces you actually run, and tell you plainly which parts are ready.