How Aregnum Works With Compatible Systems
Summary: Estates often assume adopting a platform means replacing their access hardware. This article looks at how Aregnum works with compatible access systems.
Estates considering a management platform often assume it will mean replacing their access hardware, which is a costly and off-putting prospect. The assumption is that the platform will require its own hardware, so the estate’s existing gates, readers and controllers would have to go. But this is not how Aregnum works, because its standard approach integrates with compatible access systems rather than requiring wholesale replacement. Understanding this removes a major worry, because adopting the platform need not mean replacing the estate’s access hardware.
The standard path integrates with ZKBio CVSecurity-compatible hardware, so compatible systems are worked with, not replaced. Where an estate’s access hardware is ZKBio CVSecurity-compatible, Aregnum integrates with it through its standard approach, so the estate uses its existing compatible hardware with the platform. This means the estate does not have to replace compatible hardware, because the platform works with it, which removes the cost and disruption of wholesale replacement.
The integration is what connects the estate’s access to the platform, giving centralised management without new hardware. Through the integration, the estate’s compatible access hardware is managed through the platform, so the estate gains centralised access management using the hardware it already has. This is the benefit of integration over replacement: the estate gets the platform’s management of its access without the expense of replacing the hardware that already works.
Where custom integration is needed, there is an API-based path, though it has its own requirements. For hardware that is not on the standard compatible path, Aregnum offers a custom, API-based approach, which is more involved and requires the necessary API documentation, but still aims to work with the estate’s setup rather than assuming replacement. This means even non-standard setups are approached with a view to integration where feasible, though the standard compatible path is the smoothest.
The installer’s test confirms the integration works before go-live, so the estate has assurance. As part of setting up, the installer confirms that the gate or door opens from the app, verifying the integration before the estate relies on it. This test gives the estate assurance that its access hardware works with the platform as intended, so the integration is confirmed rather than assumed, which supports a confident go-live.
It is worth being clear that the compatible, standard path is the smoothest and most common route, which is reassuring for most estates. Many estates find their access hardware is ZKBio CVSecurity-compatible or can be, so the standard integration path applies and no replacement is needed, which is the straightforward case. Because this compatible path is the norm rather than the exception, most estates approaching the platform find that their hardware can be worked with rather than replaced, so the worry about wholesale hardware replacement, while understandable, turns out to be unfounded for the majority, whose existing compatible hardware integrates with the platform through the standard approach.
Adopting Aregnum need not mean replacing the estate’s access hardware, because the standard approach integrates with ZKBio CVSecurity-compatible systems rather than requiring wholesale replacement. The estate gains centralised access management using its existing compatible hardware, with a custom API-based path where needed and an installer test to confirm the integration. For an estate worried about the cost of replacing its hardware, the reassurance is that the platform works with compatible systems, so adopting it need not carry the expense and disruption of replacing the access hardware the estate already has.
Frequently Asked Questions
Does adopting a platform mean replacing our access hardware?
Not with Aregnum’s standard approach, which integrates with ZKBio CVSecurity-compatible hardware rather than requiring wholesale replacement. Where an estate’s hardware is compatible, the estate uses its existing hardware with the platform, removing the cost of replacement.
What does the integration give us?
Through the integration, the estate’s compatible access hardware is managed through the platform, so the estate gains centralised access management using the hardware it already has, getting the platform’s management of its access without the expense of replacing working hardware.
What if our hardware isn’t on the standard path?
For hardware not on the standard compatible path, Aregnum offers a custom, API-based approach, which is more involved and requires the necessary API documentation, but still aims to work with the estate’s setup rather than assuming replacement.
How do we know the integration works?
As part of setting up, the installer confirms that the gate or door opens from the app, verifying the integration before the estate relies on it, so the integration is confirmed rather than assumed, supporting a confident go-live.
See Aregnum in action
Ready to turn your community into an effortless, secure haven? Book a demo and we will show you how Aregnum fits your property.