Specifications
The following table lists the minimum requirements for the Community Server and Community Workstation. Ancillary recommendations are listed at the end of the table.¹
A dedicated server is recommended but not required.
Requirement |
Server Small ≤ 500 Access Points |
Server Medium 500-2K Access Points |
Server Large >2K Access Points |
Community Workstation |
| CPU² | 2GHz/Intel x64-bit/4-core | 2GHz/Intel x64-bit/8 core | 2GHz/Intel x64-bit/16 core | 2GHz/Intel 64-bit/dual core |
| RAM | 16 GB or more | 16 GB or more | 32 GB or more | 8 GB |
| Disk Drive Free Space³ | 30 GB | 60 GB | 100 GB | 50 MB |
| Network Controller | Gigabit Ethernet - 1Gb/Second | Gigabit Ethernet - 1Gb/Second | Gigabit Ethernet - 1Gb/Second | Gigabit Ethernet - 1Gb/Second |
| USB 2.0 Port | Required to connect encoder | Required to connect encoder | Required to connect encoder | Required to Connect Encoder |
| Operating System⁴ |
MS Windows Server 2025/2022/2019 standard Microsoft Windows 11 Pro/Enterprise⁵ |
MS Windows Server 2025/2022/2019 standard | MS Windows Server 2025/2022/2019 standard | Microsoft Windows 11 Pro/Enterprise⁵ |
| Note: Windows 11 Pro/Enterprise do not support Remote Lock Management due to Microsoft limitations on the number of concurrent network connections. | ||||
| .NET Framework | 8.0.21.25475 | 8.0.21.25475 | 8.0.21.25475 | N/A |
| Database⁶ |
SQL Server Express 2022/2019/2017 SQL Server 2022/2019/2016 |
SQL Server Express 2022/2019/2017 SQL Server 2022/2019/2016 |
SQL Server Express 2022/2019/2017 SQL Server 2022/2019/2016 |
N/A |
| Web Browser7 |
Google Chrome (latest) Microsoft Edge (latest) |
Google Chrome (latest) Microsoft Edge (latest) |
Google Chrome (latest) Microsoft Edge (latest) |
Google Chrome (latest) Microsoft Edge (latest) |
¹Additional recommended hardware for the Community Server includes: UPS Backup, Integration HD Graphics Card, Keyboard/Mouse
²Supported CPUs: Intel and AMDx64. Additional free space may be required depending on database backup and archiving settings.
³Additional free space may be required depending on database backup and data retention settings.
⁴Community is localized for all supported operating systems. Languages: English, French. Note that browser language settings may affect on-screen
text.
⁵ TPM (Trusted Platform Module) 2.0 is required to run Windows 11.
⁶a)SQL Server Express 2022 is bundled with Community and can be selected to install during installation. b) IMPORTANT: For security reasons, dormakaba strongly recommends SQL Server 2022 (or SQL Server Express 2022). c)IMPORTANT: Due to SQL Server Express limitations, dormakaba recommends SQL Server Standard for medium and large deployments. For details, consult Microsoft documentation. d)For larger deployments, dormakaba recommends using a dedicated server for the Community database. e)Microsoft reports issues that prevent SQL Server from installing successfully on a Domain Controller. Avoid installing SQL Server on a Domain Controller.
⁷Recommended Web Browser resolution: 1366x768 or greater.
Port Exceptions
| Port | Outbound Port | Protocol | Description |
| 80/443 | HTTP/S | Community Web User Interface | |
| 8083/443 | HTTP/S | Community API | |
| 28000/28001 | TCP | KABA RFID IP Encoder I (28000)/dormakaba RFID Encoder II(28001, required for enhanced security mode) | |
| 27700 | 27001 | TCP | ONLINE - Gateway I, Control 4 (277012 is the listening port on the hardware) |
| 28002 | TCP | ONLINE Gateway II, RAC5-MFC/XT | |
| 232111 | TCP | ONLINE - INNCOM (23211 is the listening port on the INNCOM server) | |
| 123 | 123 | UDP | Open inbound and outbound access on UDP port 123 so that NTP (network time protocol) traffic is allowed and consistently reachable from the locks/gateways. |
| 40100 | HTTP/S | Community Client and Maintenance Unit. No firewall rule required. This port is not exposed to external computer; it is local host only. |
RFID Keys
The following table shows the RFID Key Types that the Community software supports.
| Key Type | Enhanced Key Security | Standard Key Security | Legacy Key Security |
| MIFARE DESFire EV2/EV3 | ✔ | ✔ | not supported |
| dormakaba RFID ComID Cards/Fobs | ✔ | ✔ | not supported |
| MIFARE Plus | ✔ | not supported | ✔ |
| MIFARE Ultralight C | ✔ | ✔ | not supported |
Encoders
| Encoder Type | Latest FW | Supported Key Types |
| dormakaba RFID Encoder I (part 064-514822 or 74750) Not supported when enhanced security mode enabled. |
1.015 | MIFARE Plus MIFARE Ultralight C |
| dormakaba RFID ENCODER II (part 75720) Required when Enhanced Security Mode Enabled |
3.002 Applet Ver 1.003 |
MIFARE DESFire EV2/EV3 MIFARE Plus MIFARE Ultralight C |
| Encoders shipped before Sept 2022 may not have the applet version required for enhanced key security. For more information, contact dormakaba technical support. | ||
Maintenance Units
| Programmer Type | Latest Supported FW | Minimum FW for Enhanced Security |
| M-Unit SAFLOK HH6 | 1.53 | Not supported |
| M-Unit SAFLOCK HH6 NFC (Required when Enhanced Security Mode Enabled) |
2.46 | 2.40 |
Locks
The following table lists supported locks and the latest firmware versions. The BLE Version for all locks is 1.3.1.0
| Lock Profile | Boot&Main |
Supported Readers |
Supported Key Types | BLE | Zigbee AVR |
| Use with Enhanced, Standard, and Legacy Security | |||||
| Confidant NFC | 03.24.25.4 | Integrated Reader | MIFARE DESFire EV2/EV3 MIFARE Plus MIFARE Ultralight C |
1.3.1.0 | 1.10x 5.13x 6.05x |
| MT4/Quantum (secure boot) |
07.22.25.4 | Quantum (secure boot): 08.12.25.5 | MIFARE Plus MIFARE Ultralight C |
1.3.1.0 | 1.10x 5.13x 6.05x |
| Quantum MT6 (secure boot) | 06.06.25.4 | LEGIC | MIFARE DESFire EV2/EV3 MIFARE Plus MIFARE Ultralight C |
4.0.0.0 | 1.10x 5.13x 6.05x |
| Pixel+ | 06.06.25.4 | LEGIC | MIFARE DESFire EV2/EV3 MIFARE Plus MIFARE Ultralight C |
4.0.0.0 |
1.10x 5.13x 6.05x |
| Pixel | 07.22.25.4 | Quantum (secure boot): 08.12.25.5 | MIFARE Plus MIFARE Ultralight C |
1.3.1.0 | 1.10x 5.13x 6.05x |
| Nova | 03.24.25.4 | integrated reader | MIFARE DESFire EV2/EV3 MIFARE Plus MIFARE Ultralight C |
1.3.1.0 |
1.10X 5.13X |
| RAC5 XT/Lite (hardware for common areas) |
03.18.25.4 (main only) | SRK (NFC Wall) reader: V_03.31.25.3 | MIFARE DESFire EV2/EV3 MIFARE Plus MIFARE Ultralight C |
1.3.1.0 | N/A |
| RCU4 | 07.22.25.4 | SR Wall Reader: 07.22.25.4 | MIFARE DESFire EV2/EV3 MIFARE Plus MIFARE Ultralight C |
1.3.1.0 | 1.10x, 5.13x, 6.05x |
| RT+ | 03.24.25.4 | Integrated reader | MIFARE DESFire EV2/EV3 MIFARE Plus MIFARE Ultralight C |
1.3.1.0 | 1.10x, 5.13x, 6.05x |
| Saffire LXD | 03.24.25.4 | Integrated reader | MIFARE DESFire EV2/EV3 MIFARE Plus MIFARE Ultralight C |
1.3.1.0 | 1.10X 5.13x |
| SRK (Secure Reader Keyscan) |
09.19.25.3 | LEGIC | MIFARE DESFire EV2/EV3 MIFARE Plus MIFARE Ultralight C |
1.3.1.0 |
1.10x, 5.13x, 6.05x |
| Use with Standard and Legacy Security | |||||
| Confidant | 09.03.19.2 | Integrated reader | MIFARE Plus MIFARE Ultralight C |
1.3.1.0 | 1.10X 5.13x |
| MT4/Quantum | 08.03.21.4 | Quantum (secure boot): 02.06.19.1 | MIFARE Plus MIFARE Ultralight C |
1.3.1.0 | 1.10x, 5.13x, 6.05x |
| RT | 06.14.18.2 | Integrated Reader | MIFARE Plus MIFARE Ultralight C |
1.3.1.0 | 1.10x, 5.13x, 6.05x |
Elevator Controllers
| Boot&Main | Supported Readers | Supported Key Types | BLE | ZigBee AVR | |
| Enhanced, Standard and Legacy Security | |||||
| ECU/RCU4 | 07.22.25.4 | Quantum (secure boot): 08.12.25.5 | MIFARE Plus MIFARE Ultralight C |
1.3.1.0 | 1.10x |
| RAC5-MFC | 03.18.25.4 | NFC Wall Reader: V_03.31.25.3 | MIFARE DESFire EV2/EV3 MIFARE Plus MIFARE Ultralight C |
1.3.1.0 | N/A |
| Standard and Legacy Security | |||||
| ECU/RCU4 | 08.03.21.4 | Quantum (secure boot): 02.06.19.1 | MIFARE Plus MIFARE Ultralight C |
1.3.1.0 | 1.10x |
| Legacy MFC | 0.017 (Main Only) | Integrated Reader | MIFARE Plus MIFARE Ultralight C |
1.3.1.0 | N/A |
| EMCC | 20090929 (Main Only) | Integrated Reader | MIFARE Plus MIFARE Ultralight C |
1.3.1.0 | N/A |
| MCC 8/12 | 0.031398 (Main Only) | Integrated Reader | MIFARE Plus MIFARE Ultralight C |
1.3.1.0 | N/A |
ZigBee Gateway
| Boot | BLE | ZigBee | |
| GWY I | 0.221 | N/A | 1.10x/5.13x |
| GWYII | 0.022 | N/A | 6.05x |
Interface Requirements
Community Supports the Following:
- Aurora SDK - v1.0.19 to v1.0.25
NOTE: For sites with Aurora integrations, verify that the User Type is set to “Master” for the Community system user created in Aurora, per the Aurora Integration Manual. Other User Types will no longer work with Community
2.4
.
For Aurora integrations, the following requirements apply when the Community license includes Visitor Management:
- Enable Extended PIN (7-digit), (Application)
- Enable Auto Generate PIN
- Enable Keyscan Credentials for Extended Card Format
- Enable KABA Integrated Mode
- Enable Auto Expiry mode
- Enable Card Count on ACUs
- Per ACU, select reader mode S - KABA Integration
For details, refer to the Community Aurora Integration Deployment and Support Manual (PK3769).
Online Communication Interfaces and Devices
|
Gateway I Device support with |
Gateway II Device supported with |
Rx-Link supported with |
RAC5-MFC/XT supported with |
|
| Gateway I Device | ✔ | not supported | not supported | ✔ |
| Gateway II Device | not supported | ✔ | ✔ | ✔ |
| Rx-Link | not supported | ✔ | ✔ | ✔ |
| RAC5-MFC | ✔ | ✔ | ✔ | ✔ |
| RAC XT | ✔ | ✔ | ✔ | ✔ |
| Legacy MFC | ✔ | not supported | not supported | not supported |
| Third Party Interfaces (Mutually Exclusive) | ||||
| INNCOM® | ✔ | ✔ | ✔ | ✔ |
| INTEREL® | ✔ | not supported | not supported | not supported |
| Telkonet® | ✔ | not supported | not supported | not supported |
| Telkonet® Rhapsody | not supported |
not supported |
✔ |
not supported |
| Control4® | ✔ | not supported | not supported | not supported |
Online Communication Lock Support
|
Gateway I / Legacy 3rd-Party Interfaces (Zigbee Gen I) |
Gateway II / Rx-Link | ||
| Zigbee Gen II Phase 1 | Zigbee Gen II Phase 2 | ||
| Pixel | ✔ | ✔ | ✔ |
| Pixel+ | ✔ | ✔ | ✔ |
| MT4 | ✔ | ✔ | ✔ |
| MT6 | ✔ | ✔ | ✔ |
| RCU4 | ✔ | ✔ | ✔ |
| RT | ✔ | ✔ | not supported |
| RT+ | ✔ | ✔ | ✔ |
| Saffire LX | ✔ | ✔ | ✔ |
| Nova | ✔ | ✔ | ✔ |
| Confidant | ✔ | ✔ | not supported |
| Confidant NFC | ✔ | ✔ | ✔ |
No Touring Requirements
To use the Community No Touring feature, the following requirements must be met:
- MT/RCU Series locks must be installed at Residence Common Areas
- The locks must be updated to the latest firmware.
- The M-Unity (HH6) must be updated to the latest firmware.
File Downloads
| File ID | Description | Last Update |
| PK3695 | Community Installation Guide V 2.5.0.0 | 01/2026 |
| PK3706 | Community Guide V 2.5.0.0 | 01/2026 |
| PK3769 | Community Release Notes V 2.5.0.0 | 01/2026 |
| PK3776 | 10/2025 | |
Links to YouTube How-To Videos
- Community Software - Common Access Area Management
- Community Software - Access Point Scheduling
- Community Software - System Settings
- Community Software - Access Management
- Community Software - Resident Visitor Management
- Community Software - Staff and Vendor Keys
- Community Software - Staff and Vendor Management
- Community Software - Property Builder
- How to change the IP Address for the dormakaba Community Software - Client and Server