Parking Access Controller — The IoT Hub
Overview
Every camera, barrier, reader, display and terminal on a site terminates at the controller. It makes the access decision locally, which is the single design choice that determines whether your car park survives a bad network day.
Cloud-dependent systems demo beautifully and fail on the first WAN outage. Ours buffers transactions on site and syncs when the link returns — an outage degrades reporting, never lane operation.
Specification
- Local decisioning — lanes keep running when WAN drops
- Buffers transactions and syncs on reconnect
- Single pane for every device on site
- Remote diagnostics and firmware push
Where it's deployed
- Multi-lane entry and exit decks
- Multi-site portfolios
- Sites with unreliable connectivity
- Mixed-credential lanes
FAQs
Kerbside Controller — common questions.
The questions buyers actually ask us. Ask them of every vendor who quotes you — the answers separate integrators from box-sellers.
Ask us something elseNothing visible. The controller decides locally, so barriers keep opening for valid vehicles. Transactions queue on site and reconcile automatically on reconnect. This is the first question to ask any vendor, and many will not answer it directly.
It depends on the protocols your current equipment exposes, which we confirm during the site survey. We tell you honestly what has to be replaced rather than quoting a full replacement by default.
Yes — the dashboard rolls up occupancy, revenue and device health across every site in a portfolio, with per-site drill-down.
The rest of the stack
Rarely deployed alone.
Get a quote for kerbside controller
We'll walk your lanes, measure your peak, and tell you what you actually need — before anyone quotes you for hardware.