About
Residential infrastructure, not another property app
Dharri started from two problems that turn out to be the same problem: estates cannot see their own operations, and residents cannot prove their own housing history. Both exist because residential records are never written down in a structured way.
What we are building
A place where residential life is actually recorded
A residential estate produces a remarkable amount of information every month. Who lives in which unit. What each unit was charged and what it paid. Who came through the gate and when. What broke, who fixed it, and how long it took.
Almost none of it survives in a form anyone can use. It is spread across a paper register at the gate, a spreadsheet on the manager’s laptop, a WhatsApp group, and a stack of transfer screenshots. The estate cannot answer basic questions about itself, and the resident ends up with no evidence of anything.
The operational side of the platform fixes the first problem, because estates need it immediately. The residential identity side follows from it: once tenancies and payments are recorded properly, a resident has something real to carry to the next home.
Manage residential communities today. Build trusted residential history that can follow a person to the next home.
Principles
How we make product decisions
These are the rules we apply when a shortcut would be easier.
Operations first, identity second — in that order
Nobody adopts a platform because of a record they might use in three years. Estates adopt it because collections reconcile and the gate works. The residential record is what accumulates while that happens.
A record is only worth what backs it
If a self-declared entry looks the same as a landlord-confirmed one, the whole thing is decoration. Verification sources stay visible and distinguishable everywhere the record appears.
The resident is not the estate's asset
An estate has a relationship with a resident for a period of time. It does not acquire their housing history, and it does not get to keep it when they leave.
The record is a by-product, not extra work
Nothing asks an estate to enter data twice to produce residential history. The history is what normal estate operations already generate.
The platform
Four surfaces, one record
Each client is built for the job it does, over the same estate and tenancy data.
- EstatesEstate and facility portalThe authenticated application estate admins and facility managers run the community from.
- ResidentsResident mobile applicationThe resident experience: visitors, bills, issues, announcements and the residential record.
- SecurityGate and security clientA focused operational client for gate personnel, exposing only what a visit check requires.
Talk to the people building it
If you run an estate, or you are thinking about the same problem from another angle, we would like to hear from you.