Security & Protected Sites

Security in this market is still a person at a gate — estates, banks, schools, hotels, depots, events — sitting next to CCTV, access control, and a control room that may only exist on paper. Halogen, Armourguard, and Kings Guards are the shape of manned guarding. Hikvision, Dahua, Axis, Bosch, HID, and ZKTeco are the shape of the hardware on the wall. Those names define the sector. They are not a client list.

Software fails here at the post and in the log. A selfie that is a printout. A lock that opens with no trail. A camera that has been dark since Tuesday. A roster on WhatsApp that nobody can reconstruct after an incident. The product has to know who stood where, what they opened, and what the client was told — including when the network drops.

We build that layer: liveness that is not a still photo, devices you can actually command and audit, and the ops desk that holds the week together. We do not run a guard company. We do not sell cameras. You keep the posts, the licence, and the code.

Inquire now

Who this is for

Guard companies that still run the roster, clock-in, and occurrence book on WhatsApp and paper.
Estates, hotels, and sites that need a live face at the gate and a lock or camera they can command without calling the vendor.
Operations desks that have to send a sitrep the client will believe, with a trail of who was on post.

In this sector

Posts, liveness, devices, and the desk that can prove it.

Manned guarding
Uniformed posts, events, residential and commercial sites. The software has to know who is on the gate, not who was on a spreadsheet this morning.
AI liveness
Clock-in that is a live person at the post — not a printed face, a video on a phone, or a colleague’s selfie sent from the bus. GPS has to agree with the roster.
IoT you can actually use
Locks, gates, cameras, and sensors that take a command and leave a trail: who opened what, when it went offline, what the fallback is when the network is down.
The client on the other side of the wall
A sitrep, who is on duty, a thread per location. Not a PDF at month-end and a phone call when something is already wrong.

Areas covered

We build the software a protected site actually runs on. Typical work includes:

01
AI liveness at the post
Attendance that demands a live face and a location that matches the roster. A still photo is not a clock-in. The desk has to see who verified, who was late, and who did not appear.
02
IoT that takes a command
Locks, barriers, and cameras as things you can open, lock, or query — with a log. A camera that only exists in a brochure is not a device. Offline mode has to be designed, not hoped for.
03
Roster, incidents, sitreps
Posts, shifts, and people as data. An incident has a type, a site, a reporter, and a close. The weekly sitrep is composed from that record, not typed from memory.
04
Handover
Repo, keys, hosting in your name. We do not keep the guard list or the camera feeds after we leave.

What the software has to survive

A security product is not finished when the dashboard looks like a control room. It has to survive a spoofed face, a lock with no log, and a night the network is dead.

Liveness is not a selfie

Printed photos, masks, and a video held up to the camera are the attack. If clock-in accepts a still, you do not know who is on post.

The post has a place

GPS that does not match the gate is a problem, not a footnote. Buddy clock-ins from the estate office should not look like a manned perimeter.

Devices leave a trail

Who unlocked, who forced, which camera went dark. If the only record is a WhatsApp voice note, you will not reconstruct the night.

The network will fail

Gates still open. Guards still stand. The product needs a mode when the cloud is unreachable — and a catch-up when it returns.

Questions a client — or a guard at 05:50 — will ask

If the product cannot answer these, you will settle it after an incident. We design so you do not have to.

01
Was the person who clocked in actually at that post, alive, not a photo?
02
Who opened the lock, and can we see it after the fact?
03
If a camera goes offline at 02:00, who is told, and what is the fallback?
04
Can the client see who is on duty without calling operations?
05
When the network drops, does the gate still have a mode that is not a padlock and a prayer?

How we build it

We build for the post, the device, and the log — not for a brochure with a shield on it.

Liveness first

The clock-in rule is designed before the marketing site. A live face and a matching location, or it does not count.

Devices as commands

Locks and cameras modelled as things you can act on, with an audit trail, including the offline case.

Roles that do not share a login

Guard, supervisor, ops, client. The client portal is not the ops console with the filters hidden.

Handover

Repo and runbooks: reopen an incident, republish a sitrep, rotate a device credential.

Someone who has stood a night shift sits in discovery if you have them.
We do not ship a roster app that accepts a still photo as attendance.
We do not keep posts, footage, or client data after handover.

Where we stop

We build the system. We do not pretend to be the guard company, the camera vendor, or the regulator.

We do not operate Halogen, Armourguard, or Kings Guards. We do not sell Hikvision, Dahua, Axis, Bosch, HID, or ZKTeco hardware. Those names define the sector.
We do not hold a private-guard licence, an NSCDC brief, or a camera dealership. You keep the posts and the permits. NSCDC, the Nigeria Police, NITDA, and NDPC define that environment. They are not clients.
We do not keep the repository, production keys, or footage after handover.

The landscape

Agencies that write the rules, then camera and access marks the market already knows, plus Bosch on the building-systems side. This is the landscape — not a list of Emicraft clients. Local guard firms such as Halogen, Armourguard, and Kings Guards belong in that picture even when we do not host their marks.

Regulators & agencies