Commissioned Research
Top 10 Best Occupancy Counting Software of 2026

GITNUXSOFTWARE REVIEW

Facilities & Property Services

Top 10 Best Occupancy Counting Software of 2026

Compare occupancy counting software options with tradeoffs for retail and venues, covering tools like Butlr, FootfallCam, and PointGrab.

21 min readUpdated Editorially scoped research
How we ranked these tools
01Editorial Scope

Vendors set the topic, but our editors set the inclusion criteria and the evaluation framework before research starts.

02Source Research

Agents extract product evidence with provenance, then collect written reviews and transcribe video reviews and podcasts.

Read our full methodology →

Framework: Features 40% · Ease 30% · Value 30%

Gitnux may earn a commission through links on this page. This does not influence our reviews. Editorial policy

Occupancy counting software turns sensor detections into usable occupancy signals for real estate and retail teams that need planning-grade space utilization, not just raw footfall. This comparison focuses on data pipelines, privacy controls, and integration paths that determine how quickly occupancy counts become dashboards, automations, and capacity decisions.

Butlr is the best pick for facilities teams needing zone-level occupancy from cameras because its configurable ingress and egress counting zones stream clean analytics outputs, while FootfallCam is a strong alternative for multi-site rollouts since its overhead zone mapping supports bidirectional behavior with real-time dashboards.

Editor’s top 3 picks

Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.

Editor pick
1

Butlr

Configurable ingress and egress counting zones tied to a zone-level analytics output stream.

Best for: Fits when facilities teams need zone-level occupancy from cameras with configurable counting lines and periodic recalibration.

2

FootfallCam

Editor pick

Overhead counting with configurable ingress and egress zone mapping that preserves bidirectional behavior per area.

Best for: Fits when facilities teams need zone-level occupancy for multiple sites with repeatable sensor deployments.

3

PointGrab

Editor pick

Ingress and egress zone configuration drives direction-aware occupancy analytics through its real-time occupancy API.

Best for: Fits when facilities teams need zone-level occupancy APIs and direction-aware counting across multiple sites.

Comparison Table

1
ButlrBest overall
enterprise
9.0/10
Overall
2
8.8/10
Overall
3
enterprise
8.6/10
Overall
4
vertical specialist
8.5/10
Overall
5
enterprise
8.3/10
Overall
6
7.7/10
Overall
7
7.4/10
Overall
8
enterprise
7.3/10
Overall
9
enterprise
6.8/10
Overall
10
6.5/10
Overall
#1

Butlr

enterprise

Anonymous people sensing platform for occupancy detection, room usage, and spatial intelligence.

9.0/10
Overall
Features9.0/10
Ease of Use9.0/10
Value9.0/10
Standout feature

Configurable ingress and egress counting zones tied to a zone-level analytics output stream.

Butlr is occupancy counting software built around video-based footfall measurement using a counting camera and configurable counting zones. It converts people movement across defined ingress and egress areas into occupancy metrics and zone-level counts for facilities and retail operations.

The product emphasizes on-site sensor deployment and ongoing accuracy handling through its own calibration and device health workflow. Butlr also supports a data feed for downstream reporting so occupancy trends can be consumed by other systems.

Pros
  • +Counting-zone configuration supports ingress and egress definitions
  • +Video analytics approach works without dedicated infrastructure like PoE thermal arrays
  • +Device health workflow reduces downtime during camera performance issues
  • +Occupancy metrics are exported for reporting and dashboards
Cons
  • –Counting accuracy depends on camera placement and stable sightlines
  • –Multi-site aggregation and governance controls can feel minimal at scale
  • –API polling interval tuning requires operational oversight for real-time use cases
  • –Calibration drift handling is a recurring admin task after environmental changes
Use scenarios
  • Retail operations managers

    Measure ingress and egress footfall

    Cleaner footfall reporting

  • Facilities and property teams

    Validate accuracy with calibration workflow

    Fewer count discrepancies

Show 1 more scenario
  • Operations analysts

    Ingest occupancy trends into reports

    Trends available outside dashboard

    Use exported data feeds to push occupancy trends into downstream reporting and analytics workflows.

