kasri.app
Product
The complete operating system for the body corporate.
One register drives who belongs, who votes, who pays, who can act, and what gets recorded. Decisions become records; records authorize money, work, notices, documents, and audit trails. Built for Tanzanian associations moving toward mobile-money collections, controlled approvals, and regulator-ready governance.
The operating loop
Each workflow feeds the next.
Kasri is not a pile of modules. It is the loop a functioning association already runs manually: register people and units, make decisions, fund them, operate the building, resolve community issues, then keep the evidence.
Register
Members, roles, units, ownership, and tenancies define the association.
Decide
Meetings, quorum, votes, and resolutions turn intent into authority.
Fund
Approved budgets become service charges, statements, and controlled payments.
Operate
Requests, assets, vendors, and contracts move work out of chat threads.
Resolve
Notices, by-laws, and disputes become structured resident records.
Defend
Documents and audit exports make every action explainable later.
Module showcases
The complete system, shown as one operating loop.
Each capability has its own surface, but the product promise is the connection between them: register, decide, fund, operate, resolve, and defend.
One register drives access, obligations, votes, and statements.
Kasri starts with the people and property records that every other workflow depends on: who belongs, which unit they represent, what role they hold, and what they are allowed to do.
- Multi-role member directory for owners, tenants, committee, staff, vendors, and auditors.
- Unit register with ownership, tenancy, and fractional-share context.
- Permission boundaries that follow the member, unit, tenant, and role relationship.
Source of truth
1
register for people and units
Role gates
AAL2
for sensitive authority changes
Scope
Unit
own vs association-wide access
- 01Invite
A resident joins against a real association and role.
- 02Verify
Membership, unit, and authority are checked before access.
- 03Drive
Votes, statements, requests, and notices point back here.
Decisions become records; records authorize action.
The target governance workflow connects notices, agenda items, attendance, quorum, votes, minutes, and resolutions so committee decisions can stand up after the meeting ends.
- AGM and committee workflows built around notices, quorum, attendance, and agenda control.
- Weighted voting and resolution records tied back to unit ownership.
- Formal decisions that can authorize levies, budgets, vendor spend, and by-law action.
Quorum
79%
by represented share
Motions
5
ready for vote
Record
Signed
resolution register
- 01Notice
The meeting opens with agenda, proxy, and RSVP context.
- 02Vote
Quorum and ownership weight shape the decision.
- 03Record
A resolution becomes the authority for the next workflow.
Money follows decisions, not WhatsApp pressure.
Kasri is designed to turn approved budgets into service charges, mobile-money reconciliation, owner statements, and controlled outgoing payments with the right signatories.
- Service charges and sinking-fund contributions designed to follow unit records and approvals.
- Mobile-money reconciliation promise for M-Pesa, Tigo Pesa, Airtel Money, and bank rails.
- Dual-signatory payment controls so money leaving the account has authority behind it.
Collection
TZS
mobile-money first
Approval
2
signatories before payout
Visibility
Owner
statement-level transparency
- 01Issue
Approved contribution schedules become owner obligations.
- 02Match
Payments reconcile against unit and member records.
- 03Control
Outgoing payments require the right authority and audit trail.
Maintenance moves from chat threads into accountable work.
Resident requests, assets, work orders, vendor assignments, and contracts are meant to sit in one operational flow so committees can see what happened and why it cost money.
- Maintenance requests from owners, tenants, and staff.
- Work orders, assets, vendors, and service contracts in one operations lane.
- Approvals and vendor accountability connected to the same audit and treasury story.
Requests
9
triaged by priority
Assets
22
under care
Contracts
MFA
for high-risk approval
- 01Report
A lift, pump, gate, or security issue enters the system.
- 02Assign
The right vendor receives scoped context and timing.
- 03Close
Completion, cost, and evidence stay attached to the asset.
Soft conflicts become process instead of rumours.
Kasri brings notices, acknowledgements, by-law violations, fines, and disputes into a structured resident record so the association can communicate and enforce rules fairly.
- Operational notices with acknowledgement context.
- By-law reports, adjudication, and dispute records connected to resident identity.
- Community communication that creates evidence instead of disappearing into chat history.
Notice reach
41/48
acknowledged
Disputes
3
in mediation
By-laws
Tracked
from report to outcome
- 01Broadcast
Residents get notice before building operations affect them.
- 02Acknowledge
Committee can see who has received the message.
- 03Resolve
A violation or dispute moves through a documented process.
Every workflow leaves evidence a committee can defend.
The complete system ends in documents and audit: minutes, statements, notices, approvals, exports, and action logs that help committees answer owners, auditors, and regulators.
- Append-only audit trail for sensitive actions and exports.
- Document promise for minutes, budgets, statements, notices, and compliance packs.
- MFA-protected export paths for auditors, regulators, and committee accountability.
Audit
Append
who did what and when
Exports
MFA
for high-risk records
Pack
Ready
for committee review
- 01Capture
Actions across the system generate structured records.
- 02Seal
Sensitive logs and exports carry actor and timestamp context.
- 03Explain
The association can produce evidence after the fact.
Built compliance-first
Bank-grade trust. From line one of the schema.
We spent a year on the compliance scaffolding before shipping a single feature — because RERA RERA (Real Estate Regulatory Authority) Tanzania's real estate regulator — funded in the 2025/26 budget to require audit-grade records and structured reporting from developments and body corporates. is coming, and your records have to survive an audit.
22 roles · 50+ permissions
Permission-gated everywhere — from chairman to vendor plumber. Row-Level Security at the database layer.
Step-up MFA
Every critical action — payments, role changes, audit export — requires a fresh TOTP TOTP (time-based one-time password) A short-lived code from an authenticator app — Kasri asks for a fresh one before payments, role changes, and audit exports. challenge.
Dual-signatory treasury
Chairman + treasurer must both sign. The same user cannot countersign their own request.
Immutable audit log
HMAC-SHA256HMAC-SHA256 (hash-based message authentication code)A tamper-evident fingerprint on each audit log row — change the record and the checksum no longer matches. row checksums. Monthly partitioning. Append-only at the database level.
GDPR GDPR (General Data Protection Regulation) The EU data-protection standard for consent, access, correction, and deletion — Tanzania's regime is aligned with it. · Art. 15–21
Consent records, data subject requests, automated anonymisation. Tanzania's data regime is GDPR GDPR (General Data Protection Regulation) The EU data-protection standard for consent, access, correction, and deletion — Tanzania's regime is aligned with it. -aligned.
TIPS-native payments
Routed through the Bank of Tanzania's Instant Payment System. One API, every wallet.
Security model
The same controls run through the whole loop.
Access, permissions, step-up checks, tenant isolation, and audit logs are not bolted on to one feature. They sit under the register, decisions, money, operations, communication, documents, and exports.
Read the security & compliance write-up- 01 · What you see
Role-based screens — owners, tenants, treasurers, and vendors each get only what their role allows.
- 02 · What can run
Role changes, votes, approvals, exports, and high-risk actions require the right authority.
- 03 · Where data lives
Each association is walled off. Another building's records cannot be reached from yours — by design, not by policy alone.
- 04 · What the auditor gets
An append-only trail — who acted, when, on what — sealed so tampering shows up immediately.
See the modules running together in your building.
Live walkthrough. Real test tenant. We'll move through the register, meeting, service-charge promise, facility request, notice, dispute, document, and audit trail as one connected system.