Billing that reconciles itself
Levy every occupied unit in one action. Payments land through Paystack or Flutterwave and settle against the oldest debt first, so arrears are a number you read rather than a spreadsheet you rebuild.
Renly unlocks the administration of residential estates in Nigeria, the service charges, the gate, and everything residents currently chase over WhatsApp.
Estate software usually solves billing or security, never both. Renly treats them as the same system because in practice they are: the person behind on their service charge is the person at the gate.
An append-only ledger. Corrections are new entries, never edits, so a disputed levy can always be traced.
Signed visitor passes, a searchable gate log, and a vehicle register that replaces the book on the desk.
Levy every occupied unit in one action. Payments land through Paystack or Flutterwave and settle against the oldest debt first, so arrears are a number you read rather than a spreadsheet you rebuild.
Visitor passes carry their own signature. The gate verifies them on the device, with no connection at all, and syncs the entry log when signal returns.
Residents report faults with photographs. Staff triage, assign and close them, and every message stays attached to the request.
Each estate's records are separated at the database level, not merely in application code. One estate cannot read another's, by construction.
A gatehouse loses signal, that is Tuesday, not an edge case. So a Renly pass carries a cryptographic signature the guard’s device can check on its own. Entry is decided in front of the visitor, recorded locally, and reconciled with the server when the network comes back.
Estate management software asks people to trust it with their money and their front gate. That trust has to be earned in how the thing is built.
Balances are computed from the ledger every time they are shown. Nothing is cached and quietly allowed to drift.
A gate that has not synced can still admit a recently revoked pass. We bound that window and say so, rather than pretending otherwise.
Patchy signal and shared hardware are the normal case here, not the edge case. The product assumes them.
We never sell it, gate logs are deleted after two years, and personal details never enter product analytics.
Tell us how many units you manage and how you collect today. That is usually enough for a useful first call.