Best for: Fits when facilities teams need zone-level occupancy from cameras with configurable counting lines and periodic recalibration.

#2

FootfallCam

SMB

People counting and occupancy monitoring platform with in-store analytics, dashboards, and sensor hardware.

8.8/10
Overall
Features8.8/10
Ease of Use8.8/10
Value8.8/10
Standout feature

Overhead counting with configurable ingress and egress zone mapping that preserves bidirectional behavior per area.

FootfallCam is built around calibrated people counting from overhead sensors, then converts those inputs into an occupancy dashboard with zone-level breakdowns. The workflow supports multi-site aggregation and historical occupancy trend analysis, which helps when rollouts span multiple floors or buildings. Admin control is centered on managing sensor locations, zone configurations, and role-scoped access to reporting views.

A key tradeoff is the need for careful zone and line configuration when layouts include irregular walk paths or multiple entry points. FootfallCam is most useful in facilities rollouts where PoE sensor deployment reduces installation complexity and teams can standardize configurations across similar sites.

Pros
  • +Zone-level occupancy outputs for facilities reporting
  • +Edge to cloud counting workflow supports real-time dashboards
  • +PoE sensor deployment speeds site installs
  • +Multi-site aggregation for cross-building trend views
Cons
  • –Zone and line calibration needs layout-specific tuning
  • –Reporting depth can require admin attention to keep definitions consistent
  • –API coverage depends on selected integration approach
  • –Outlier counts can persist after layout changes without revalidation
Use scenarios
  • Facilities and operations teams

    Monitor zone occupancy during peak hours

    Fewer crowding surprises

  • Retail analytics teams

    Measure space utilization by zone

    Better staffing alignment

Show 2 more scenarios
  • Multi-site rollout managers

    Aggregate occupancy across buildings

    Consistent rollouts

    Multi-site reporting consolidates historical occupancy trend comparisons for the full portfolio.

  • Space planning teams

    Validate utilization changes after re-layout

    More reliable utilization forecasts

    Re-running zone definitions after floor changes supports before and after occupancy analysis.

Best for: Fits when facilities teams need zone-level occupancy for multiple sites with repeatable sensor deployments.

#3

PointGrab

enterprise

Workplace occupancy sensing platform that tracks desk, room, and zone utilization with edge-based sensors.

8.6/10
Overall
Features8.6/10
Ease of Use8.6/10
Value8.6/10
Standout feature

Ingress and egress zone configuration drives direction-aware occupancy analytics through its real-time occupancy API.

PointGrab fits facilities organizations that need zone-level counting and historical occupancy trend reporting, because occupancy is computed per configured area rather than only as total visitors. Deployment options commonly include PoE sensor deployment and edge-based counting, which reduces dependence on constant high-bandwidth video streaming. The integration surface targets building management system integration and external analytics consumers through an occupancy API, plus exported datasets for reporting workflows.

A tradeoff appears in sensor calibration drift management, since accurate counts depend on keeping counting lines and mounting conditions stable over time. The best usage situation is recurring peak hour analysis for public venues and workplace environments, where direction-aware ingress and egress definitions support operational decisions like staffing and crowd control.

Pros
  • +Bidirectional counting accuracy with configurable ingress and egress zone boundaries
  • +Real-time occupancy API for integrating zone metrics into external dashboards
  • +Edge-based counting reduces reliance on continuous upstream video processing
  • +Multi-site aggregation supports consistent zone definitions across buildings
Cons
  • –Sensor calibration drift requires periodic checks to preserve accuracy
  • –Edge installations require careful commissioning to match mounting and line geometry
  • –Tuning occupancy thresholds and alerts needs governance by zone owners
Use scenarios
  • Facilities operations teams

    Zone-level occupancy threshold alerting

    Lower crowding risk

  • Workplace analytics teams

    Peak hour analysis across floors

    More accurate staffing

