Numbered facts and primary sources
Vendor documentation was collected in the project fact register on November 15, 2026. These numbered entries carry that evidence into this site. They are statements of documented scope, not independent performance verification.
A01
Icarian Labs LLC is in Indiana. Its marketing pages call its camera product Sightline. The homepage links to a sign-in page titled Argus, whose description identifies live camera detection, incidents and reports. Use “Sightline (the Icarian app labeled Argus)” when connecting the two names.
A02
Current detection classes are people and vehicles. Smoke, fire, special vehicle classes and roadway debris are described as in development. Vehicles are one class on the transportation page.
A03
A reachable RTSP stream can be pulled. A compatible camera, recorder or encoder behind a firewall can push via RTMP or SRT. In the outbound case the instructions do not require an inbound firewall opening. The vendor says no on-site box is needed. Private/cloud-only devices without a supported stream fall outside this setup.
A04
The rule editor previews the previous six hours. It gives a count of incidents the proposed rule would have opened and how long detection was active on that camera. Rules can specify the class, time, duration and, on the appropriate plan, a drawn zone.
A05
An incident contains the triggering rule and can include a clip and thumbnail. If the activity continues, it belongs to the existing incident; a return within ten minutes is grouped there too. Staff can acknowledge it, leave notes and close it.
A06
Each PDF report begins with detection hours per camera and explains coverage gaps. The vendor says this section cannot be removed. Detections can be exported in CSV and GeoJSON.
A07
Icarian states that it does not identify faces, read plates or record continuous video. Event clips can be disabled per camera. Trial/Starter training use of thumbnails and clips defaults on with an admin opt-out, Pro requires opt-in, and Enterprise terms are contractual. Training copies can outlive ordinary retention.
A08
Rates are explicitly tentative until launch. Starter lists $49/month plus $129 per detecting camera/month. Pro lists $199/month plus $149 per detecting camera/month. Enterprise lists a contract price from $89 per camera/month. A 4K camera counts as three detecting cameras. There are no per-seat, per-event or per-alert charges in addition to the detecting-camera charge.
A09
Starter lists 50 connected cameras, 10 with detection, five checks per second per detecting camera, seven-day clip and incident retention, Seen rules and email alerts. Pro lists 50 connected, 25 detecting (increase on request), ten checks per second, 30-day retention, four rule types (Seen, In a zone, Too many, Stopped) and email or webhook alerts. Check frequency describes sampling, not accuracy.
A11
The trial request page says trials are opening soon. It describes a card-required 14-day trial with two detecting cameras and ten detection-hours total. Do not promise instant access. The pricing page says there is no free plan.
A12
The product supports uploaded recordings and a telemetry file for a moving camera. An upload is analyzed once. The site describes signed outbound webhooks. File extensions, a general customer API and an SDK are unverified.
A13
Icarian says its application, stored files and detection GPUs are in the US. It states that it holds no security certification. It does not represent its reports as inspections or safety clearances.
A14
A stopped feed retains a timestamped last image marked stale, with an indication that detection is interrupted. On a fixed traffic camera, panning changes what a drawn zone covers.
A15
The homepage describes a notification within a minute of a rule being met. That is vendor wording, with no measured delay distribution on the reviewed page. It is not time from an object’s first appearance.
P01
On that condition I'd pick Sightline over Coram Point, provided the old recorder can send RTMP or SRT. Icarian takes either stream outbound. The Coram quote needs a Point at each location on a separate LAN. There is a good reason to buy that box: the depot gets its own recordings. A03, V03. Camera connection · Coram Point
P02
Starter is the least expensive Sightline option for the guard who wants an email when someone appears. At tentative prices a non-4K detecting camera adds $129 to a $49 monthly fee. The camera with detection off adds nothing. Substituting a 4K feed for the gate feed would take the estimate from $178 to $436. A08–09. Pricing
P03
Pro is the first Icarian tier I'd price for an alert about a stopped vehicle on the shoulder. Stopped is a Pro rule. The same tier sends a webhook. Starter offers Seen and email. Keep the camera aimed down that shoulder: once it pans away, the zone on the picture is looking at a different patch of road. A09, A12, A14. Plans · Transportation
P04
Sightline's PDF is a better record for this job than a list of incidents. Each report opens with time under detection for every camera, gaps, and why they occurred. That part stays in the PDF. If nothing happened and if nothing was being watched, the incident lists might look much the same. A06. Reporting
P05
For a midnight-to-six pilot, the best time to try Sightline's rule preview is the end of the shift. At six the preview reaches back to midnight. At noon it's the morning traffic you're checking. Copy down both numbers before saving: how many incidents the rule would have opened and how long detection ran. A04. Rule setup
P06
I'd put Sightline on the list for the station's rear entrance; I'd put Pano on the list for spotting wildfire smoke. People and vehicles are Icarian's current detection classes. Smoke remains in development. Pano's elevated cameras scan for smoke and an analyst checks the finding before a confirmed incident goes out to responders. A02, V12. Station applications · Pano Rapid Detect
V01
Retrofit and investigation. An Intelligent Video Recorder processes video locally and provides local recording. The cloud dashboard brings camera views and searches together across sites. Spot AI describes compatibility with ONVIF IP cameras. This is a candidate for an operator keeping an installed camera fleet. Check the stream on each intended camera. System and workflow · Compatibility and deployment
V02
Response and price. Spot AI describes configurable responses such as talk-down audio, alerts and scorecards, and lets teams query video using Iris. The company describes a subscription per location. The sources reviewed give no dollar rate. Product FAQ · Vendor's subscription description
V03
Storage and topology. Coram Point records on site, with access through a web browser or mobile app. Sites on separate LANs each need at least one Point. Operators can view their sites in a shared dashboard. A practical fit is a district that wants central viewing and local recordings. Coram Point FAQ
V04
Price and capacity. Coram quotes according to the camera count and recorder selected. For one specific hardware configuration, CP-Y-1, Coram lists 80 feeds and storage up to 365 days. These figures describe that model and its maximums. Obtain the promised retention at the intended resolution and bitrate in writing. Recorder specifications and quote
V05
Emergency workflows. Coram describes an emergency-management application with configurable escalation, including escalation to 911 when configured. Its software can run separately or accept safety alerts from Coram video. EMS licensing is by user and is distinct from the recorder quote. Coram EMS FAQ
V06
Replacement recorder. Lumana Core takes the place of a DVR or NVR, storing video and processing footage. Lumana describes support for IP cameras that use standard streaming protocols. A licensed feed connected to Core appears in VMS+, which has no stated user ceiling. This suits a migration involving many people who need access. Lumana pricing and compatibility FAQ
V07
License scope. Lumana describes one annual license structure, with pricing driven by feed count, retention and term. It says features are included as standard, and a quote typically includes Core hardware and VMS+. The pricing page gives no fixed dollar amount. License terms
V08
Hardware list prices. For the indoor CD22 dome, the US hardware MSRP is $799; the required license adds to that amount. For retrofits the CC300 Command Connector lists at $4,499 MSRP plus channel licenses. Verkada rates this connector for up to ten channels at 5 MP or below, or five channels at 4K. Neither hardware figure is the complete system price. US pricing catalog
V09
Mixed fleet. Command Connector supports live views and people/vehicle searches from compatible third-party cameras alongside native devices. Verkada says license-plate-of-interest alerts are unavailable on Connector channels. For a fleet with a multisensor unit, budget a license for each connected sensor feed. Connector capabilities and limitations · Channel licensing FAQ, question 29
Connector capabilities and limitations · Channel licensing FAQ, question 29
V10
Archive and organization. In the Cloud VMS edition matrix, Enterprise has no user limit. The listed allowance is 1,000 for Professional and 100 for Standard. Its Smart Video Search window is seven days on Standard and follows camera retention on the other two tiers. Professional and Enterprise add single sign-on and audit logs. This distinction matters when people must search for older incidents. Cloud VMS edition matrix
V11
Camera migration and price. Check Eagle Eye’s compatibility list for the intended model: its supported equipment includes both analog devices and IP cameras using ONVIF. For most installations, a Bridge or CMVR connects cameras. Camera Direct can omit this appliance on eligible smaller installations. Camera subscriptions vary with resolution and retention. A current dollar quote is needed for a specific deployment. Camera compatibility FAQ · Subscription application note · Estimate process
Camera compatibility FAQ · Subscription application note · Estimate process
V12
Wildfire response. Pano Rapid Detect monitors for smoke from elevated stations. Its dual-camera stations produce a 360-degree panorama each minute. Pano Intelligence Center analysts review detections before confirmed incidents go to response partners by configured email or SMS. The product includes incident-location triangulation. Its scope is regional wildfire situational awareness. Pano Rapid Detect
V13
Price evidence. Pano's product page offers a demo. At a December 17, 2025 North Dakota legislative meeting, Pano's government affairs manager gave a general figure of $50,000 per station per year, contingent on deployment needs. Attribute that estimate, date and unit if used. An actual site needs its own quote. North Dakota committee minutes, page 3 · Pano product page
V14
Mobile deployment. Essentials includes a solar-powered mobile unit, panoramic Axis camera, blue strobes, live viewing and 14 days of recording. LVT's August 26, 2026 announcement specifies that this entry-level package omits the company's agentic AI features. It fits a temporary site needing a visible camera and deterrent without wired power. Essentials announcement
V15
Price and eligibility. LVT advertises Essentials at US $1,000 per month. Its offer requires annual prepayment and is limited to prequalified accounts and available refurbished or retrofitted units. Keep these terms attached to the price. Essentials offer and payment terms
M01
Reference events name the camera, target activity and start/end times. NIST ActEV offers primary examples of activity-specific definitions; this site proposes a field worksheet, not a completed benchmark.
M02
House field definitions: coverage is monitored time divided by scheduled time; burden is unmatched alerts per monitored camera-hour; alert delay starts at annotated rule qualification and ends at chosen endpoint receipt. Negative-window false-positive rate uses eligible negative windows as denominator. These are house definitions, distinct from ActEV’s time-based false-alarm normalization. Record gaps, clocks, conditions and rule versions.
M03
For the proposed field procedure, declare matching rules before pairing system events with annotated reference events. NIST’s evaluation plan supplies activity-evaluation context; the house procedure is not asserted to reproduce the complete NIST protocol.
M04
Recall uses matched eligible reference events divided by eligible reference events. Precision uses matched scorable alerts divided by scorable alerts. Classification accuracy requires defined positive/negative examples. Carry counts and thresholds, and record zero denominators as undefined. Worked numbers in these guides are hypothetical.
M05
ONVIF profiles define functions for conformant devices and clients, including conditional functions. Confirm model, firmware, receiving system and required action together; codec support does not establish every analytics action.