Skip to content
Readers outlive credentials. That is the whole of the problem, and it is why a standard published in February matters to a purchase order signed in August.
A mobile credential platform can be changed in a licensing cycle. A reader estate installed across forty doors, cabled, commissioned and certified, is there for a decade. Which means the decision you make about readers this year quietly determines what credentials you can use until the middle of the next.
What Aliro is
Aliro 1.0 was released by the Connectivity Standards Alliance in February 2026. Its founder members include Apple, Google, Samsung, HID, ASSA ABLOY, Allegion and dormakaba, which is an unusually broad coalition of device manufacturers and access control vendors agreeing on the same thing at the same time.
Technically, it uses NFC or Bluetooth Low Energy with ultra-wideband, and is built on public key infrastructure with mutual authentication between reader and device. It supports offline credential sharing and revocation, which addresses one of the persistent weaknesses of cloud-dependent mobile credential systems.
Commercially, it is an attempt to end vendor lock-in at the credential layer. Until now, choosing mobile credentials has meant choosing a vendor’s ecosystem: readers, credentials and management platform arriving as a bundle, with moving later meaning replacing all three.
What it does not change
It does not make your current platform obsolete. A well-implemented mobile credential deployment on a vendor platform is a good system today and will remain one.
It does not oblige anyone to support it. Founder membership signals intent, not shipped product. Some vendors will implement early and thoroughly, some will implement partially, and some will support it on new hardware only.
It is not a reason to stop a project. If you have an unencrypted credential estate running MIFARE Classic or 125 kHz proximity, waiting for an open standard while your cards remain trivially cloneable is the wrong trade. Fix the exposure now.
What it does change
The question you should be asking suppliers this year is no longer just “does this support mobile credentials”. It is “what is your Aliro position, on which hardware, and on what timeline”.
That question does three useful things. It reveals which vendors have a genuine roadmap and which have a press release. It gives you a basis for negotiating firmware upgrade commitments into the contract rather than hoping for them. And it separates hardware that will still be relevant in 2032 from hardware that will be a replacement programme in 2029.
The practical position for a buyer in 2026
- If you are replacing readers this year, ask for Aliro capability or a documented firmware upgrade path, and get the answer in writing as part of the specification. Readers bought now without that conversation are readers bought blind.
- If your reader estate is recent and healthy, do nothing dramatic. Note the position, factor it into your next refresh cycle, and check what your existing vendor commits to.
- If you are running legacy credentials, the credential exposure is the urgent problem and Aliro is not the answer to it. Migrate to an encrypted platform now, and make Aliro capability a selection criterion for the readers you buy as part of that work. The two decisions happen at the same time anyway, because both require access to the same doors.
- If you are mid-way through a mobile rollout, finish it. Aliro is a portability standard, not a replacement technology, and a half-deployed credential programme is worse than either end state.
The upgrade nobody costs properly
There is a second decision that belongs in the same conversation and usually isn’t.
If you are opening up readers to replace them, that is also the moment to deal with the reader-to-controller link. Legacy Wiegand transmits unencrypted and unsupervised, and a device spliced into the cable can capture or inject credentials. OSDP replaces it with encrypted, supervised communication, and is published as BS EN IEC 60839-11-5:2020.
Doing the credential migration, the reader replacement and the OSDP upgrade as one programme costs materially less than doing them across three separate projects, because all three need the same physical access to the same doors. Any integrator quoting one without raising the others is either not thinking about it or is planning to come back.
Evolution plans credential strategy across physical and mobile, and will tell you where Aliro support is real and where it is roadmap. If you are specifying readers this year, that is a conversation worth having before the order goes in rather than after.