Show 2 more scenarios
  • System integrators

    Building management system integration

    Fewer manual exports

    An occupancy API delivers zone metrics for BMS workflows and reporting pipelines.

  • Multi-site property managers

    Central dashboard across buildings

    Faster oversight

    Multi-site aggregation keeps consistent zone definitions for comparative occupancy reporting.

Best for: Fits when facilities teams need zone-level occupancy APIs and direction-aware counting across multiple sites.

#4

V-Count

vertical specialist

Retail traffic and occupancy analytics platform that combines people counting sensors with business intelligence dashboards.

8.5/10
Overall
Features8.5/10
Ease of Use8.5/10
Value8.5/10
Standout feature

Zone mapping based on ingress and egress definitions for bidirectional flow segmentation.

V-Count supports zone-level counting driven by configured counting line and ingress or egress definitions, which is a closer match to facilities workflows than simple building-wide totals. The operational model centers on ongoing sensor health checks and calibration handling, which matters for sensor calibration drift across high-traffic locations. Multi-site aggregation and a dashboard view help staff compare utilization rates across buildings without re-building reports each time.

Pros
  • +Zone-level counting configuration maps to facilities entry and corridor layouts
  • +Threshold alerting connects occupancy changes to operational response workflows
  • +Historical occupancy trend views support capacity planning and peak hour analysis
  • +Multi-site aggregation reduces repeated reporting work across buildings
Cons
  • –Counting line configuration requires more site-specific tuning than building-wide counting
  • –Best results depend on sensor placement constraints like mounting height and angle
  • –Real-time updates can require disciplined API polling interval choices
  • –Edge to cloud processing increases troubleshooting steps during deployments
Use scenarios
  • Facilities operations teams

    Lobby and corridor occupancy alerts

    Faster staffing and crowd control

  • Space planning analysts

    Peak hour utilization reporting

    More accurate utilization baselines

Show 2 more scenarios
  • Building managers

    Multi-site occupancy trend review

    Consistent reporting across buildings

    Aggregate occupancy dashboards across multiple sites to compare utilization changes over time.

  • Security and compliance staff

    Privacy-by-design footfall monitoring

    GDPR-aligned occupancy analytics

    Run occupancy counting without requiring identity-level data to track footfall by zone and time.

Best for: Fits when facilities teams need zone-level occupancy visibility with alerting and repeatable multi-site reporting.

#5

Density

enterprise

Occupancy analytics software with privacy-safe people counting sensors and real-time space utilization dashboards.

8.3/10
Overall
Features8.3/10
Ease of Use8.3/10
Value8.3/10
Standout feature

Real-time occupancy API paired with zone and alert rules designed for automated operational triggers.

Density is an occupancy counting software built around computer-vision detection and a cloud occupancy dashboard. It supports zone-level counting and occupancy threshold alerting so facilities teams can react to exceedances without manual spreadsheet checks.

Pros
  • +Zone-level counting with consistent ingress and egress zone definitions
  • +Real-time occupancy API for automated dashboards and downstream systems
  • +Occupancy threshold alerting for operational response to crowding
  • +Cloud occupancy dashboard for historical occupancy trend review
Cons
  • –Counting line configuration can be time-consuming during rollout
  • –Video analytics throughput can be sensitive to camera placement and lighting
Use scenarios
  • Retail and venue operators

    Track corridor traffic by zone

    Traffic monitoring by zone

  • Facilities and office administrators

    Monitor meeting room capacity

    Room availability reflects use

Show 2 more scenarios
  • Workplace operations teams

    Tune desk hoteling rules

    Hot-desks match real demand

    Compare desk reservations with observed occupancy to adjust booking availability and policy decisions.

  • Venue event operations teams

    Alert on zone capacity exceedance

    Faster response to crowding

    Set occupancy thresholds per zone to surface live density risks during events and staffing decisions.

Best for: Fits when facilities teams need zone-accurate occupancy data with an API for automated BMS and analytics workflows.

#6

Steerpath

SMB

Office analytics software that provides occupancy data, desk utilization metrics, and real-time workplace insights.

7.7/10
Overall
Features7.7/10
Ease of Use7.7/10
Value7.7/10
Standout feature

Real-time occupancy API retrieval paired with threshold-based alerts for zone density conditions.

Steerpath targets occupancy counting deployments that need operational reporting, zone-level visibility, and workflow handoffs for facilities teams. The system centers on video analytics based counting with configurable counting lines and zone definitions, then publishes occupancy metrics into a cloud dashboard for day-to-day review.

Pros
  • +Zone-level occupancy reporting designed for facilities workflows
  • +Configurable counting lines and ingress-egress zone definition
  • +API access for real-time occupancy and analytics retrieval
  • +Threshold alerting supports density response without manual checks
Cons
  • –Video-based counting can require careful calibration to reduce drift
  • –Integration depth depends on aligning data outputs to existing systems
Use scenarios
  • Facilities and operations teams

    Review zone occupancy in reports

    Zone visibility for operations

  • Automation and integration teams

    Retrieve occupancy metrics via API

    Occupancy data outside the UI

Show 1 more scenario
  • Workplace density analysts

    Automate recurring density reporting

    Less manual reporting work

    Use threshold alerting and recurring reports to deliver occupancy updates without manual spreadsheets.

Best for: Fits when facilities teams need zone-level occupancy dashboards plus an API for downstream automation.

#7

Envoy Workplace

SMB

Workplace platform with live occupancy visibility, desk and room usage controls, and capacity management for offices.

7.4/10
Overall
Features7.4/10
Ease of Use7.4/10
Value7.4/10
Standout feature

Configurable counting zones with real-time occupancy threshold alerting for per-area density monitoring in the facilities manager view.

Envoy Workplace counts people in office spaces by combining room and area occupancy signals with configurable zones for facility reporting. It provides a real-time occupancy dashboard and an occupancy threshold alerting workflow that helps teams react when density crosses set levels.

Pros
  • +Zone-level counting setup supports ingress and egress area definitions
  • +Occupancy threshold alerting reduces manual monitoring during peak periods
  • +Multi-site aggregation supports standardized dashboards across facilities
  • +Video analytics SDK integration supports custom workflows around occupancy state
Cons
  • –Counting line configuration requires careful calibration to avoid drift effects
  • –Real-time occupancy API coverage depends on a consistent sensor-to-cloud data path
Use scenarios
  • Office space managers

    Report live occupancy by zone

    Current density visibility

  • Facilities teams

    Trigger alerts when density spikes

    Faster reaction to exceedances

Show 1 more scenario
  • Workplace technology teams

    Send occupancy events to systems

    Occupancy feeds into workflows

    Use integrations to push occupancy state and events for building workflows and facilities use cases.

Best for: Fits when facilities teams need zone-level occupancy alerts and centralized dashboards across multiple office sites.

#8

XY Sense

enterprise

Workplace intelligence platform that measures occupancy, desk usage, and meeting room utilization with privacy-first sensors.

7.3/10
Overall
Features7.3/10
Ease of Use7.3/10
Value7.3/10
Standout feature

Zone boundary management that supports line-based counting configuration and threshold alerting per defined area.

XY Sense counts occupancy by turning people-counting sensor feeds into zone-level analytics and alerts. It supports multiple sensor types and configurations, then aggregates results into a cloud occupancy dashboard with historical trend views.

Pros
  • +Zone-level occupancy reporting with configurable ingress and egress boundaries
  • +API access for real-time occupancy feeds into building workflows
  • +Historical occupancy trend views for peak-hour and utilization analysis
  • +Sensor calibration and drift handling tools for long-running deployments
Cons
  • –Counting-line configuration can be time-consuming for complex layouts
  • –Automation coverage depends on API polling interval choices
  • –Governance controls are limited for large multi-site deployments
  • –Higher accuracy depends on careful sensor placement and commissioning
Use scenarios
  • Facilities teams

    Calibrate counting lines for accuracy

    More reliable occupancy counts

  • Office operations managers

    Monitor occupancy trends by zone

    Trends for zone performance

