A gate controller that works offline allows an estate to keep checking resident credentials and operating its gate even when the internet connection disappears. For Nigerian estates, that is not a minor feature. A router fault, fibre cut or mobile-network outage should not suddenly turn an automated entrance into a manual gate.
The important question is where the access decision is made. If every card, RFID tag or visitor credential must contact a remote server before the gate can open, the internet has become a single point of failure.
What makes a gate controller work offline?
An access controller sits between the credential reader and the physical gate, barrier or lock.
When a resident presents a card or vehicle credential, the controller needs to determine:
Who is this credential assigned to?
Is it currently valid?
Is this person allowed through this entrance?
Is access permitted at this time?
A true offline-capable controller stores enough of that information locally to make the decision without contacting the internet for every request.
This architecture is common in professional access-control equipment.
HID's VertX EVO V1000, for example, stores its access-control database locally and is specified to continue making access decisions and logging events when it is not communicating with the host software. HID lists capacity for up to 250,000 cardholders on the controller.
That is the type of behaviour an estate should be asking about.
The reader should not simply stop recognising residents because the router has been unplugged.
Before choosing hardware, understand the wider access control system in Nigeria, because the controller is only one component in the chain.
What information should be stored locally?
Offline operation requires more than storing card numbers.
Depending on the system, the controller may need local copies of:
- authorised users;
- credential numbers;
- access permissions;
- time schedules;
- blocked credentials;
- door or gate rules;
- recent visitor credentials;
- and configuration information.
It should also have enough local storage to record access events while communication with the main system is unavailable.
For example, HID's current Aero X1100C intelligent controller lists capacity for 250,000 credentials and a 500,000-event transaction buffer.
ZKTeco's current InBio Pro Plus range similarly lists up to 100,000 users and 500,000 transactions, depending on the model and configuration.
An estate will rarely need capacities anywhere near those numbers, but the principle matters.
If the internet disappears at 4 p.m. and returns at 9 p.m., the controller should not lose every gate event that happened during those five hours.
It should continue operating and retain the records for later synchronisation.
The same principle applies regardless of whether residents use the credentials discussed in our card readers, fobs and PIN pads comparison.
How should readers communicate with the controller?
The reader and controller also need a dependable local connection.
Common access-control communication methods include Wiegand, RS-485 and OSDP.
Wiegand remains widely supported, particularly on older installations, but estates buying new equipment should ask what newer communication options are available.
HID describes OSDP as providing secure-channel support and bidirectional communication between compatible readers and controllers. Its Aero controllers support both Wiegand and OSDP reader connections.
The Security Industry Association also operates an OSDP Verified programme for products that have been independently tested for conformity with the OSDP standard.
This does not mean every estate needs to replace working equipment simply because it uses Wiegand.
It means a new installation should consider:
- reader compatibility;
- encrypted communication;
- future replacement options;
- maximum cable distances;
- monitoring;
- and whether the estate is being locked into one proprietary vendor.
The wiring matters as much as the protocol.
Our guide to access control wiring at the gate explains why cable type, voltage drop, conduit and reader distance should be planned before installation.
Offline capability is useless if the controller cannot reliably communicate with the reader sitting twenty metres away.
What happens when the internet comes back?
Offline operation should not create a second isolated database.
When connectivity returns, the controller and management system should reconcile what happened while communication was unavailable.
That usually means uploading stored access transactions and receiving any configuration or credential changes that occurred while the controller was offline.
ZKTeco's own support documentation gives a practical example: when an InBio260 Pro controller has been offline, stored transactions can be uploaded to the management software after the controller reconnects, including through periodic transaction retrieval.
Ask the vendor exactly how this works.
For example:
A resident enters at 6:05 p.m. while the internet is down.
Is the entry stored locally?
When connectivity returns, does that 6:05 p.m. event appear in the central history?
Now consider the opposite direction.
Suppose an administrator revokes a lost credential while the gate is offline.
When does the controller learn that the credential has been cancelled?
Good offline architecture needs a clear answer for both situations.
The controller should continue operating during temporary disconnection without allowing two databases to drift indefinitely.
What happens if power fails too?
Internet failure and electricity failure are separate problems.
A controller can have excellent offline functionality and still be useless if it loses power.
The access controller, RFID reader, router, network switch and gate motor may all depend on electricity.
That means an offline-capable estate entrance also needs a proper gate hardware backup-power plan.
Some controllers are designed to work with dedicated power enclosures and batteries.
ZKTeco's optional InBio Pro Plus enclosures, for example, provide space for backup batteries alongside their controller power supplies.
During commissioning, test failures separately.
Test 1: Disconnect the internet.
The credential should still work if offline access is part of the design.
Test 2: Switch off mains power.
The controller and required readers should move onto backup power.
Test 3: Remove both internet and mains power.
This is the real test.
Test 4: Restore the internet.
Confirm that stored events synchronise.
Test 5: Restore mains power.
Confirm that switching between normal and backup power does not reset the system unexpectedly.
An installer telling you that a controller “supports offline mode” is not enough.
Ask them to demonstrate it at your gate.
What should you ask before buying a controller?
Do not choose a controller solely because it has many ports or a familiar brand name.
Ask these questions:
Where are authorised credentials stored?
The answer should make clear whether routine gate decisions can happen locally.
How many users can it store?
Allow for future estate growth.
How many transactions can it retain offline?
This determines how much history can survive an extended disconnection.
Which readers does it support?
Check card readers, RFID, biometrics, QR readers and any future hardware being considered.
Does it support OSDP, RS-485 or Wiegand?
Understand what your proposed readers actually require.
How are offline events synchronised?
Ask the supplier to demonstrate the process.
What happens to newly issued credentials while the controller is disconnected?
A credential created in the cloud cannot magically reach an offline controller.
What happens to revoked credentials?
This is equally important.
Can the estate export its records?
Do not allow years of access history to become trapped inside proprietary software.
Can another installer support the hardware?
Widely supported equipment reduces long-term vendor dependence.
Does it integrate with the gate or barrier already installed?
The controller ultimately needs to trigger physical equipment.
For resident vehicles, see our guide to vehicle access control for estates.
Also ask where the controller will physically be installed.
It should be protected from rain, excessive heat, tampering and accidental damage while remaining accessible for authorised maintenance.
How should offline control work with Kompound?
A gate controller that works offline should handle the immediate physical decision at the gate while the wider estate platform manages residents, visitors and access records.
The two responsibilities are related but different.
For example, Kompound can support a resident creating visitor access before the guest arrives.
The gate system can then receive the information it needs so that an expected access decision does not depend entirely on a live internet request at the exact second the visitor reaches the entrance.
Our visitor management guide for Nigerian estates explains the wider workflow.
The objective should be offline-first access, not offline-only access.
When connectivity exists, the estate benefits from synchronisation, administration and central records.
When connectivity disappears, the entrance should continue handling the access decisions it already knows about.
When the connection returns, the systems should reconcile.
That is far better than an architecture where a working barrier, working reader and authorised resident are all waiting for a remote server before the gate can move.
Before approving a controller, ask the installer to unplug the router.
Then present a valid resident credential.
What happens in those next ten seconds tells you more about the system than most sales presentations will.