TheTrustInfrastructureforAfricanPrivateSecurity.
Every shift, patrol and incident recorded where it happens — on the phones your guards already carry, working with or without signal. The record cannot be edited afterwards. Not by your client, not by you, not by us.
Developed with Olswen Independence Alliance Ltd — Nigeria's first licensed operator to deploy ZumaGrid in live field conditions.
Platform
Four Layers of Trust
Each layer is independently rugged and collectively unbreakable. Together they form the complete security operating system.
At the gate
Check in, walk the route, report what happened, raise a panic alert. Works with no signal — nothing is lost at the post.
The operation
Roster static posts, patrols, escorts, VIP details, convoys and cash runs. Check calls on the work that moves.
Assurance
Your client sees attendance, patrol completion and the incidents that concern them — and no guard personal data.
The record
Append-only. A shift, a scan or an incident cannot be edited or deleted afterwards by anyone, including ZumaGrid.
Use Cases
Deployed Across Sectors
One platform, many missions. Tap a sector to see how ZumaGrid adapts.
Residential Estates
Replace the paper occurrence book. See whether your gates were staffed last night and whether the patrol was actually walked, without asking your provider to tell you.
Discuss this use case arrow_forwardCoverage
Every Kind of Duty You Sell
Most systems model a guard standing at a gate. That is a fraction of the work. A detail, a run and a deployment are team jobs with a commander \u2014 and they are modelled as such.
Patrol completion is only measured where a patrol applies. An escort has no checkpoints, so it never reports as a failed patrol \u2014 it reports on check calls instead.
What it proves
Three Things You Can Show a Client
Not dashboards. Answers to the questions a client actually asks after an incident.
Who did not turn up
Roster who is expected. A closed shift with no check-in is a no-show, reported with its denominator — three missed out of twelve reads very differently from three out of four hundred.
When a run goes quiet
Escorts and cash runs have no checkpoints, so they run on check calls at an agreed interval. A missed call is the alarm, raised at the top of the supervisor board.
Records nobody can edit
Shifts, scans, incidents and the audit trail are append-only at the database level. Not editable by your client, not by you, and not by ZumaGrid.
About
Building Africa's Sovereign Trust Infrastructure
From a single security post to a national intelligence grid.
Our Mission
Every naira spent on security should be accounted for. Every patrol should be verifiable. Every incident should be recorded in a way that holds up in court.
ZumaGrid was founded to eliminate the trust deficit in African private security. We replace paper occurrence books and fragmented spreadsheets with immutable digital infrastructure — from the gate to the cloud.
“Trust is not declared. It is engineered — post by post, patrol by patrol.”
— Donald Ogbemudia, CEO & Founder
Office
Lagos
Nigeria
Operating in Lagos, Abuja, Port Harcourt and Kaduna.
Olswen Independence Alliance Ltd
Licensed Private Security Operator — Nigeria
Lead Partner, Shareholder & Founder
Start here
Which One Are You?
Who uses ZumaGrid, what each of them does with it, and how each one gets in. Some we set up directly. The rest are added by the organisation they work for.
Private security company
Owner, administrator, HR, supervisors, guards.
Roster posts and every kind of duty, prove attendance and patrols, handle incidents with timed escalation, decide what each client sees, issue access codes, and keep contracts, payroll and licences in one place.
How you get in: ZumaGrid creates your organisation and your administrator and hands the login over. You then add supervisors and guards yourself, each with a badge number and a password. Nothing is emailed.
Corporate and CSO
Chief Security Officers of banks, oil and gas, and large enterprises, with their branches and site managers.
Run every branch or site under one organisation, guard with your own people or approved security providers, see exceptions first across dozens of branches, scope logins to a branch or region, and import a whole branch network from a spreadsheet.
How you get in: ZumaGrid provisions your organisation as a corporate, sets up your CSO login, and approves any security providers you use. Your branches are then created by paste-and-import.
Estate, complex or client
Estate managers and committees, shopping complexes, and any business that pays a security company.
See attendance, patrol completion, the guards on the gate and the incidents your provider shares. Issue visitor access codes, and manage the businesses inside your premises.
How you get in: Your security company adds you. If you do not have one on ZumaGrid yet, tell us and we will introduce you to one, or you can see what the client side looks like in a demo.
Guards and supervisors
The people on the post.
Check in at the post, scan the round, log visitors, report incidents and raise a panic alert, with or without signal. Where the company uses it, check in with your face.
How you get in: Your company gives you a badge number and a password. You install the field app on the phone you already carry and sign in with your badge.
Residents and tenants
People who live or trade inside a guarded estate or complex.
Give a visitor a code, and the guard at the gate checks it. Single use by default, and it stops working at the end of the day.
How you get in: Your estate committee creates your account and the security company approves it.
Police, NSCDC and agencies
Verified officers and regulators.
Maintain the wanted and stolen registers, review submissions from security companies for national sharing, and query the registry.
How you get in: ZumaGrid verifies your agency and sets up your accounts.
Anyone
No account needed.
Check that a security guard is genuine and licensed, and report a stolen vehicle, phone or asset with a police reference.
How you get in: Nothing to set up.
Construction and project sites
Main contractors and project owners running large sites with many subcontractors.
Site access for workers by QR badge (face optional), who is on site right now, hours per person and per subcontractor, emergency muster, and material deliveries received and stocked. New: in pilot.
How you get in: ZumaGrid sets up your organisation and each site, and chooses the modules for each. You then issue your own staff logins. Try a demo first.
Facility management firms
Firms that run buildings for others, with their own guards, cleaners, engineers or other companies’ guards.
Access control and attendance across the buildings you manage, whoever employs the person at the door, plus supplies received and stocked. One organisation can run many sites. New: in pilot.
How you get in: ZumaGrid sets up your organisation and each building as a site. Your own guards, if you have them, use the Company and Field apps.
How it works
Running by The End of the Week
No installation, no site survey, no hardware order.
We set you up
We create your organisation and your administrator, and hand over the login directly. You change the password the first time you sign in.
You add your operation
Your posts, the points a guard must reach on patrol, and an account for every guard and supervisor — each with a badge number and a password you issue.
Your guards work
They install it on the phone they already carry, sign in with their badge number, and check in. From that night you can see who was on, and who was not.
Questions
The Things You Are About to Ask
Our gates have no network. Does it still work?expand_more
Yes. Once installed on the phone, check-ins, patrol scans, incidents and panic alerts are stored on the device and sent the moment signal returns. Nothing is lost at the post — that is the case the app was built for, not an edge case it tolerates.
Our guards share one phone between shifts. Is that a problem?expand_more
No. Each guard signs in with their own badge number and password, so the record follows the person rather than the handset. We are direct about the limit: with a shared device and a password the company issued, the record proves a badge account acted, not that a particular person did. Where your company turns on face check-in, the guard also has to show a live face that matches the one enrolled, which makes clocking a colleague in much harder. It is a basic check, not certified anti-spoofing.
Most of our guards have no email address.expand_more
They do not need one. You issue a badge number and a password and hand them over directly — nothing is emailed. Supervisors and HR staff work the same way. Only your administrator signs in with an email.
What if a guard loses the phone, or forgets the password?expand_more
You reset it yourself and hand over a new one. Because there is no inbox, there is no reset link to wait for, and no account left stranded when someone leaves — you revoke access the same hour.
Do we have to buy hardware?expand_more
No. It runs on phones your guards already carry. Dedicated devices at posts and tags at checkpoints are available where a site needs them, quoted with installation, and nothing depends on buying either.
Who can change a record after the fact?expand_more
Nobody. Shifts, patrol scans, incidents, check calls and the audit trail are append-only in the database itself — not a setting, and not something an administrator can switch off. That includes ZumaGrid. A mistake is corrected by adding a record, never by editing one.
Where does our data live, and who else sees it?expand_more
Your organisation only. Every query is scoped to your tenant at the database level, so another company on ZumaGrid cannot see your posts, your guards or your incidents. A client you give a dashboard to sees attendance and patrol completion — never a guard’s personal data.
Ready to Secure Your Assets?
Join the vanguard of organizations redefining private security through institutional-grade technology and operational certainty.