RBH access control explained for facility security teams

privacy policy, keyboard, security, secure, to back up, protection, castle, chain, padlock, computer, pc, protect, trojan, data theft, password, keyword, privacy policy, privacy policy, privacy policy, privacy policy, privacy policy, keyword, keyword

a[data-rs-seo-link]{text-decoration:underline!important;color:#1a56db!important;cursor:pointer!important;}a[data-rs-seo-link]{text-decoration:underline!important;color:#1a56db!important;cursor:pointer!important;}

What RBH access control is

RBH access control refers to the physical access control software, controllers, readers, credentials and integrations offered by RBH Access Technologies. For a facility manager or security integrator, the main issue is not just whether the system can open and secure a door. It is which RBH platform fits the site: Integra32 for many small and midsize deployments, AxiomV or AxiomXa for larger and more complex environments, and AxiomCLOUD where browser-based administration and a cloud-managed operating model are appropriate. RBH public materials position the portfolio around access control, alarm monitoring, video, elevator control, visitor management and building automation, so it should be evaluated as a facility security platform rather than as a standalone reader package. For related industry background, visit our access control section.

How the RBH platform family fits together

RBH has several product names that may appear in proposals, support notes and upgrade discussions. These names matter because they point to different database models, server requirements, licensing approaches and expansion paths. Public RBH product and support materials available in November 2026 list Integra32, AxiomV, AxiomXa, AxiomCLOUD and RBH View as part of the software ecosystem. RBH View is a video management product, while the other platforms are more directly tied to access control and security management.

cyber, mac wallpaper, 4k wallpaper, security, full hd wallpaper, crack, crime, access, anti, cyberspace, data, design, wallpaper 4k, background, wallpaper hd, binary, blue, beautiful wallpaper, circuit, cool backgrounds, closed, free wallpaper, code, computer, laptop wallpaper, 4k wallpaper 1920x1080, concept, free background, connect, digital, firewall, guard, hacker, information, gray data, gray security, gray information, gray code, windows wallpaper, hd wallpaper, desktop backgrounds, gray coding
RBH option Role in the portfolio What to verify before specifying
Integra32 Security management software commonly positioned for small and midsize organizations, with access control plus related security integrations. Door count, client count, database needs, support status and whether a future Axiom migration is expected.
AxiomV Enterprise security management software for larger, multi-site or multi-tenant environments. Server design, SQL requirements, distributed components, operator roles, video and alarm workflows.
AxiomXa Newer enterprise security management family shown in RBH software comparison materials. Edition, API requirements, controller compatibility and project-specific feature licensing.
AxiomCLOUD Cloud-managed access control option promoted for remote administration, centralized visibility and reduced local server maintenance. Recurring cost model, controller firmware path, mobile needs, data hosting expectations and dealer support process.

Integra32 for small and midsize deployments

RBH describes Integra32 as a security management system that integrates access control with intrusion alarms, elevator control, CCTV and DVR connections, biometric authentication, photo ID, building automation and alarm monitoring. RBH product information also describes web browser and mobile support when the Integra web server is configured. Public materials state that Integra32 can start with smaller deployments and expand, including an in-place upgrade path to AxiomV. In November 2026, RBH support information listed Integra32 R5 v5.1.16 as the current release version.

The practical takeaway is that Integra32 should not be judged only by the initial number of doors. A small office, school building, clinic or multi-tenant property may also need visitor badges, elevator access, video call-up on events or audit-ready reporting. Those requirements should be documented before comparing controller kits or reader models.

AxiomV and AxiomXa for enterprise environments

RBH describes AxiomV as an enterprise security management system for large multi-site and multi-tenant applications. Public product descriptions emphasize access control, alarm monitoring, video, building automation, asset tracking, guard tour and visitor management. In November 2026, RBH support information listed AxiomV R4 v5.3.21 as the current release version. AxiomXa appears in RBH software and comparison materials as another enterprise security management option, with professional and enterprise editions shown in published comparison documents.

For a security team, the distinction is less about product branding and more about system architecture. Enterprise sites need clear answers on database segregation, operator permissions, distributed servers, reporting, failover expectations and integration boundaries. If a facility has multiple buildings, multiple tenant groups or strict separation between cardholder databases, those requirements should be written into the scope before a platform is selected.

AxiomCLOUD for cloud-managed access control

RBH describes AxiomCLOUD as a cloud-managed access control ecosystem for organizations that want centralized administration from browser-enabled devices without relying on local servers. Public RBH materials state that AxiomCLOUD is designed and hosted in Canada, backed by Microsoft Azure, and organized around centralized management, remote door control, real-time reports and a predictable per-door operating model. RBH also states that AxiomCLOUD can use proven RBH controller architecture and, in some cases, repurpose existing Axiom and Integra32 controller hardware through the correct compatibility path.

That does not mean every existing RBH site can move to cloud management without field work. Controller model, firmware, reader wiring, licensing, dealer access and network policy all matter. The strongest cloud migration plans start with a door-by-door hardware inventory and a written rollback plan.

Hardware and topology considerations

An RBH access control system is not only software. The field layer may include network controllers, reader controllers, input and output modules, enclosures, power supplies, readers and credentials. RBH hardware materials reference controllers used with both Integra32 and Axiom systems, including two-door controller options and D-NET or RS-485-connected devices in certain topologies. Published RBH topology documents also show that distance, cable type and communication method are part of the design, not details to resolve after installation starts.

Reader protocol is another important decision. RBH reader materials show support across technologies such as MIFARE, DESFire, Bluetooth, NFC, Wiegand and OSDP on selected reader families. The Security Industry Association describes OSDP as an open protocol used between access control panels and peripheral devices such as card readers, with bidirectional communication, device supervision and Secure Channel encryption capabilities. In practical terms, OSDP can provide stronger reader-to-controller communication than legacy one-way Wiegand wiring when it is supported, configured and keyed correctly.

However, support for OSDP at the product-family level does not prove that a particular installed door is using secure OSDP today. During assessment, the integrator should record the reader model, cable type, protocol mode, reader address, controller port, credential technology and whether secure channel keys are set. This is especially important when migrating legacy readers or mixing older and newer doors in the same facility.

Security and lifecycle questions to verify before deployment

Good access control design starts with policy. Widely used security guidance, including NIST principles, supports least privilege: people should receive only the access needed for their role and should lose it when that role changes. In physical security, that principle becomes a practical checklist: who can enter, where they can enter, during which schedule, under what exception process and with which audit trail.

  • Credential lifecycle: Define how badges, mobile credentials, temporary visitor passes and contractor credentials are issued, suspended and revoked.
  • Operator permissions: Separate everyday badge administration from system configuration, database maintenance and emergency override privileges.
  • Door behavior: Confirm fail-safe or fail-secure requirements, local fire code, emergency egress rules and authority-having-jurisdiction expectations.
  • Event review: Decide which alarms require live response, which events are retained for investigation and which reports management needs monthly.
  • Patch and support status: Check software maintenance dates before planning upgrades, because RBH support materials tie some software upgrades and support rights to the active support period.

These checks are especially important for sites that inherited an older RBH installation. A door may still work day to day even if the database, server operating system, backup process, firmware or support agreement no longer matches the current risk profile. See also: Alarm and Detection.

RBH access control selection checklist

Before choosing an RBH platform or approving a migration, teams should build a short, specific requirements document. This avoids the common mistake of selecting software by door count alone.

  1. Map the facility: Count doors, elevators, gates, turnstiles, alarm points, visitor desks and remote sites.
  2. Classify users: Separate employees, tenants, contractors, visitors, guards, administrators and emergency responders.
  3. List integrations: Document video, intrusion, elevator, biometric, building automation, HR database, reporting and notification requirements.
  4. Inventory hardware: Record controllers, reader models, power supplies, lock hardware, cabling, enclosure locations and network connections.
  5. Confirm hosting model: Decide whether the organization prefers on-premises servers, cloud management or a phased transition.
  6. Review support path: Check software version, maintenance expiry, dealer access, backup availability and upgrade eligibility.
  7. Plan testing: Test door schedules, lockdown behavior, visitor workflows, video pop-ups, alarm routing and credential revocation before handover.

The best-fit RBH option depends on this combined picture. Integra32 may be enough for a straightforward site with moderate expansion needs. AxiomV or AxiomXa may fit better when the system must handle enterprise workflows, multiple sites and more complex databases. AxiomCLOUD may be attractive when reducing local server maintenance and enabling remote administration are priorities.

Limitations and migration considerations

Public product literature is useful, but it cannot replace project validation. RBH controller comparison materials indicate that firmware and controller compatibility vary by solution, and some transitions require dealer flashing or physical firmware changes. For that reason, an upgrade from an older Integra32 or Axiom environment to another RBH platform should be treated as a controlled project, not as a simple software setting.

There are operational limits as well. Cloud management may simplify administration, but it introduces questions about internet resilience, account governance, service terms and recurring budgeting. On-premises systems may provide more local control, but they require server maintenance, backups, operating system care and a clear plan for software support. Enterprise systems may add useful segmentation and integrations, but they need disciplined configuration so operators can still understand and manage the system every day.

A sensible RBH migration plan starts with discovery, moves to lab or pilot testing, then converts doors in phases. Each phase should identify affected doors, credentials, controller firmware, reader protocol, database backup, expected outage window and rollback process. For high-risk openings such as server rooms, pharmacies, laboratories or main entrances, the team should test after-hours and keep mechanical or supervised contingency access available.

Frequently asked questions

Is RBH access control only for large facilities?

No. RBH public materials include options positioned for small and midsize deployments as well as enterprise and cloud-managed environments. The right fit depends on door count, integrations, reporting needs, database complexity, support model and expansion plans.

What is the difference between Integra32 and AxiomV?

Integra32 is commonly positioned for small and midsize security management needs, while AxiomV is described by RBH as an enterprise security management system for larger multi-site or multi-tenant applications. The decision should be based on architecture, database requirements, integration scope and long-term growth rather than product name alone.

Does RBH support cloud access control?

Yes. RBH describes AxiomCLOUD as a cloud-managed access control ecosystem with browser-based administration, centralized site management, remote control functions and a per-door operating model. Existing hardware compatibility should be verified before assuming a direct migration.

Should an existing RBH site upgrade or replace hardware?

Not automatically. Many sites should begin with an inventory and support review. If controllers, readers, firmware and cabling support the target platform, a phased upgrade may be possible. If key components are obsolete, unsupported or incompatible with the desired security model, targeted replacement may be safer.

What should buyers ask an integrator before approving RBH access control?

Ask for a written platform recommendation, door schedule, controller list, reader protocol plan, credential strategy, licensing assumptions, support terms, backup plan and acceptance test checklist. These items make the proposal easier to compare and reduce surprises during commissioning.