Signals connects to existing camera infrastructure and turns every space into a queryable data layer. Ask any question in plain English. Get clips, counts, and recommendations back in seconds. Not surveillance. Operations.
The natural language interface is the difference. Every other camera analytics platform on the market gives operators dashboards and filters. Signals gives them a question box. The same question your COO would ask, asked the same way, with an answer back in seconds.
"How many customers left the line at register 3 before being served yesterday between 4 and 6pm?"
"Show me anyone who accessed the chemistry building loading dock after 10pm in the past 30 days who isn't on the authorized list."
Any question about any camera at any point in time, asked in plain English. Returns clips, counts, summaries, or recommended actions. No specialist required.
Dwell time, line length, traffic flow, zone occupancy, engagement patterns. The data your cameras have always seen but never surfaced.
Configurable rules engine. Operators set thresholds for what matters in their environment. Slack, Teams, SMS, or alert console delivery.
Behavioral deviation flagged before it becomes an incident. After-hours access, unusual movement patterns, density violations.
Per-vertical dashboards configured for the people who actually use them. Not a security monitor. A live operational picture.
Connects to VMS, POS, BMS, access control, ticketing, and the rest of the systems already in your stack. REST API for everything else.
Where Signals runs is a decision driven by your data sovereignty requirements, your site count, and your network. Same platform underneath. Choose the mode that fits your environment.
All inference runs on-site on a compact Qualcomm-powered device. No footage routed to the cloud. No per-frame compute costs. Sub-second alert latency. Fully operational without internet connectivity.
Regulated industries. Campus FERPA. Single-site operators with data sovereignty requirements.
Edge handles real-time alerting and privacy-sensitive processing. Cloud powers indexed search, cross-site analytics, and historical trend reporting. The configuration most enterprise deployments end up choosing.
Stadiums, university campuses, multi-building portfolios, multi-property CRE operators.
Camera streams route to a managed cloud environment for processing, indexing, and storage. Longer retention windows. Access from anywhere. Centralized analytics across every location.
Multi-site chains. Franchise portfolios. CRE operators where central visibility matters more than local data control.
Generic camera analytics platforms try to be everything. Signals is the opposite. Four focus verticals. Per-vertical event taxonomies, dashboards, integrations, and pricing. Pick the one that matches your environment.
Concession line management, gate flow, crowd density, sponsorship verification. The strongest ROI case in the portfolio. Recovering 10% of abandoned concession transactions at a 20,000-seat venue is a six-figure season.
Building occupancy, dining lines, study space utilization, event safety, occupancy-driven HVAC. FERPA-compliant edge deployment by design. Typically 15-25% reduction in academic building energy use.
Conversion by zone, dwell by display, line abandonment, staff coverage, loss prevention. Already deployed in production at Hi-Life convenience chain across Taiwan. Multi-site cloud or hybrid configurations.
Verified tenant traffic, lobby and amenity occupancy, energy optimization, lease negotiation data. Co-sell ready with BIMstream's built environment platform. Behavioral layer on top of the static building model.
Signals does not replace your camera infrastructure, your VMS, your POS, your access control, or your BMS. It connects to them and turns the data they produce into operational intelligence. Below is a partial integration list across the four focus verticals.
| Camera & VMS | Axis · Hanwha · Hikvision · Dahua · Milestone XProtect · Genetec Security Center · Avigilon |
| Edge Hardware | Qualcomm-powered devices (preferred) · IP camera-direct compatibility |
| Point of Sale | Square · Lightspeed · NCR · Oracle Retail · Oracle MICROS · Shopify POS · Clover · Appetize |
| Access Control | Lenel (UTC) · Genetec · Brivo · HID |
| Building Management | Siemens · Honeywell · Johnson Controls · Schneider EcoStruxure |
| Ticketing | AXS · Ticketmaster · SeatGeek (entry flow correlation) |
| Workforce | Deputy · Sling · UKG (staffing alerts from live traffic) |
| BI & Reporting | Power BI · Tableau · Looker · REST API for everything else |
| Comms | Slack · Microsoft Teams · SMS · PagerDuty (alert routing) |
Cameras are commoditized. The platforms that operate on top of them are not. Every stadium, campus, store, and office building runs cameras that produce footage nobody watches. Signals turns that footage into a live operational picture and a queryable record.
Privacy is not a policy bolted on after the fact. It is a structural property of how the platform is built. Signals operates on behavioral events, not people. No biometric identifiers, no facial recognition, no personal data records. Edge deployment keeps customer footage inside customer infrastructure.
Edge deployment at the building level. Student-identifying footage never leaves the network. Anonymized behavioral metadata only.
Vision models trained to extract behavioral events without creating biometric or personal data records. Illinois, Texas, and Washington biometric law compliance built in.
Continuous controls monitoring. Audit logging on every customer data access. Encryption in transit and at rest. Penetration tested annually.
Pilots run 60 to 90 days depending on vertical. Defined KPIs agreed in advance. Pilot fee credited against year one on conversion. Three to five sites for retail, one event window or 60 days for stadium, one building or zone for campus, one property for CRE.