Direct answer: Architectures that run on a local server or device (edge) keep the authorization list on site, so plate reading and barrier opening continue even during an internet outage. Only cloud-based reporting and remote management pause temporarily until the connection returns; transit records are not lost and are synchronized once the connection comes back.
How does a local (edge) architecture work?
In a local architecture, the LPR software and the authorization list (whitelist/blacklist) are kept directly on the on-site device or mini server. When the camera image is processed and the plate is read, the comparison is done locally without going out to the internet, and the barrier command is issued directly from the site. This means the decision mechanism does not depend on an internet connection.
What changes in a cloud architecture?
In a fully cloud-based architecture, every plate query is sent to the central server and a response is awaited from there; when the internet goes down, this query cannot complete. To reduce this risk, cloud-based systems also usually cache a copy of the last-synchronized authorization list on site; this way, basic transit function can continue even during short outages.
What happens once the connection returns?
Transit records (plate, date, time, direction) created during an internet outage are kept locally. Once the connection returns, these records are automatically transferred to the central system or the cloud; there is no data loss in reporting and query screens, only a delayed synchronization.
Which architecture is preferred, and when?
A local/edge architecture is recommended for single-location sites, factories, or parking facilities where uninterrupted operation is critical. For multi-branch corporate structures where central reporting is a priority, a cloud architecture with local caching support can be preferred. The right architecture is determined during the site survey based on the reliability of the internet infrastructure.
Quick facts table
| Local (edge) architecture | Transit operations continue during an internet outage |
|---|---|
| Cloud architecture (with caching) | Can operate with the cached list during short outages |
| Transit records | Kept locally during the outage, then synchronized |
| Affected function | Only remote management and real-time reporting |
Frequently asked questions
Does the barrier still work if the internet goes down?
Yes, with architectures that run on a local server or device; since the authorization list is kept on site, transit operations continue.
Where is plate data saved when there's no internet?
Transit records are kept in the memory of the device or the on-site server; they are synchronized to the central system once the connection returns.
Which architecture should I choose?
A local architecture is recommended for single-location sites where uninterrupted operation is critical; a cloud architecture with local caching support is recommended for multi-branch structures where central reporting is a priority.
Last updated: July 20, 2026 · Technical content: Gray Teknoloji project team
Get a free survey and quote →