Osprey Vision
Face & object clustering for CCTV and live drone/recon feeds.
Deployed on infrastructure you own or are authorized to operate — corporate sites, guarded facilities, and authorized aerial survey/recon work.
What it sees
Face clustering and identity verification are deliberately separate: the general pipeline never tries to name a person, and identity verification only ever runs against a set you explicitly loaded — not the open pipeline. Object classification is a different kind of "identification" entirely — it labels a thing's type, not a person's identity.
How it works
One capture path handles both live surveillance cameras and drone downlinks, since both typically speak the same two protocols. From there, every appearance is reduced to a comparable embedding before anything gets grouped.
In the on-prem deployment, all four steps run in containers on your own hardware instead — same pipeline, no tunnel involved.
Two ways to run it
Both run the identical pipeline — the only difference is where it executes. On-prem trades cross-site convenience for guaranteeing footage never leaves your premises.
Common questions
Does Osprey Vision identify people by name?
Not by default. The clustering engine groups appearances of the same face or object under an opaque internal id — no name is ever attached. A separate, optional watchlist verification mode can match against a reference set you supply yourself, for confirming a specific known identity — it does not run against the general clustering pipeline.
Does my camera feed leave my network?
In the cloud offering (the default), yes — your cameras' feeds are captured over an encrypted, authenticated secure tunnel and processed in Osprey Vision's cloud, which is what lets you deploy without standing up any local infrastructure and query every site from one place.
If your requirements call for footage to never leave your premises — data residency, air-gapped environments — an on-prem deployment is also available, where capture, detection, and clustering all run on your own infrastructure instead.
How does the secure tunnel work?
A lightweight agent runs on your network, connects outbound to Osprey Vision's cloud over an encrypted tunnel, and relays your configured RTSP/MJPEG camera and drone streams. No inbound ports need to be opened on your network — the connection is always initiated from your side.
What camera and feed types are supported?
Any RTSP stream or HTTP MJPEG source — the two most common transports across IP cameras, NVR/DVR systems, and drone or aerial recon downlinks. One capture path handles both.
Who is this built for?
Security operations teams and integrators deploying on cameras and airspace they own or are contractually authorized to operate — corporate sites, guarded facilities, and authorized aerial survey/recon work.
It is not a public search service, and is not intended for surveillance of individuals without a lawful basis and appropriate notice.
How accurate is the clustering?
Face clustering uses ArcFace-family embeddings with a conservative single-face quality gate on every reference sample, exact — not approximate — cosine matching, and a similarity threshold you calibrate against your own deployment's data rather than a fixed global number.
Deploy Osprey Vision
Cloud or on-prem, per-camera pricing. Tell us about your sites and camera count.