Your cameras record everything. Notice what matters.

OpenPatrol helps a security team bring existing cameras, alarms and sensors onto one screen, review possible incidents sooner and coordinate what happens next.

Keep the equipment you already haveConnect common camera feeds, alarms, access systems and sensors.
Bring important events to the operatorSurface possible falls, break-ins, fights, distress and unusual movement for human review.
Respond from the same placeVerify evidence, raise alerts, speak through connected devices and keep an audit trail.

See how it works Run the demo

Open source · Rev-AA working digital prototype for teams to inspect, test and improve

OpenPatrol Rover One, TriScout, four-rotor AirScout and Sentinel Rev-A product family

REV-A VISUALISATIONDIGITAL PROTOTYPE

Built for real sites with mixed equipment.WarehousesCampusesIndustrial facilitiesGated communities

Security equipment should work as one system

Most sites do not lack cameras. They lack one dependable way to connect what those cameras and sensors see with the people who must decide what to do.

See the whole site

Bring live cameras, alarms, door events and fixed sensors into one operator view—even when they come from different systems.

Know where to look

Turn activity from several sources into a possible incident with the relevant time, place and evidence attached.

Act without changing screens

Alert the team, trigger a light or siren, play a warning, use talkback and record who took each action.

Reach beyond fixed cameras

Add a patrol robot or supervised drone when a site needs a closer view—without making them compulsory.

For implementers: RTSP and ONVIF-compatible camera paths, Frigate, MQTT, NDJSON, generic event contracts, ROS 2 and Gazebo are documented in the repository.

From “something moved” to “here is what needs attention”

The command centre gives an operator the site view, supporting evidence and response controls together. These demo screens use the warehouse scenario included with the project.

See the operator guide →

OpenPatrol command centre showing cameras, devices and site status — See cameras, devices and site status together

OpenPatrol screen for reviewing evidence attached to a possible incident — Check the evidence before responding

OpenPatrol controls for announcements and operator talkback — Warn, speak and record the response

Where OpenPatrol fits

It is not a cheaper clone of a field-proven robot. It is an open integration and engineering starting point for teams that want to own the stack.

Published capability	OpenPatrol	Frigate	Knightscope K5	Asylon platform
Primary role	Multi-system coordination	Local AI NVR	Managed security robot	Managed ground + aerial security
Open source / inspectable build files	Yes	Software	No	No
Local-first camera analytics path	Yes, via adapters	Yes	Vendor platform	Vendor platform
Camera, alarm, access and sensor fusion	Included contracts	Camera-centric	Vendor integrations	Vendor integrations
Ground robot + drone in one workflow	Reference designs	No	Ground portfolio	Yes
Editable robot CAD, BOM and firmware	Included	Not applicable	No	No
Physical field validation	Not yet	Software deployments	Commercially deployed	Commercially deployed

Comparison reflects public product documentation checked 3 August 2026. Sources: Frigate, Knightscope, Asylon DroneDog and Guardian. “Included” describes repository scope, not field performance.

Engineering you can inspect

Product visualisations communicate the family; controlled dimensions trace to locked Rev-A schedules and editable OpenSCAD sources.

Browse hardware packs →

Sentinel Rev-A mast dimensional envelope — **Sentinel Rev-A**460 × 400 mm base · 980–1,500 mm sensor head

AirScout Rev-A dimensional envelope — **AirScout Rev-A**380 mm motor diagonal · 9-inch propeller envelope

One simple path from event to response

Something happensA camera, alarm, door, sensor or patrol device sees activity

→

Bring it togetherOpenPatrol attaches the place, time and available evidence

→

Ask for attentionThe system presents a possible incident instead of making the final call

→

A person respondsVerify · alert · speak · dispatch · preserve the record

One workflow, across the site

Rover One, Sentinel and the four-rotor AirScout extend the same operator-controlled incident workflow beyond fixed cameras.

OpenPatrol Rover One, Sentinel and four-rotor AirScout operating in a warehouse — Rev-A product visualisation · physical performance remains unvalidated

Prototype hardware cost

Indicative component BOM—not a retail price or fabrication quote. USD equivalents use ₹95.13 per US$ on 3 August 2026.

Rover One4-wheel ground patrol≈ $388 ₹36,891

TriScoutLow-cost smooth-floor rover≈ $342 ₹32,499

AirScoutSupervised aerial inspection≈ $473 ₹44,980

SentinelElevated sensing + telepresence≈ $703 ₹66,890

Sensor Hub8 zones + AV alert outputs≈ $91 ₹8,700

Excludes labour, tax, shipping, tooling, integration, validation, certification and third-party equipment. Exchange-rate reference: Reuters, 3 August 2026.

From files to a physical prototype

Start by quoting the metal, polymer and composite parts. Then use a local mechatronics integrator for assembly, wiring, calibration and acceptance testing.

Send suppliers the controlled files—not the marketing images.The current repository offers preliminary OpenSCAD geometry and schedules. A fabricator may still require STEP/DXF conversion, tolerance callouts and assembly drawings before quoting. None of these firms is endorsed by or affiliated with OpenPatrol.

Run it in two commands

Python 3.11+. The lightweight command-centre demo has no third-party runtime dependency.

Full setup and integrations →

# install from GitHub
pipx install git+https://github.com/eyeinthesky6/openpatrol.git

# launch the bundled scenario
openpatrol

# open http://127.0.0.1:8765

Why OpenPatrol exists

Security teams are often asked to watch too many feeds across too many separate systems. Useful equipment becomes another island: the camera records, the door system logs and the alarm sounds, but the operator must piece the story together.

OpenPatrol explores a vendor-neutral alternative that can sit above existing equipment, remain inspectable and grow from fixed cameras to mobile patrol devices only where they add value. People remain responsible for consequential decisions, and certified life-safety systems remain independent.

Complete digitally. Honest physically.

Software, simulation, firmware interfaces, parametric CAD, BOMs, wiring guidance and Rev-A specifications are complete enough for a digital prototype release. Fabrication, real-camera calibration, endurance testing and certification remain a future physical-validation phase.

Safety boundary

OpenPatrol creates incident candidates; it does not guarantee detection. Certified fire, pool, medical and access systems remain independently operational.