Platform overview
One record of residential life, used by everyone who touches it
Estate operations and residential identity are not two products bolted together. The tenancy and payment records an estate creates while doing normal work are the same records a resident carries to their next home.
How it fits together
Two layers on one data model
The operational layer is organization-scoped. The residential layer is resident-centred and can span several estates or standalone properties. They share a model instead of copying data between systems.
Estate operations layer
Scoped to an estate or organization. Everything an estate admin or facility manager needs to run the community, with roles and scopes that decide who sees what.
An estate sees the residents and tenancies inside its own boundary. It does not automatically inherit a resident’s history from anywhere else.
Residential identity layer
Centred on the resident. A residential profile holds current and previous tenancies, documents, rent obligations and payment evidence, each carrying the source that supports it.
Moving home creates a new tenancy on the same profile. Leaving an estate does not erase the record of having lived there.
Modules
What the operational layer covers
Exact availability depends on what has shipped for a given estate. These are the areas the platform is built around.
Residents & properties
Blocks, zones and units with the residents attached to them, and occupancy that is recorded over time rather than overwritten.
Finance & collections
Service charges, levies and utilities billed against units, with payments, receipts, reconciliation and arrears.
Visitors & access
Resident-created invitations, single-use codes, gate verification, and entry and exit logs.
Issues & maintenance
Reports with category, location and evidence, assigned to an owner and tracked through to resolution.
Communication
Announcements and emergency notices targeted at the right audience, with a record of what was sent.
Infrastructure
Roads, drainage, power, water, streetlights, gates and shared facilities tracked as assets with faults and projects.
Clients
Different jobs need different surfaces
A facility manager works in tables and forms on a laptop. A resident checks a bill on a phone. A guard verifies a code at a gate at night. Each gets a client built for that job, over the same API.
Estate & facility portal
The authenticated web application estate admins and facility managers work in every day: registers, tables, billing, workflows and reporting, scoped by role.
Resident mobile app
Residents get a dedicated mobile experience for visitors, bills, issues, announcements and their own residential record — not a squeezed-down web portal.
Security app
A focused operational client for gate personnel that exposes the minimum information needed to verify a visitor and log entry and exit.
See the platform against your own estate
A short walkthrough using your blocks, your charges and the way your team already works.