What is the difference between an access hub and a door controller?
A door controller manages 2–8 doors directly and executes local access policy (grant/deny based on credentials). A hub is a centralized platform that connects and orchestrates multiple controllers, readers, and I/O modules. Hubs provide enterprise-scale features: unified credential management, cross-site event correlation, policy updates, and audit trails. For small deployments (1–4 doors), a single controller suffices; for multi-building sites, a hub is necessary.
Do I need network connectivity for the hub to grant or deny access?
No. Modern hubs cache credentials locally on connected controllers, allowing offline door grants during WAN outages. However, real-time features (revoking a stolen card, pushing new policies) require the hub to reach controllers. Always deploy a UPS and test failover behavior: does your hub grant based on cached credentials, or fail-safe locked? This distinction is critical for compliance and safety.
How many door controllers can a single hub manage?
Capacity depends on the hub model: compact hubs manage 4–16 controllers, enterprise hubs support 64–256+. Network bandwidth is often the limiting factor—each event (door open, credential read, tamper) consumes bandwidth. Verify that your network uplink can handle peak event rates. For example, 100 doors each generating 100 events/hour = ~3 events/second; ensure your hub's network port and uplink have sufficient throughput.
Can I integrate access hubs with surveillance and building systems?
Yes. Most modern hubs expose APIs (REST, webhooks, MQTT) for third-party integration. IP cameras can be triggered to record on access-denied events; intercom/paging systems can announce visitor arrivals; building automation (HVAC, lighting) can unlock employee-only floors. Validate API support for your specific integrations before purchase—some hubs have limited or vendor-locked ecosystems.
What happens if the hub fails or goes offline?
Doors remain operable via cached credentials on local controllers. However, new credentials cannot be provisioned, revoked credentials are not enforced until sync resumes, and events are queued locally (not centrally logged). Deploy a redundant hub, regular backups, and a UPS to minimize downtime. For critical facilities, consider geographic redundancy: hub A (primary) and hub B (secondary) across separate networks.
How do I choose between on-premises and cloud-based hubs?
On-premises hubs offer full control, lower latency, and compliance (no third-party data access). Cloud hubs are easier to manage remotely, enable multi-site aggregation, and reduce IT overhead. Hybrid models (local policy enforcement + cloud sync) balance both. Verify data residency requirements, SLAs, and whether the hub supports offline operation if cloud service fails. For healthcare, finance, or government, on-premises is typically mandated.