RS2 access control explained after the Access It! 13.0 update

cyber, cool backgrounds, security, crack, crime, windows wallpaper, access, wallpaper 4k, anti, cyberspace, data, design, 4k wallpaper 1920x1080, hd wallpaper, background, wallpaper hd, binary, blue, laptop wallpaper, free background, circuit, desktop backgrounds, closed, code, computer, free wallpaper, concept, connect, digital, firewall, guard, hacker, 4k wallpaper, information, gray computer, mac wallpaper, full hd wallpaper, gray data, gray digital, beautiful wallpaper, gray security, gray information, gray code, gray coding

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 RS2 access control means today

RS2 access control most commonly refers to RS2 Technologies’ Access It! platform, which is now part of Acre Security’s access control portfolio. For security managers, integrators, and facility teams, the practical question is not only what RS2 was, but how Access It! fits into a physical security program in 2026. Public Acre Security release notes list Access It! 13.0.0 on September 14, 2026, with a modernized desktop and web experience and a significantly expanded Web API. That makes RS2 relevant to two audiences: organizations already running Access It! that need an upgrade plan, and buyers comparing established on-premises or hybrid systems with newer cloud-first access platforms.

In short, RS2 remains an enterprise-oriented access control option built around Access It! software, Mercury-based controller architecture, and a dealer or integrator delivery model. It can support small buildings, multi-site systems, and integrations with video, wireless locks, credentials, and other security subsystems. For more background on the category, see our access control coverage.

cyber, hd wallpaper, security, crack, free wallpaper, crime, wallpaper hd, 4k wallpaper 1920x1080, access, anti, cyberspace, data, desktop backgrounds, free background, design, background, wallpaper 4k, binary, blue, circuit, closed, code, computer, concept, connect, digital, firewall, guard, hacker, information, gray computer, cool backgrounds, gray data, gray digital, gray security, laptop wallpaper, gray information, full hd wallpaper, windows wallpaper, gray code, beautiful wallpaper, mac wallpaper, 4k wallpaper, gray coding

RS2 access control timeline and current context

The timeline matters because RS2, Access It!, and Acre Security are often used interchangeably in field conversations. RS2 Technologies was acquired by Acre in April 2019, according to Acre’s own company history. Since then, the Access It! product line has continued within Acre’s broader security portfolio, while many installers and end users still refer to it by the RS2 name.

Date Event Why it matters
April 2019 Acre acquired RS2 Technologies RS2 became part of a larger access control vendor portfolio rather than an independent software maker.
July 4, 2025 The U.S. Department of Veterans Affairs Technical Reference Model listed Access It! Universal.NET as a scalable access control technology available in Standard and Enterprise editions This is a useful public reference for how the platform is described in a government technology catalog, although it is not a product endorsement.
August 20, 2026 Access It! 12.4.2 release notes listed updates including LDAPS support for Data Exchange and controls to prevent multiple operators editing the same record at the same time Recent maintenance releases show attention to directory integration, lockset detail, and operational controls.
September 14-15, 2026 Access It! 13.0 was listed in release notes and Acre product communications described the 13.0 interface refresh The update changes the operator experience while preserving the same underlying platform and workflows.

This context helps avoid mistakes during research and procurement. A search for RS2 access control can surface older RS2-branded documents, current Acre pages, reseller pages, and user discussions. For version-specific decisions, use current Acre release notes and support channels. Treat older RS2 PDFs as background unless they match the version and deployment model in use.

How the platform is typically built

RS2’s Access It! environment is best understood as access control management software sitting above field hardware, credentials, doors, readers, locks, and integrations. Legacy RS2 corporate material describes the system as built around Mercury Security System Control Processors. Mercury-based deployments are common in enterprise access control because they can help separate controller hardware decisions from the head-end software decision. That should not be confused with open-source software or unrestricted interchangeability.

In practice, a deployed RS2 system may include application servers, SQL databases, operator workstations, web clients, Mercury intelligent controllers, downstream modules, readers, credentials, locks, door contacts, request-to-exit devices, power supplies, and network infrastructure. Depending on licensing and system design, it may also connect to video management systems, intrusion panels, wireless locksets, elevator control, badge design, cardholder data exchange, mobile credentials, and reporting tools.

This architecture creates both capability and responsibility. A well-designed system can scale and integrate with many building workflows, but the owner still needs accurate documentation. Door schedules, access levels, card formats, panel firmware, database backups, operator permissions, event retention, and integration dependencies all affect reliability. Many access control failures are not caused by a single product defect. They come from undocumented changes, expired support agreements, unsupported operating systems, weak credential policies, or unclear ownership between IT, facilities, and security.

The delivery model is also important. RS2 historically emphasized a dealer and systems integrator network. That can be valuable for organizations that want professional design, installation, and service. It also means the final outcome depends heavily on the integrator’s access control experience, documentation practices, cybersecurity discipline, and familiarity with the customer’s industry requirements.

What Access It! 13.0 changes

Acre does not describe the Access It! 13.0 update as a separate platform or a ground-up rebuild. Its public product communication says the refresh modernizes the user interface across desktop and web while preserving familiar workflows. That distinction is important for existing RS2 customers: the visible experience changes, but the project should normally be planned as an upgrade to an existing access control environment, not as a rip-and-replace migration by default.

The most visible changes are operational. Acre describes refreshed table grids, cleaner layouts, per-column filtering, search, drag-and-drop grouping, light and dark modes, and a system insights dashboard. These items may sound cosmetic, but operator usability affects response time. A guard or facilities operator who can filter alarms, identify unsecured doors, view system health, and verify a lockdown status more quickly is in a better position to act correctly during a busy shift.

