Skip to content
The entrance gate and sign of Abuja Model City in Gwarinpa, Abuja, with cars, a motorcycle and trees.

Come home to acalmer gate.

Your visitors arrive expected. The guard knows who to look for. The estate keeps one clear record of every arrival, from the first pass to the last check-out.

4 inside, 12 expected

Built for Nigerian estates, closes and resident associations. Works on the guard's phone and the administrator's laptop.

The resident passes screen on a phone: the Expected filter, a recurring pass for Blessing Okafor at Main Gate, an Anytime Visitor pass and the New pass action.The resident passes screen on a phone: the Expected filter, a recurring pass for Blessing Okafor at Main Gate, an Anytime Visitor pass and the New pass action.

Your visitors, in your pocket.

Built for the way an estate runs.

A Nigerian estate is usually a gated community: a gatehouse, internal streets, shared services and a residents' association. The product is built for how that community runs.

A palm tree, a home and a walled gate at sunrise in Gwarinpa Estate, Abuja.
Homes and households, connected to one gate.
The entrance gate of the Lekki Peninsula Scheme 1 estate in Lagos, with its security booth and construction behind.
A gate that knows who is expected.
A row of blue and white tropical apartments with palm trees in Abuja, Nigeria.
Every arrival, kept in one record.

The estate structure, in one view.

The gate, the lane and the homes, the same structure the administrator builds in the product. Every pass and gate event is recorded against it.

An illustrated garden estate: six homes around a lawn and a pond, a gatehouse with a lifting barrier, and a visitor pass for Ms. Fatima Yusuf at the main gate.

A visit, end to end.

Four quiet steps, each recorded against the community, the unit and the gate.

The resident creates a pass

One visit or a routine, the visitors, the gate and the expected window. The pass carries a QR code and a six digit PIN.

The visitor arrives

They open the link, show the code at the gate, or press Arrived to tell the resident they are outside.

The guard checks the party in

The guard sees the host, the apartment or block, the party size and the window. The PIN admits everyone the pass expects.

The community keeps the record

Check-in and check-out become an access event. The resident sees their own history, the administrator sees the community history.

One estate. Three points of view.

The same pass looks different to the three people who need it, and each sees only what their part of the job needs.

The resident home screen on a phone: Flat 1, House 33 at Mission Estate, with Create a pass, Household, History and Approvals above the visitor passes.The resident home screen on a phone: Flat 1, House 33 at Mission Estate, with Create a pass, Household, History and Approvals above the visitor passes.

For residents

Your visitors, already expected.

Create a pass, share the link, and see the people you are expecting. Manage the household without calling the office.

  • A pass for one visit or a routine.
  • The household, in one place.
  • Your own gate history.
The guard expected screen on a phone at Main Gate: on duty, two expected visitors, and the check-in action.The guard expected screen on a phone at Main Gate: on duty, two expected visitors, and the check-in action.

For guards

A short list, and one clear decision.

The expected party, the host and the unit, for the gates you cover. Ask for the PIN, check the party in, and log a walk-up with what happened.

  • Expected, inside and the gate log.
  • Only the gates on your shift.
  • Off duty means nothing to check.
The Mission Estate administrator overview, with 49 properties, 66 units, 2 gates, 5 requests waiting and 1 walk-up to review.The Mission Estate administrator overview, with 49 properties, 66 units, 2 gates, 5 requests waiting and 1 walk-up to review.

For administrators

The whole estate, in one quiet record.

Zones, streets, properties, units, gates and guards. Approvals, invitations, access history, walk-up review and broadcasts.

  • Build the structure once.
  • Decide only the claims you own.
  • A community opens with a gate and an accountable admin.

Inside the console

The administrator console

The community structure, the approvals and the gate record in one place, on a laptop at the gate or in the office.

The Mission Estate administrator overview, with 49 properties, 66 units, 2 gates, 5 requests waiting and 1 walk-up to review.The Mission Estate administrator overview, with 49 properties, 66 units, 2 gates, 5 requests waiting and 1 walk-up to review.
The Mission Estate dashboard on the review build.
  1. Zones, streets, properties, units, gates and guards, built once and edited in place.
  2. Approvals show only the claims the person may decide.
  3. Access history filters by date and searches the vehicle plate.

A gate should feel like a welcome.

The visitor is expected. The guard has the details. The resident has the record. A calmer gate, from the first pass to the last check-out.

Everything the gate needs. Nothing it does not.

The work of running a gate, arranged so a resident, a guard and an administrator each see their own part.

Visitor passes

One visit or a recurring routine, with a QR code, a six digit PIN and a share link.

Household

Family members and household personnel, with one-time codes to sign in.

Approvals

An owner or caretaker decides a tenant claim, and the administrator sees the record.

Access history

Every gate event, with a date range and a vehicle plate search.

Walk-up review

What the guard decided at the gate, flagged for the administrator to review.

Broadcasts

A message to the whole community, a street or one unit, counted before it is sent.

The gate is a promise. We treat it like one.

The platform was built with the isolation rules a community needs, and the record to answer for what happened.

The estate record and the person stay connected, without a paper book at the gate.

  1. Every request is checked against the community and the role, not only the screen.
  2. A one-time code for a first sign-in, then a password of their own. Passwords are hashed, never stored readable.
  3. The visitor PIN is derived from the pass and a server key. It is never stored, so a database copy carries no usable PIN.
  4. Privileged actions write an audit row in the same transaction as the action.
  5. The platform is built for the Nigeria Data Protection Act 2023. The privacy policy says what is kept, why, and for how long.

Come and see the estate at work.

A walk through the resident, guard and administrator screens using Mission Estate, a fictional community stocked with realistic homes, residents and visitor history.

Request a demonstration