Show 2 more scenarios
  • Systems integration engineers

    Use API for real-time occupancy

    Real-time occupancy automation

    Connect the API to drive real-time occupancy actions in downstream automation workflows.

  • Security and compliance coordinators

    Alert on threshold exceedances

    Alerts for density exceedance

    Configure threshold alerts so density exceedances surface through operational workflows for rapid response.

Best for: Fits when facilities teams need zone-level occupancy analytics plus a real-time API feed.

#9

Vergesense

enterprise

Space occupancy intelligence platform that tracks people presence and workplace utilization across offices.

6.8/10
Overall
Features6.8/10
Ease of Use6.8/10
Value6.8/10
Standout feature

Privacy-by-design video analytics workflow designed to produce occupancy without storing identifiable footage as the primary output.

Vergesense targets occupancy counting through vision-based sensors and an edge-to-cloud pipeline built for facilities deployments. It focuses on zone-level counts with configurable entry and exit counting lines, then publishes occupancy to operational dashboards and integrations.

Pros
  • +Zone-level ingress and egress counting via configurable counting lines
  • +Privacy-focused video analytics approach supports GDPR-aligned workflows
  • +Edge-first architecture reduces dependency on continuous upstream connectivity
  • +Integrates occupancy outputs into building workflows through available interfaces
Cons
  • –Accuracy is sensitive to calibration and counting line placement
  • –Setup requires on-site configuration discipline for each monitored zone
Use scenarios
  • Facilities and building operations teams

    Analyze dwell and recurrence patterns

    Traffic flow visibility

  • Workplace technology teams

    Connect occupancy signals to operations

    Signals available for analysis

Show 2 more scenarios
  • Workplace strategists and planners

    Base capacity decisions on observed demand

    Capacity matches measured use

    Compare allocation ratios using observed occupancy patterns instead of relying on assumptions.

  • Corporate real estate teams

    Study peak rates across floors

    Repeatable utilization evidence

    Review mapped room, floor, and zone utilization using occupancy rates, density, and peak patterns.

Best for: Fits when facilities need zone occupancy counts from vision sensors with operational integrations.

#10

Kontakt.io Occupancy Management

vertical specialist

RTLS-based occupancy management software for tracking room capacity, zone utilization, and live occupancy status in workplaces and healthcare sites.

6.5/10
Overall
Features6.5/10
Ease of Use6.5/10
Value6.5/10
Standout feature

Occupancy threshold alerting tied to zone-level counts and a real-time occupancy API for external triggers.

Kontakt.io Occupancy Management combines people counting from compatible IoT hardware with a cloud occupancy dashboard for zone-level tracking and historical occupancy trends. The solution focuses on automation around occupancy threshold alerting and configurable counting line behavior so facilities teams can tune counts by ingress and egress context.

Pros
  • +Real-time occupancy API supports downstream dashboards and integrations
  • +Zone-level counting supports building-wide occupancy visibility by area
  • +Automation rules for occupancy threshold alerting reduce manual monitoring
  • +Multi-site aggregation supports centralized reporting across deployments
Cons
  • –Counting accuracy depends on correct counting line and zone configuration
  • –Video analytics SDK style workflows are not included in typical sensor deployments
Use scenarios
  • Multi-site facilities teams

    Track occupancy across zones

    Historical occupancy visibility

  • Workplace technology teams

    Feed occupancy into building systems

    Occupancy drives automation

Show 1 more scenario
  • Facilities admins and schedulers

    Tune counting lines by ingress and exit

    Counts align with access routes

    Configure counting line behavior to match ingress and egress context for more accurate occupancy tracking.

Best for: Fits when facilities teams need zone occupancy counts with API access and threshold alert automation.

Conclusion

After evaluating 10 occupancy counting software, Butlr stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.

Our Top Pick
Butlr

Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.

Frequently Asked Questions About Occupancy Counting Software

