Software upgrade for the access control you already own For integrators[email protected]
GateStride

Systems / Hirsch Velocity

Hirsch Velocity: versions, Mx controllers, end of life and upgrade options

Hirsch (formerly Identiv's physical security business)GateStride: Not yet scheduledReviewed October 2026

By Tom Jin

Velocity is the on-premise access control software from Hirsch. It was long sold under the Identiv name, until Identiv completed the sale of its physical security business to Hawk Acquisition, Inc., a subsidiary of Vitaprotech SAS, on September 6, 2024, for $145.0 million. The business now trades as Hirsch, part of the Hirsch Group based in Lyon.

Velocity is strong in federal and high-security sites. The current release, Velocity 3.9, was released on September 4, 2025, with TLS 1.3 and FIPS 140-3 support and an integration with the Velocity Vision video management system. An earlier release, 3.8.6, was approved for the GSA Approved Products List. Velocity runs Hirsch's own Mx controllers rather than Mercury boards. Hirsch also sells a separate, IT-centric line called Primis and a cloud option, Velocity Cirrus, which are different products from Velocity.

How to recognise Hirsch Velocity

Look for the Velocity client on the security workstation, with Hirsch or older Identiv branding. In the comms room, controllers are Hirsch Mx units or, on older sites, DIGI*TRAC controllers such as the M2, M8 or MSP. If the controllers say Primis or EG-2, you are on Hirsch's other product line, not Velocity.

  • The software is called Velocity; older screens and manuals may carry the Identiv name.
  • Current controllers are Mx-1, Mx-1-ME, Mx-2, Mx-4 and Mx-8 (for example Mx-8-S3OB or Mx-8-N3).
  • Older sites may still have DIGI*TRAC M2, M8 or MSP controllers (model codes such as M2N, M8N, MSPN).
  • Readers connect using Hirsch's MATCH interface, Wiegand or OSDP.

Still not sure? Follow how to identify your access control system.

Versions and editions

NameDetailsStatusSource
Velocity 3.9Released September 4, 2025. TLS 1.3, FIPS 140-3, Velocity Vision VMS integration.currentsource
Velocity 3.8.6Earlier release, approved for the GSA Approved Products List. Release notes are public.legacysource
Velocity CentralUnified monitoring hub, previewed March 27, 2025.currentsource
Velocity VisionHirsch's video management system; version 6.2 documents are published.currentsource
Older Velocity releases (before 3.8)Support end dates were not confirmed; Hirsch's support portal requires a login.unconfirmedsource

Hardware

NameDetailsStatusSource
Mx-8-S3OB, Mx-8-N38-door controllers with the SNIB3 board. Up to 500,000 credentials with SNIB3. Proprietary X*NET2/X*NET3 protocol; MATCH, Wiegand and OSDP readers. Not Mercury.currentsource
Mx-2, Mx-4Expandable to 8 doors.currentsource
Mx-1, Mx-1-MESingle-door PoE+ controllers.currentsource
SNIB3Network interface board used in Mx controllers.currentsource
DIGI*TRAC M2, M8, MSP (M2N, M8N, MSPN and others)End of sale December 15, 2017 (announced April 27, 2017); last ship December 31, 2017. Replaced by Mx-2 and Mx-8.end of salesource

What is ending, and when

The dated notice is for the older controllers. Hirsch (then Identiv) ended sale of the DIGI*TRAC M2, M8 and MSP families on December 15, 2017, with last shipments on December 31, 2017, and named the Mx-2 and Mx-8 as replacements. If your site still runs DIGI*TRAC hardware, it has been off sale for years, and spare parts are the main risk. We did not find a published end-of-support date for those controllers.

We found no end-of-life notice for Velocity itself; 3.9 is current. The 2024 change of ownership from Identiv to Vitaprotech did not retire the product, and Hirsch has continued to release Velocity versions since. Check that your Velocity release supports the Mx models you plan to buy.

See every dated notice in the end-of-life tracker.

What offices commonly miss

  • Exits are usually free: people push a bar or trip a request-to-exit sensor. The system logs a door opening but not who left, so it cannot give an exit record or live occupancy unless exits are badged.
  • Hardware is Hirsch-only. Mx controllers use Hirsch's own protocols and are not Mercury boards, so other platforms cannot simply take them over.
  • Federal and FICAM sites are slow to change. Any add-on usually needs approval against the site's compliance requirements, which takes time.
  • Primis and Velocity Cirrus are separate Hirsch products. Do not assume a feature or integration for one applies to Velocity.

Integration options

Hirsch publishes three integration surfaces for Velocity: a .NET SDK, Velocity Web Services (with public release notes for the Velocity Web Services Client, including versions 3.8.0.920 and 3.8.6) and URL Triggers. Full SDK manuals sit behind Hirsch's support portal login.

Because Mx controllers are proprietary, every integration goes through Velocity rather than to the panels. For federal sites, an integration also has to fit the site's security accreditation, which is a separate approval from the technical work.

Upgrade paths

Keep Velocity and add features as software

If the doors and Mx controllers work, keep them. Missing features could come from software connected through Velocity Web Services or the SDK, subject to Hirsch's terms and the site's compliance approval.

Update to 3.9 and replace DIGI*TRAC

Move to Velocity 3.9 for TLS 1.3 and FIPS 140-3, and replace any DIGI*TRAC M2, M8 or MSP controllers with the Mx-2 or Mx-8 that Hirsch named as replacements. Doors, wiring and cardholders typically stay.

Full replacement

Moving off Velocity means new controllers, because Mx hardware runs only on Hirsch software. For regulated sites, factor in re-approval time and cost, not only hardware.

Compare the routes over three years in the savings calculator.

GateStride and Hirsch Velocity

Not yet scheduled GateStride has not scheduled a Hirsch Velocity integration. It is not on our roadmap yet, and we do not support Velocity today. GateStride is in early access and currently works with Kantech EntraPass. If your office runs Velocity, tell us your version and door count. Demand decides what we build next, and we will only call an integration Verified after testing it ourselves on a live system.

Full compatibility list · Tell us you run Hirsch Velocity

Questions about Hirsch Velocity

Is Identiv Velocity still supported?
Yes. Identiv sold its physical security business to a Vitaprotech subsidiary on September 6, 2024, and it now trades as Hirsch. Hirsch released Velocity 3.9 on September 4, 2025. Older releases may be out of support, so check your version with Hirsch or your installer.
Are DIGI*TRAC controllers end of life?
They are end of sale. Hirsch ended sale of the DIGI*TRAC M2, M8 and MSP families on December 15, 2017, with last shipments on December 31, 2017, and named Mx-2 and Mx-8 as replacements. We did not find a published end-of-support date.
Does Velocity use Mercury controllers?
No. Velocity runs Hirsch's own Mx controllers, which use the proprietary X*NET2 and X*NET3 protocols with MATCH, Wiegand and OSDP readers. That means hardware refreshes stay within Hirsch's range, and a move to another platform usually needs new controllers.
Does Velocity have an API?
Hirsch offers a .NET SDK, Velocity Web Services and URL Triggers. Release notes for the Velocity Web Services Client are public, while the full manuals sit behind Hirsch's support portal. Federal sites also need any integration approved against their compliance requirements.

Related systems: AMAG Symmetry · Gallagher Command Centre

Sources

Last reviewed October 2026. Hirsch Velocity and other product names are trademarks of their respective owners. GateStride is independent and not affiliated with, endorsed by or a dealer for any manufacturer.