For most of the last decade, a gate lane was a stack of separate boxes. A camera read the plate, a server somewhere decided what the plate was worth, a reader handled the credential, and a controller closed a relay. Every box had its own cable, its own firmware, and its own way of failing. The interesting change in new controller designs is not any single feature. It is that plate reading, credential reading and the open-or-hold decision are collapsing into one device at the lane.
A label, not a standard
“Fourth generation” is a vendor’s framing, not an industry classification. Inugo, a Bluetooth-based access vendor, uses it for a gate controller it says will add license plate recognition and NFC alongside its existing Bluetooth access, with a Q4 launch described in its own announcement. No standards body numbers controller generations, so treat the phrase as shorthand for “plate camera and credential reader inside the controller” and nothing more.
The vendor’s claims, which are the only public detail we found, are worth stating plainly and checking independently. Inugo says the camera is built in with no external camera required, that plates from New Zealand, Australia, Europe and the USA are supported, that read accuracy reaches 99.8%, and that Bluetooth control remains as a fallback when a plate cannot be read. It says entry reads a plate, logs it and opens the gate, and exit reads again and matches the entry record. It also says the system can run offline with local storage. The NFC reader is described as coming through a partnership with payments provider Windcave, accepting dedicated cards, bank-issued cards, and phones using Apple Pay or Google Pay. None of these figures come from an independent test.
What moves to the edge
The architectural shift is easiest to see by asking where each decision is made.
In a conventional lane, the camera sends an image or a plate string to a server. The server looks up the plate against permits, reservations or an open session, and returns an allow or deny. If the link to that server drops, the lane either falls back to tickets and buttons or stops.
In an integrated controller, the lookup data lives on the device: a local copy of the permit list, open sessions and deny list, refreshed from a central system. The decision is made in the lane, and the central system learns about it afterward. That changes three things.
Latency becomes a local property. The time from plate read to open command no longer depends on a WAN round trip, which matters most at exits where queues spill into the street.
Network outages stop being lane outages. A lane can keep admitting known credentials from its local copy. What it cannot do is know about a permit revoked or a reservation created after the last sync.
State now lives in many places. A site with eight lanes has eight local datasets that must converge. The failure to design for is not a total outage, which is obvious, but a partial one, where two lanes disagree about whether a plate is already inside.
The synchronization questions to ask
Vendor materials tend to answer “does it work offline?” with a yes. The useful questions are narrower.
How are lists distributed, by full replacement or incremental change, and how does a lane report which version it holds? How are conflicts resolved if the same plate enters at one lane and exits at another while the link between lanes and server is down? For a plate-matched exit, what happens to a vehicle whose entry was logged on a lane that has since been replaced or reset? And when connectivity returns, are queued transactions replayed in order, and are duplicates rejected?
Ask also what the Bluetooth or NFC fallback looks like in practice. A fallback that works for a driver who has the app installed does nothing for a first-time transient visitor whose plate read failed. Someone still has to decide what that driver does, whether that is a ticket, an intercom call or a staffed override, and the controller’s marketing page will not decide it for you.
Credentials and payment scope
Putting an NFC reader in the controller raises a separate question: what payment data touches the device. A reader that accepts bank cards and wallets at the lane sits in the cardholder data environment. The right question is whether it is a PCI-listed point-to-point encryption solution or a reader integrated in some other way, because the answer determines how much of the surrounding network falls into assessment scope. Ask for the listing by name rather than accepting a compliance logo, and confirm with your assessor how the controller’s other functions, such as plate storage and remote management, are segmented from the reader.
For access credentials rather than payment, the wallet side is moving too. In February 2026 the Connectivity Standards Alliance released Aliro 1.0, a credential and communication standard for access points that covers NFC tap, Bluetooth LE, and Bluetooth LE with ultra-wideband for hands-free use. The release says it uses asymmetric cryptography, is designed to work without network coverage, and that Apple, Google and Samsung have committed to it. Those are commitments and a published specification, not shipping parking-gate support. For a procurement decision, ask whether a controller roadmap names Aliro certification, and treat a vague answer as a no for now.
Privacy and data residency
A controller that stores plates locally also stores personal data locally. That is a retention and access question, not just a convenience. Establish how long entries are held on the device, whether the data is encrypted at rest, what happens to the stored list when a unit is decommissioned or sent for repair, and who can export it. Many plate-privacy obligations attach to the operator regardless of where the bytes sit, so a distributed design means more places to inventory.
What to do with this
Treat integrated controllers as a different class of equipment, not a drop-in for the old stack. Before a pilot, write down the three states you care about: normal, link down, and recovering. Then test each one on a single lane with real plates, including a deliberately unreadable plate, a revoked permit pushed during an outage, and an exit that follows an entry logged on another lane. Measure read accuracy yourself, at night and in rain, instead of relying on a headline figure. And before any NFC reader goes on a lane, get the PCI listing in writing. A controller that passes those tests earns its place at the gate; one that only passes the demo has simply moved the old failure modes inside a smaller box.