How does real-time occupancy delivery differ between PointGrab, Density, and Steerpath?
PointGrab converts sensor streams into zone-level occupancy and exposes a real-time occupancy API for downstream consumers. Density pairs its zone and alert rules with a real-time occupancy API aimed at automated BMS and analytics workflows. Steerpath emphasizes API retrieval for occupancy and related analytics while keeping the primary workflow centered on cloud dashboards and threshold alerting.
Which tools support bidirectional counting accuracy using ingress and egress boundaries?
PointGrab drives direction-aware occupancy by configuring ingress and egress zones and exporting zone-level occupancy through its real-time occupancy API. V-Count uses ingress and egress zone definitions to segment bidirectional flow and then applies threshold alerts on the resulting zone counts. FootfallCam also relies on configurable ingress and egress zone mapping to preserve direction behavior per area.
How do zone-level counting and counting line configuration show up in V-Count versus XY Sense?
V-Count focuses on configuring counting zones and calibrating sensor inputs, then publishing occupancy threshold alerts from zone-level metrics. XY Sense centers on calibrating counting lines and managing zone definitions, then aggregates results into a cloud occupancy dashboard with historical trend views. Both publish alerting, but V-Count ties the admin workflow to zone setup and calibration, while XY Sense stresses line-based configuration for zone boundaries.
When does an edge-to-cloud workflow matter for FootfallCam, Vergesense, and Butlr?
FootfallCam uses an edge to cloud counting workflow so zone-level occupancy streams can be generated for multiple sites with repeatable sensor deployments. Vergesense deploys vision sensors with an edge-to-cloud pipeline and makes counting line configuration a dependency alongside calibration for deployment accuracy. Butlr emphasizes on-site camera deployment plus calibration and device health workflows, which affects operational overhead when hardware is distributed across sites.
What breaks if counting line or zone boundaries drift from the physical layout, and how do tools mitigate it?
If counting lines or ingress and egress zones no longer match the walk paths, bidirectional counting accuracy can degrade and zone threshold alerting can trigger based on misclassified movement. Butlr addresses this with ongoing accuracy handling through its calibration and device health workflow tied to the counting zones. Vergesense similarly depends on calibration and counting line configuration rather than only software setup, so drift control must be treated as an operational process.
How do Envoy Workplace and Kontakt.io differ in the way they produce and react to occupancy threshold alerts?
Envoy Workplace uses camera-based people counting within defined counting lines and zones, then applies occupancy threshold alerting per area in the facilities manager view. Kontakt.io centers threshold alerting tied to zone-level counts and pairs it with a real-time occupancy API pattern for external triggers. Both support threshold alerting, but Envoy Workplace is built around office room and area occupancy signals, while Kontakt.io is built around IoT-compatible hardware and an API-first external trigger workflow.
Which tools offer multi-site aggregation and centralized administration for facilities teams?
PointGrab supports multi-site aggregation so centralized monitoring can span multiple buildings and floor plans. V-Count is built around repeatable multi-site reporting workflows that include multi-site alerting based on configured zones. Kontakt.io Occupancy Management adds centralized admin workflows for multi-site aggregation and recurring report needs, while Butlr focuses more on on-site deployment and calibration operations.
How do API-based integration workflows compare between Density, XY Sense, and Envoy Workplace?
Density provides a real-time occupancy API designed to feed BMS integrations and automated analytics workflows alongside zone and alert rules. XY Sense offers an API for real-time occupancy use cases while keeping the operational workflow anchored in cloud dashboards and historical trends. Envoy Workplace pushes occupancy events and state for facilities use cases through integrations tied to its real-time occupancy dashboard and threshold alerting workflow.
What security and privacy controls differ when using Vergesense and other vision-based tools?
Vergesense emphasizes privacy-by-design video analytics workflows that make occupancy output the primary result without storing identifiable footage as the main output. Butlr and FootfallCam both rely on camera-based counting workflows with configurable counting zones, which shifts privacy risk management toward deployment practices and footage handling choices. This is why Vergesense positions its workflow as a built-in privacy control rather than treating it as a post-processing decision.

Tools reviewed

Primary sources checked during evaluation.

Referenced in the comparison table and product reviews above.

How to Choose the Right Occupancy Counting Software

Different options separate themselves by how measurement becomes decisions: reliability of occupancy counting accuracy, how you configure counting behavior, and how much automation and API control you get over counts and events. In practice, the gaps show up during setup and during the handoff from live sensors to your workflow.

