# Flock Condor Video and Wing Gateways Flock markets Condor as an AI-assisted video-camera family and Wing as a gateway for bringing video streams into its software. Jacksonville and Russellville records establish Arkansas agency purchases; the connected-stream inventory and activation state remain production-specific questions. ## Vendor self-description Flock's current video page describes Condor variants, visual alerts, vehicle and people searching, and a “non-biometric” people-search design that the vendor says does not use facial recognition. Those are current vendor representations, not independent accuracy or configuration findings (vendor primary/self-description, [Flock video-camera page](../../web%20archive/2026-07-20/flocksafety.com/video-cameras.md)). The May 26, 2026 catalog lists multiple Wing gateway configurations. One named configuration provides eight streams, 8 TB of storage, eight AI channels, and 30 days of storage; other catalog configurations and capacities differ. These are dated SKU specifications and do not establish what a particular customer installed (official procurement attachment / vendor catalog, [Flock price list, May 26, 2026](../../web%20archive/2026-07-20/omniapartners.com/r250203-flock-pricing-2026-05-26.md)). ## Jacksonville deployment Jacksonville's first production is the corpus's first Tier-1 Arkansas evidence of a Wing order and populated Wing networks. The customer-signed order lists one 128-stream Wing gateway, FlockOS Advanced, 30-day retention, a $14,500 first-year total, and a $14,000 annual recurring subtotal. Its product description says FlockOS Advanced integrates third-party live video cameras into Flock's VMS and map; the produced Flock signature fields are blank ([[Jacksonville Flock Wing Order and Motorola-Vigilant Acknowledgements]], `PO- Flock Safety - Documents (003).pdf`, pp. 2-3, 5). Jacksonville's tenant location export contains 101 rows typed `Video Integration`, divided between `Jacksonville AR PD (Wing)` and `Jacksonville AR PD - (PD Wing)`, plus two rows typed `Video Camera`. Those records carry exact coordinates but do not identify the underlying make or ownership of each third-party camera or establish current stream health ([[Jacksonville Flock and Wing Camera Location Export]], pp. 1-3). The supplemental device-health CSV exactly reproduces those 126 tenant rows. Its `Health Status` field labels the 101 integrations `Video Integration`, which is not a health assessment. The deployment tracker separately labels PTZ#001 and PTZ#002 `INSTALLED` and PTZ#003 `Permitting / Processing / Pending - Awaiting Permit` ([[Jacksonville Flock Device Health and Deployment Tracker]]). A 2026 invoice itemizes one 128-stream Wing line at $4,000 and FlockOS Advanced at $7,500 alongside eight LPRs; it establishes billed product categories, not the health or ownership of 101 integrated streams ([[Jacksonville Flock LPR Contract and Renewal Invoices]], `Scan_2026_07_30_13_09_35_632.pdf`, p. 3). ## Russellville contract Russellville's customer- and vendor-signed 2024 order lists four Condor PTZ cameras and one eight-stream Wing gateway alongside 13 Falcon LPRs and FlockOS Advanced. A later inventory shows four park Condors, but it does not identify the gateway or any attached third-party stream. A February 2025 budgetary quote proposes replacing the original Condor/Wing line with four solar PTZ cameras; the accompanying amendment copy is unsigned ([[Russellville Flock Contract and PTZ Amendment]], `Flock Contract.pdf`, pp. 2, 6, 8-13). ## Internet-exposure dispute 404 Media reported that at least 60 Condor PTZ systems it examined exposed live streams, archived video, and administrative functions without authentication. Flock later acknowledged that a carrier placed a small number of PTZ cameras on a public cellular network and exposed a diagnostic interface, but disputed access to its cloud, camera control, modification, and archived video (web research 2026-07-20, [404 Media report](../../web%20archive/2026-07-20/404media.co/flock-condor-camera-internet-exposure-2025-12-22.md); vendor primary/self-description, [Flock cybersecurity response](../../web%20archive/2026-07-20/flocksafety.com/flock-safety-cybersecurity-how-we-protect-customer-community-data.md)). The competing accounts are preserved at [[T010 - Condor Internet Exposure Competing Accounts]]. ## Evidence boundary - “Non-biometric” is a vendor description of method; it does not mean the resulting clothing, movement, association, or location evidence is non-identifying. - A gateway's listed local capacity does not prove a customer's actual retention setting, network exposure, or cloud synchronization path. - The disputed 2025 exposure does not prove every Condor device was exposed, and Flock's response does not independently resolve what the examined systems allowed. - Jacksonville and Russellville are documented Arkansas Wing customers; Jacksonville also produced populated Wing tenant exports, while Russellville did not. No Tier-1 record on this page ties Wing or Condor to Conway, Little Rock, Pulaski County, Sherwood, Fayetteville, ASP, or ARDOT. ## Open questions - Do any Arkansas agencies hold Condor/Wing quotes, orders, asset inventories, diagrams, or tenant configuration exports? - For any deployed gateway: which streams are ingested, where is video stored, how long is it retained, and what identities can reach live, archived, or administrative functions? ## Bentonville and Van Buren current inventories Bentonville's August 2026 native export lists eighteen `Video Camera` rows in the Parks Condor tenant and eighteen paired compute boxes at the same coordinates. The current camera-site count is eighteen, not thirty-six ([[Bentonville Native Camera Inventory and Deployment Tracker]]). Van Buren's current export lists one City Park video camera plus a Main Street/8th Street dual-lens PTZ represented by one parent and two named channel rows. Those three PTZ-related rows remain one site in the public register ([[Van Buren Flock Locations and Health August 2026]]). ## Marion orders and sharing boundary Marion's additive records identify six Condors: three in the 2023 initial order, two in the 2025 parks order, and one in the hotels invoice (`Invoices - Flock.pdf`, pp. 1, 13-17; `Flock Safety - forms.pdf`, pp. 2-5; [[Marion Flock Orders Invoices and Camera Count]]). The July 2026 portal reports 32 total cameras and 25 LPR cameras, implying seven non-LPR cameras and leaving one non-LPR unit unidentified ([[T061 - Marion Thirty-Two-Camera Portal Total vs Six Identified Condors]]). Marion's sharing printout also uses a distinct `Marion AR PD Condor` network label on outbound relationships (`Shared Networks_2026_August11 Flock.pdf`, pp. 1-48; [[Marion SharedNetworks August 2026]]). That label proves a configured network name, not which video streams, cameras, users, or permissions it contains.