Key takeaways
- TDSi by Hirsch released GARDiS 3.3 on August 10, 2026, according to the manufacturer.
- The update integrates Ajax Cloud intruder functions into GARDiS, including monitoring and authorized arm, disarm and bypass actions.
- A universal Card or Fob type is intended to consolidate credential administration and migrates existing credentials during upgrade.
- New controls cover password rules, account lockout, event-dashboard access, organization-based filtering and report visibility.
- Installers should validate integration licensing, network paths, controller outputs and upgrade behavior before deploying the release at live sites.
Release confirmed; reported date corrected
TDSi by Hirsch has released GARDiS 3.3, an update to its access-control and integrated-security software. The manufacturer dated its release announcement August 10, 2026. That is the supported event date, rather than the August 31 date in the candidate record. Independent industry coverage later described the same release and feature set. ([tdsi.co.uk](https://tdsi.co.uk/news/tdsi-by-hirsch-releases-gardis-version-3-3))
The release centers on three operational areas: an Ajax Cloud intruder integration, a revised credential data model, and expanded administration controls for accounts, events and reports. For organizations already standardizing on GARDiS, the update is principally an administration and workflow release rather than a newly announced controller platform. ([tdsi.co.uk](https://tdsi.co.uk/news/tdsi-by-hirsch-releases-gardis-version-3-3))
Ajax Cloud brings intrusion tasks into the GARDiS workflow
With the Ajax Cloud intruder integration, authorized GARDiS users can discover and view Ajax hubs, devices and groups in the access-control application. TDSi says operators can monitor status changes and carry out arm, disarm and bypass-management actions without moving between separate interfaces. Ajax panels, zones and groups can also be used in GARDiS Cause & Effect rules. ([tdsi.co.uk](https://tdsi.co.uk/news/tdsi-by-hirsch-releases-gardis-version-3-3))
This may be useful where security teams want access events and intrusion-state information available to the same operator. It does not eliminate the need to define alarm-response responsibility, user authorization and testing procedures. Integrators should verify which Ajax Cloud account, devices, permissions and network connectivity are required for the intended workflow before commissioning the integration.
For applications without a direct intruder-panel integration, TDSi says GARDiS controller outputs can provide a basic connection to an intruder panel. That option should be engineered as a discrete I/O interface: installers should document the input/output logic, fail-safe behavior, supervision requirements and responsibility for alarm signaling rather than treating it as equivalent to a full software integration. ([tdsi.co.uk](https://tdsi.co.uk/news/tdsi-by-hirsch-releases-gardis-version-3-3))
Credential administration is consolidated
GARDiS 3.3 introduces a universal “Card or Fob” credential type designed to work across virtually all reader and card technologies supported by the platform. The purpose is to remove the administrator task of matching each credential to a particular decode type. TDSi also says its upgrade process automatically migrates existing credentials and permits verification before changes are applied. ([tdsi.co.uk](https://tdsi.co.uk/news/tdsi-by-hirsch-releases-gardis-version-3-3))
The revised model also encompasses biometric credentials and IP-lock whitelisting, according to TDSi. For sites with mixed legacy reader estates, the potential benefit is a less fragmented enrollment process. However, a universal software object should not be mistaken for universal field compatibility. Project teams still need to inventory credential formats, bit lengths, facility-code handling, reader configuration and controller decoding before an upgrade. ([tdsi.co.uk](https://tdsi.co.uk/news/tdsi-by-hirsch-releases-gardis-version-3-3))
Governance features target delegated administration
The update adds configurable password-strength requirements, banned-word lists and automatic account lockout. It also expands role and permission checks, lets administrators control who can view the events dashboard, and supports restricting event information by organization. Saved reports can remain private to their owner or be shared with selected users. ([tdsi.co.uk](https://tdsi.co.uk/products/gardis-pro-software/))
Those features are relevant to deployments in which facilities, departments or tenant organizations need separate visibility into people and events. In practice, the value will depend on role design: security administrators should map operator roles, report ownership, organization boundaries and exception-handling processes before activating broad delegated access. This is an implementation consideration based on the capabilities announced by TDSi. ([tdsi.co.uk](https://tdsi.co.uk/news/tdsi-by-hirsch-releases-gardis-version-3-3))
Compatibility and upgrade checks for installers
TDSi lists additional 3.3 changes including the latest STid V3 mobile credential API, support for 32-bit Wiegand readers and credentials, OSDP readers configured as In/Out readers, simplified Chinese as an interface-language option, and performance improvements for bulk database updates and message-queue handling. ([tdsi.co.uk](https://tdsi.co.uk/news/tdsi-by-hirsch-releases-gardis-version-3-3))
Before moving a production site to GARDiS 3.3, integrators should take a verified backup, review release documentation and test the credential migration on a representative system. They should also confirm licensing for any optional integration, validate Ajax Cloud connectivity and permissions, test Cause & Effect logic under normal and alarm conditions, and recheck reader behavior where Wiegand, OSDP or mobile credentials are in use. TDSi’s product page identifies Ajax Cloud intruder integration and other third-party capabilities within its GARDiS Pro software offering. ([tdsi.co.uk](https://tdsi.co.uk/products/gardis-pro-software/))