Is anyone identified?
No. People are counted as shapes crossing a line. No faces are stored, no one is identified, and only counts and occupancy leave the site.
Directional in and out counts and live occupancy at every entrance — anonymous, on-premise.
Flagship — Abdali Mall
--:--
Today
1,284
In store
37
Avg dwell
1m 12s
Entrance
1,284 · dwell 14s
New arrivals
842 · dwell 1m 36s
Checkout
611 · dwell 2m 22s
Back wall
203 · dwell 38s
edge-store-01 · healthy
by hour
People Counting measures how many people enter and leave a space, through every door, gate, or corridor you point a camera at.
Directional counts add up to live occupancy, so teams know how full a store, floor, or venue is right now, and how traffic moves through the day and week.
Counting runs on-premise and is anonymous by design: people are counted as shapes crossing a line. No faces are stored and no one is identified.Counts and occupancy flow to the dashboard, and threshold alerts — a floor over capacity, an entrance suddenly busy — go out through no-code automations.
Directional counts on virtual lines at each door, gate, or corridor, calibrated per entrance during the pilot.
Entries minus exits, per floor, zone, or building, with alerts when a space passes the limit you set.
Hourly, daily, and weekly traffic per entrance and site, ready to compare and export.
Powered by IFA
Runs as a module on the IFA edge box beside your cameras.
The IFA dashboard
Every IFA module reports into the same web dashboard. A new module shows up with its charts, events, and automations the day it is deployed — nothing is coded per module.
Plant overview — today
Events per hour
Events by severity
184 events · 2 modules · 4 cameras
Streams
Automation runs
Every camera as a health card: online, degraded, or offline, with frame rate, latency, and uptime, and a live view from the edge box when it is streaming. Refreshes on its own.
Pick a metric, group by line, zone, severity, or product, and bucket by hour, day, or week. Line, bar, area, stacked, and pie — all built from the events a module emits, never hand-coded.
Every event, filterable by module, type, and severity, with the frame that triggered it. Email and WhatsApp notifications go out through automations, with a per-run record of what was sent and what was suppressed.
A drag-and-connect flow builder: a trigger (a module event, a camera going offline, a schedule), logic (filter, window, cooldown, time gate), then actions — send an email, send a WhatsApp message, capture the frame, generate a report.
A report action turns a session or a shift into a readable document — totals, shares, per-product detail — attached to the notification email and kept in the dashboard's report list.
People counting questions
No. People are counted as shapes crossing a line. No faces are stored, no one is identified, and only counts and occupancy leave the site.
Accuracy depends on camera placement and height, so each entrance is checked against manual counts during the pilot before numbers go live. We report the measured accuracy per entrance rather than quoting one figure for every site.
Existing overhead or angled CCTV with an RTSP/ONVIF stream usually works. Where an entrance has no usable view, a standard IP camera is added. Counting runs on the IFA edge box on site.
Yes. Occupancy and count thresholds can trigger email alerts or reports through no-code automations in the dashboard, with every alert logged.
Last updated: