Replace the gate book. Secure every entry.
Ahcess is the access layer for residential estates, commercial property and managed communities. Credentials instead of paper, household approvals instead of phone calls, and an append-only record of every entry, exit and refusal.
No hardware to install. Works on the phones your guards already carry, and keeps working when the signal drops.
Hold the code inside the frame
12s
Target median time from scan to decision at the gate
Zero
New hardware, wiring or capital expenditure to begin
12h
Offline tolerance before a device enters restricted mode
5 days
From signature to a live gate, data preparation included
The problem
A paper book at the gate is not a security record.
It is a queue, a liability, and an argument waiting to happen. Three failures repeat at every property we have looked at, and none of them are the guard's fault.
The record is unreadable
A book of handwriting nobody indexes. When something goes wrong, the answer takes three days and comes down to who remembers what.
What Ahcess does: every entry, exit and refusal is a structured event, searchable in seconds and append-only.
Approvals happen in group chats
A guard phones a resident who does not answer, so the visitor waits at the barrier, or gets waved through on a guess.
What Ahcess does: the request goes to every household member with approval rights at once, and the ladder escalates on a timer.
Nobody can prove anything
A stolen parcel, a damaged barrier, a disputed entry. Without a defensible trail the property carries the liability by default.
What Ahcess does: every decision carries its author, its timestamp and its stated reason — including manual overrides.
How it works
Invite, pass, scan, admit.
Four steps, and the visitor installs nothing. The whole loop is designed around the twelve seconds a guard actually has.
Step 3 in detail
Verification is local, so the queue never waits for a network.
Credentials are signed, and the device holds the property's active set plus the revocation list. A revoked pass is refused offline just as it is online. The event queues with its real device timestamp and syncs when the signal returns.
11.4s
median gate time
12h
offline tolerance
0
server calls to verify
Founding pilots see it first. We are recruiting a small group of properties in Lagos to run this loop at a live gate, with onboarding and guard training included.
Apply as a pilotSurfaces
Four people, four different jobs.
The same record, narrowed at the source for each role. A guard sees a name and a unit — never a phone number, arrears, or where someone has been.
At the gate
One hand, bright sun, no signal
The surface that decides whether any of this works. One dominant action per screen, targets sized for a gloved thumb, and a decision the guard can defend afterwards.
What this role cannot see
Phone numbers, arrears, movement history, and anything about another unit. A lost guard phone is an inconvenience, not a breach of the resident register.
Permissions default to deny
If a role is not explicitly granted a field, it does not receive it — there is no implicit access anywhere in the system. The full matrix is published rather than described.
Read the permission matrix →Offline first
The gate does not stop when the network does.
Credentials are signed, so a guard's device can verify one on its own. Events queue with their real timestamps. Nothing about this is a degraded mode — it is the design, and it is why Ahcess works at properties where connectivity is not a given.
Signed credentials
A pass verifies against a key held on the device. No round trip, so no queue while a page loads.
Synced revocation list
Revoke a credential and offline devices refuse it too, on their next sync or immediately if they are online.
Honest timestamps
A queued event keeps the time it actually happened, and is marked as synced late rather than backdated silently.
No hardware required
No barriers, readers or cabling to buy. Ahcess runs on the phones your guards already carry, from day one.
The one thing that genuinely needs a network is asking a household to approve an unannounced visitor. The app says so plainly and applies the property's own default, rather than letting a guard guess.
Who it is for
Anywhere a gate has a queue behind it.
Property variation is configuration, never a bespoke build. The same credential and event model fits each of these; what changes is the policy on top.
Residential estates
Households, domestic staff, contractors and deliveries at a shared gate.
Apartment complexes
High visitor turnover, tight lobbies and parcels that need custody.
Commercial & offices
Tenant companies, meeting guests and contractor engagements.
Schools & campuses
Guardian pickup, staff schedules and visitor screening with a duty of care.
Hospitals
Ward visiting hours, supplier deliveries and emergency vehicle access.
Malls & hotels
Loading bays, contractor windows and guest vehicle permits.
Trust
A committee will ask whether this becomes surveillance.
It is the right question. Our answers are published in full, including the parts that constrain us, because a posture you have to ask for is not a posture.
The property is the controller
They decide what is collected and for how long. We process it on their instruction, and we say so rather than burying it.
Managers see aggregates
Querying one person's movements requires an investigation with a stated reason, and that query is logged for the committee.
Retention is enforced, not promised
An automatic purge removes identifying fields at the property's chosen period. Nobody can quietly extend it.
No biometrics today
No facial recognition and no biometric processing anywhere in the product. Those are roadmap, and they are labelled as roadmap.
Tiers
Three tiers, by capability.
Priced per property against unit count and gate count. We quote directly rather than publish a number that would be wrong for most properties.
Essential
A single property replacing paper at the gate, with the record and reporting that makes it defensible.
Professional
Most propertiesEverything in Essential, plus the operational depth a facility manager needs day to day.
Enterprise
For management companies and multi-property operators accountable across a portfolio.
Ten properties. One city. Built with you.
We are recruiting a small group of estates, complexes and management companies in Lagos to run Ahcess at a live gate. You get the product, the onboarding and the guard training. We get the truth about what breaks.
What you commit. One gate live, a baseline captured at onboarding, sixty days of real use, honest feedback every fortnight.
What you get. Onboarding and guard training at no cost, direct access to the team building it, pilot pricing held for two years.
What you keep. Your data, exportable at any time, and the right to walk away at the end of the pilot with the record intact.
Questions
The ones that decide it.
Do we need to buy hardware?
No. Ahcess runs on the phones your guards already carry. Barrier and reader integration is roadmap for those who want it later, and nothing in the product depends on it.
What happens when the network drops?
Verification, deliveries, incidents and exits keep working, and events queue with their real timestamps. Household approval is the one thing that needs a signal, and the app applies your property's stated default instead of guessing.
Will our guards actually use it?
Training takes under thirty minutes and is measured by observed task completion, not attendance. The number to watch afterwards is manual overrides — a rising override rate means the system does not fit the property yet, and that is our problem to fix.
How long does it take to go live?
Five working days from signature, including data preparation. The go-live checklist is in the product, with an owner against each step.
Can you restrict access for unpaid dues?
It is configurable and off by default, and it stays a written per-property decision by the administrator. It is legally sensitive, and we will not enable it quietly on your behalf.
What happens to our data if we leave?
You export the full ledger in a readable format, and we delete our copy on a stated schedule. Your access record belongs to the property, not to us.