Counting accuracy validation workflow

Why it matters

Counting accuracy validation workflow matters because occupancy counting software lives or dies on whether reported counts match real door traffic. Without a clear way to validate, you may only discover errors after deployment.

How to check

Ask for a demo where they walk through a validation run against a known manual count or a provided test scenario. Look for a checklist that includes input capture time, a tolerance rule, and how they handle mismatches.

Sensor and camera configuration options

Why it matters

Sensor and camera configuration options matter because counting behavior changes with placement, angles, and lighting or coverage. The more explicit the configuration, the easier it is to get stable results without constant tweaks.

How to check

During the demo, request to see how they handle common setup variants (new camera angle, changed entrance location, or different coverage area). Confirm whether the configuration is expressed as testable settings and whether they show expected impact on counts.

Events and occupancy data model

Why it matters

Events and occupancy data model matters because downstream systems need consistent meaning, not just numbers. If the data model is vague, automations and reporting will drift when you change entrances or time periods.

How to check

Ask to receive a sample export or API response showing fields for occupancy state and event timestamps for entry/exit. Check whether identifiers for locations and time windows stay consistent across reconfigurations.

Automation and occupancy API surface

Why it matters

Automation and occupancy API surface matters because the value is in actions you trigger from counts. If the API is limited to dashboards, teams lose control over workflows and integrations.

How to check

Ask the vendor to show a short automation scenario: pulling counts, creating an alert or task, and writing the result into another system. Confirm what can be pushed or subscribed (for example, event webhooks vs polling) and how they document payload structure.

Admin controls and audit log

Why it matters

Admin controls and audit log matter because occupancy counting software will be tuned over time and multiple people will touch configuration. If changes can’t be traced, you can’t explain shifts in reported occupancy.

How to check

In the admin demo, ask how roles are separated and whether changes to counting configuration are recorded with who and when. Then request an audit view for the last configuration change and verify the timestamps and linked configuration items.

Privacy controls for stored data

Why it matters

Privacy controls for stored data matter because occupancy counting frequently relies on video inputs even when you don’t want raw footage retained. Strong controls reduce risk while keeping counts usable for operations.

How to check

Ask what data is retained by default and what can be turned off (for example, video storage, frame retention, or export history). Check for configurable retention periods and whether privacy settings remain effective after configuration updates.

Red flags

  • The tool can’t show a repeatable counting accuracy validation workflow
  • Configuration changes don’t produce explainable changes in counts
  • No clear events or API payload that matches the intended occupancy meaning

Fit by situation

  • If you must prove counts to internal stakeholders before rollout, prioritize counting accuracy validation workflow.
  • If you expect entrances to change or coverage to be reworked, prioritize sensor and camera configuration options.
  • If you need other systems to react automatically to occupancy changes, prioritize Automation and occupancy API surface.
Commissioned Research

Funding and competing interests

This study was co-funded by several of the vendors assessed in it. No single vendor funded it. Funders could propose the market studied.

They had no role in selecting vendors, setting or weighting criteria, analysing data or drawing conclusions, and they received the same factual-accuracy check as every other vendor assessed.

Market definition, inclusion rules and criteria weights were fixed by an editor before research began and did not change afterwards. Editorial process →

Keep exploring

FOR SOFTWARE VENDORS

Not on this list? Let’s fix that.

Our best-of pages are how many teams discover and compare tools in this space. If you think your product belongs in this lineup, we’d like to hear from you—we’ll walk you through fit and what an editorial entry looks like.

Apply for a Listing

WHAT THIS INCLUDES

  • Where buyers compare

    Readers come to these pages to shortlist software—your product shows up in that moment, not in a random sidebar.

  • Editorial write-up

    We describe your product in our own words and check the facts before anything goes live.

  • On-page brand presence

    You appear in the roundup the same way as other tools we cover: name, positioning, and a clear next step for readers who want to learn more.

  • Kept up to date

    We refresh lists on a regular rhythm so the category page stays useful as products and pricing change.