RBH Axiom vs Integra32: Choosing the Right Access Control Platform
Essential Security Supplies
RBH Integra32 and RBH Axiom are access control platforms from the same manufacturer, but they are intended for different operating requirements. For New Zealand security integrators, the decision is less about choosing a brand and more about the number of access points, how the site will be managed, the integrations required and the likely expansion over the system's working life.
Integra32 supports commercial access control with options such as alarms, video integration, visitor management, mobile access and lift control. AxiomV and AxiomXa extend the RBH range into more demanding multi-site, high-availability and enterprise security environments. Both require edition-specific checks before a system is specified.
RBH Integra32: commercial access control with room to grow
Integra32 is suited to small and medium-sized facilities that need centrally managed doors, cardholders, time schedules and event monitoring without starting with an enterprise-scale architecture. Typical projects include offices, warehouses, schools, residential complexes and smaller multi-building sites.
It should not be dismissed as a basic door-only system. RBH lists anti-passback, high-security modes, scheduled locking, door-held and forced-door alarms, visitor management, web and mobile clients, biometric support, video integration and lift control among its Integra capabilities. Availability can depend on the software release, controller, licensing and associated modules.
RBH's software edition comparison (Integra32 R5) lists support for up to 128 access points, including 64 in the base configuration. These are R5 edition figures; confirm the specification for the software version being supplied. Confirm the exact licence, client count, expansion requirements and controller compatibility at quotation stage rather than treating the maximum figure as an included entitlement.

RBH Axiom: more extensive management and integration
Axiom is RBH's broader security management family, including AxiomV and AxiomXa editions. It is aimed at projects needing more extensive access control expansion, alarm processing and operational functions across large or distributed estates.
Depending on the chosen edition and modules, Axiom supports centralised multi-site management, local operator permissions, advanced event handling, enterprise reporting, dynamic mapping, video management integration, visitor management, guard tours and building automation. AxiomXa provides additional options for complex security operations and integration.
For sites with multiple tenancies, a central security office or a requirement to delegate administration while maintaining central oversight, the management model can matter more than the initial number of doors.

RBH Axiom vs Integra32: key differences
| Selection factor | Integra32 | AxiomV / AxiomXa |
|---|---|---|
| Typical project | Small and medium commercial sites, including expandable installations | Large, complex or distributed sites with enterprise management needs |
| Door expansion | Manufacturer comparison lists up to 128 access points for Integra32 R5 | Manufacturer comparison lists larger configurations; capacity is edition and licence dependent |
| Remote management | Web and mobile client options and multi-site capability | Central and delegated local administration across complex multi-site operations |
| Integrations | Video, alarms, visitor management and lift control, subject to configuration | Broader enterprise integration and advanced security-management options |
| Database architecture | Microsoft Access in RBH's R5 comparison | Microsoft SQL Server options, varying by edition |
| Upgrade planning | Documented in-place controller upgrade route to Axiom for supported hardware | Specify software edition, controller firmware and licence requirements for the intended scale |
Specification note: These distinctions describe platform positioning, not guarantees that every listed feature is included in every licence. Verify the current software edition, supported controllers and any paid modules with the supplier.

When does Integra32 make sense?
Consider Integra32 where the project requires reliable access schedules, central cardholder administration, monitored doors and a straightforward operator workflow. It may also suit a modest multi-site installation when its management and reporting model meets the organisation's requirements.
For example, a commercial warehouse with staff entrances, an office door, selected restricted areas and CCTV event verification may not need the broader enterprise functions of Axiom. The installer should still check reader technology, offline controller operation, door hardware, fire interfaces and expected future growth.
When should an integrator specify Axiom?
Examine Axiom where the customer requires large-scale expansion, multiple security operators, central and local control across separate sites, complex alarm responses or extensive integration with other building and security systems.
A hospital campus, industrial estate or multi-building organisation may need different permissions for different operating teams, consolidated event monitoring and advanced reporting. In those cases, software architecture, supportability and operating procedures should be established before controller quantities are finalised.
Can an existing Integra32 system be upgraded to Axiom?
RBH documents an upgrade route from Integra32 to AxiomV, including in-place controller firmware upgrading for applicable hardware. This makes early hardware selection important, but an upgrade should never be assumed to be software-only for every legacy installation.
Before recommending migration, audit the existing controllers, firmware, readers, credential formats, databases, workstation requirements, licences and third-party integrations. Confirm the precise migration path with RBH and plan testing, backups and an agreed changeover window.
Five questions to settle before quoting
- How many doors now and later? Document the anticipated access points, lifts and buildings for the next several years.
- Who administers the system? Determine whether each site needs local control, whether headquarters needs central visibility and how privileges should be separated.
- Which integrations are essential? Record video platforms, intruder alarms, visitor systems, identity directories and building-management interfaces, including exact versions.
- What happens during an outage? Define controller autonomy, server resilience, backup power, event buffering, fire release and emergency egress requirements.
- What is the complete ownership model? Include licensing, server infrastructure, commissioning, training, maintenance and the likely cost of expansion.
What about AxiomCLOUD?
RBH also offers AxiomCLOUD as a separate cloud-managed proposition. If the customer prefers browser-based management without maintaining local application servers, compare that option explicitly rather than assuming it has the same deployment or licensing model as on-premises AxiomV or AxiomXa.
Access control planning for New Zealand projects
Choosing an access platform does not replace opening-by-opening design. Confirm electric locking arrangements, escape routes, fire alarm interfaces, door contacts, request-to-exit devices, network segregation and cybersecurity responsibilities. Life-safety and regulatory requirements should be checked against the applicable New Zealand building and fire design for each premises.
For related design guidance, read How Door Access Control Works and Smart Lock vs Access Control System. Explore RBH Integra hardware, RBH Integra32 software, the RBH Axiom software range and the RBH UNC-500 Axiom controller listed by Essential Security Supplies.
RBH Axiom vs Integra32: frequently asked questions
Can Integra32 controllers be reused when migrating to Axiom?
Some supported Integra32 controllers have a documented in-place upgrade route. Whether a particular controller can be reused depends on its model, hardware revision, firmware, licence and the proposed Axiom edition. Audit the installed equipment and obtain RBH confirmation before promising a migration path.
How many doors can Integra32 manage?
RBH's Integra32 R5 comparison identifies 64 access points in its base configuration and expansion to 128. Confirm the current product edition and licensed capacity when specifying a new installation or upgrading an older one.
Does Axiom need an on-site server?
AxiomV and AxiomXa are server-based platforms with architecture dependent on the edition and deployment. RBH offers AxiomCLOUD separately. Confirm infrastructure, network access, redundancy, data handling and licensing for the exact product proposed.
What should an integrator check before comparing licences?
Compare the complete project requirements: doors, sites, operators, third-party integrations, high availability, reporting, existing controllers and future expansion. Request an edition-specific bill of materials and review ongoing software and support costs with the supplier.
Discuss your RBH project with Essential Security Supplies
Send our team your door schedule, site layout, existing RBH hardware details and integration requirements. We can help identify the questions to resolve before an Integra32, AxiomV or AxiomXa specification is finalised. Contact Essential Security Supplies to discuss your project.