The release notes also state that the Web API has been significantly expanded to expose more platform management capabilities, including hardware, configuration, integrations, users, cardholders, events, and reporting. For enterprise customers, that may be more consequential than the interface refresh. A broader API can support cleaner integration with identity workflows, visitor management, reporting platforms, or internal operations dashboards. However, the presence of an API does not automatically make an integration secure or maintainable. IT and security teams should review authentication, logging, change control, network segmentation, and vendor support before connecting production access control to business systems.

Access It! 13.0 should therefore be evaluated in two layers. The first is operator efficiency: can daily tasks such as onboarding, alarm review, lockdown confirmation, and cardholder searches be completed with fewer errors? The second is system governance: does the expanded interface and API surface improve visibility without creating unmanaged administrative access?

Evaluation criteria for existing and new sites

For existing RS2 customers, the main decision is usually upgrade timing and readiness. If the system is stable but several versions behind, moving directly to a newer release may require more planning than a routine patch. Review the current Access It! version, server operating system, SQL Server version, controller firmware, workstation dependencies, integrations, and support status before scheduling an upgrade window. See also: Alarm and Detection.

For new projects, the question is broader. RS2 access control may fit organizations that prefer an established, integrator-supported platform, need on-premises control, use Mercury-based field hardware, or require integration with existing physical security systems. It may be less attractive for teams that want a purely self-service cloud product, minimal local infrastructure, or an access control model managed entirely through a browser without traditional server components.

Buyers should avoid reducing the decision to a brand comparison. A stronger evaluation starts with operational requirements:

  • How many doors, sites, operators, and cardholders must be supported over the next five years?
  • Does the organization require on-premises hosting, cloud hosting, or a hybrid approach?
  • Which credentials are planned, such as proximity cards, smart cards, mobile credentials, or multi-technology readers?
  • Will the system integrate with video, visitor management, HR directories, identity systems, elevators, wireless locks, or intrusion detection?
  • Who will own database backups, server patching, cybersecurity review, credential policy, and user deprovisioning?
  • Is the integrator certified and experienced with the exact version, controller family, and integration scope?

These questions often show whether a system is a good match before price discussions begin. A low software price can become expensive if the design requires custom work, unclear support, or hardware replacement. Conversely, a platform with a higher initial project cost may be justified if it reduces future migration risk and supports existing field devices.

Upgrade and migration checklist

Whether an organization plans to keep RS2, upgrade Access It!, or compare alternatives, the first step is to build a factual system inventory. This inventory should be completed before vendor demos or budget approval because it defines the real scope of work.

  1. Document the current version. Record the Access It! version, license type, modules, support agreement status, server names, operating systems, SQL instance, and workstation count.
  2. Export a door and hardware list. Include doors, readers, panels, downstream modules, locks, inputs, outputs, elevators, alarm points, and any offline or wireless locksets.
  3. Map credentials and card formats. Identify card technologies, facility codes, mobile credential use, PIN policies, biometric integrations, and any legacy formats that should be retired.
  4. Review integrations. List video management, visitor management, HR data exchange, LDAP or LDAPS, intrusion, badging, reporting, and custom API connections.
  5. Validate backups and recovery. Confirm database backups, event database retention, configuration exports, server images, and restoration procedures.
  6. Check cybersecurity controls. Review operator permissions, password rules, directory authentication, network segmentation, firewall rules, remote access practices, and audit logs.
  7. Plan a test window. Use a staging environment or controlled pilot when possible, especially if moving across major versions or changing server infrastructure.

A migration away from RS2 requires a different level of analysis. Mercury-based hardware may reduce some replacement costs in certain scenarios, but hardware reuse depends on controller models, firmware, licensing, reader compatibility, card formats, the destination platform, and integrator access. Treat hardware reuse as a design assumption that must be verified, not as a guaranteed benefit.

Scenario Primary risk Practical next step
Upgrade within Access It! Version gaps, server compatibility, integration breakage Review release notes, back up databases, and test critical workflows before production rollout.
Move servers or SQL database Downtime, failed restore, workstation connection issues Document service accounts, database paths, firewall rules, and rollback steps.
Replace software but keep controllers Firmware, licensing, and platform compatibility uncertainty Have both the current and future integrators verify controller models and conversion requirements.
Replace readers or credentials Cardholder disruption and access denial Run a credential transition plan with temporary overlap and clear enrollment procedures.

Frequently asked questions

Is RS2 the same as Access It!

In most current access control conversations, RS2 refers to RS2 Technologies and its Access It! software line. Acre acquired RS2 in 2019, so current product information and support references may appear under Acre Security while field teams still use the RS2 name.

Is RS2 access control cloud-based or on-premises

RS2’s Access It! ecosystem has been associated with on-premises, web client, and SaaS-related options in public product material. The correct answer for a specific site depends on the edition, license, hosting model, and integrator design. Buyers should confirm deployment architecture in writing rather than assuming a product name defines the hosting model.

What is the main value of Access It! 13.0

The main value is a modernized operator experience and expanded Web API coverage while preserving the same Access It! platform foundation. For many organizations, the benefit will come from easier searching, filtering, alarm handling, system status visibility, and better integration possibilities.

Can an organization keep existing Mercury controllers if it leaves RS2

Sometimes this may be possible, but it is not automatic. Controller model, firmware, licensing, reader wiring, credential formats, and the target software platform all matter. Any reuse plan should be verified by qualified integrators before budgets are finalized.

What should security teams ask before upgrading RS2

Ask for a version-specific upgrade path, supported server and SQL requirements, controller firmware impact, integration testing plan, backup and rollback process, expected downtime, operator training needs, and post-upgrade validation checklist. Those answers are more important than a generic product brochure.