In short
Face recognition is rarely the only system at a door. This page covers how Ayonix joins video management systems, access controllers, turnstiles and business applications, with the event mechanism for each and an honest status: implemented, validated, an integration project, or not supported.
Video management systems
Each page names the specific mechanism, cites the vendor’s own documentation with the date it was read, and states honestly what has and has not been validated.
MIP SDK analytics event protocol
AnalyticsEvent XML delivered to the Event Server on the Analytics Receive port or by HTTP POST, matched against an alarm definition created in the Management Client.
Full integration detail →Primary source
Milestone MIP SDK documentationRead 11 September 2026. The vendor’s documentation is the authority on their platform’s behaviour.
Custom events and event-to-action
A custom event is raised on a match and associated with the camera entity; the customer’s existing event-to-action configuration decides the consequence.
Full integration detail →Primary source
Genetec Security Center documentationRead 11 September 2026. The vendor’s documentation is the authority on their platform’s behaviour.
Nx Metadata SDK plugin
Object and event metadata packets sent to the Nx server, stored against the camera and timeline, and consumed by the Rules Engine.
Full integration detail →Primary source
Network Optix developer documentationRead 11 September 2026. The vendor’s documentation is the authority on their platform’s behaviour.
Everything else
A VMS integration puts a match in front of a person. These put it into a system that acts.
A decision reaches the door controller as a relay closure, an OSDP or Wiegand message, or an API call — whichever the installed hardware speaks. Confirm which before the site survey, not after.
Where an access platform is already the system of record for entitlements, recognition supplies the credential decision and the platform keeps the authorisation model it already has.
A verification result returns to the gate system that owns the passenger interaction and the border decision. Ayonix supplies the face verification component, not the gate or the reader.
Temporary enrolment with an automatic expiry covers contractors and visitors; attendance systems consume the same events rather than needing their own capture.
An HTTP API deployed inside your own environment, callable from any language. Suits several applications served by one deployment.
In-process integration where latency matters or where the video must not leave the application at all. Typically a terminal, a gate or an edge device.
Status
Every integration on this site is described using these four. There is no 'certified' state, because no certification has been verified with any VMS vendor.
| Status | What it means | What it does not mean |
|---|---|---|
| Implemented | Supported: The Ayonix integration performs this, using the vendor’s documented mechanism. | That it has been tested against your specific platform version. |
| Validated | Supported: Tested end to end against a named platform version. | That it is validated for every version. Validation is stated per deployment. |
| Available by integration project | Partial: Achievable through documented interfaces, and not yet built. | That it exists today. It is scoped and quoted as work. |
| Not supported | Not supported: Not on offer, whether by design or because it is not achievable. | That it is impossible in principle — only that Ayonix does not offer it. |
| Certified | Not supported: Deliberately not used anywhere on this site. | Verify certification or marketplace status with the VMS vendor directly. |
Integration work with Network Optix, Milestone and Genetec video management platforms
What this does not establish
Integration capability only. This is NOT a claim of certification, marketplace listing, technology-partner status or joint validation with any of the three vendors. No such status has been verified, and none is asserted anywhere on this site.
XProtect receives analytics events as XML on the Analytics Receive port, default 9090, or by HTTP POST, and matches the EventHeader Message against an alarm definition created in the Management Client
What this does not establish
Describes the documented Milestone protocol. It is not a statement of certification or marketplace status, and the port and prerequisites should be confirmed against the XProtect version in use.
The Nx Metadata SDK exchanges ObjectMetadataPacket and EventMetadataPacket with the Nx server, and the Rules Engine exposes an Analytics Object Detected event
What this does not establish
Describes the documented Nx plugin architecture. Not a statement of certification or marketplace listing.
This site documents three in detail — Milestone XProtect, Genetec Security Center and Network Optix — each on its own page, written from that vendor’s own published documentation and naming the specific mechanism used. Integration with other platforms that expose a documented event or metadata interface is achievable as an integration project; that is stated as an integration project rather than as existing support, which is the honest distinction.
No such status is claimed anywhere on this site. Using a vendor’s public, documented integration interface is a statement about how software works rather than about a commercial or certification relationship. Where certification or marketplace listing matters to a procurement, verify it with that vendor directly rather than inferring it from an integration existing.
A VMS integration puts a match in front of an operator, attached to the video that shows it — the output is attention and evidence. An access control integration sends a decision to a door controller — the output is a physical action. Many deployments need both: the door opens, and the event is visible to the control room with its recorded video. They are separate integration points with separate failure modes.
Yes, through the API and webhooks, or through a direct integration built for the platform. Anything that can consume an HTTP webhook or call an HTTP API can receive recognition events. Where a specific platform integration does not yet exist, it is described honestly as an integration project with a scope and a timeline rather than as something already available.
No. Biometric templates remain in the Ayonix deployment under its own access control, retention and audit configuration. The VMS receives events and metadata. This keeps one governance model for the biometric data rather than splitting it across two systems with different rules, which matters when someone has to demonstrate the data lifecycle to an auditor.
Next step
Tell us the platform, the version and the camera count in scope. The package covers the prerequisites, the event mapping for your naming convention, the configuration to create and the test sequence — before anyone books an engineering visit.