Rent & ledgers
Charges, credits and running balances post to a per-unit ledger — every line traceable to the event that created it.
- →Automatic monthly rent posting
- →Split payments and partial balances
- →Arrears and aging views per unit
Platform overview
Rent, payments, maintenance, notices, documents and applications aren't separate tools bolted together — they're views into one append-only record per unit, running on infrastructure you control.
● Unit 4B · live viewExplore the modules
Charges, credits and running balances post to a per-unit ledger — every line traceable to the event that created it.
2024-06-01 · 09:14
Rent posted - June
$1,450.00 charged to Unit 4B ledger
2024-06-30 · 00:05
Balance rolled forward
$0.00 carried · unit current
The data model
Every module writes the same shape of record: an immutable, timestamped entry that references the unit and the actor. Corrections append a new entry that supersedes the old - nothing is edited in place.
How it runs
Pull the container image onto your servers or private cloud.
Create your one organisation and issue staff accounts.
Every action appends to the immutable Unit Timeline.
Data lives on your storage: export or back up anytime.
A closer look
drop product screenshots →
unit timelineRent, repairs, notices and signatures on one chronological rail per unit - scroll the whole history of a home.
event detailOpen a single entry to see the amount, actor and timestamp - and the original it corrects, if any.
Security & control
Isolation
No shared database, no cross-tenant queries, no other organisation's data in the same system as yours.
0 public sign-ups · you provision accounts
At rest and in transit, on keys you manage.
Staff, resident and read-only scopes per record.
Who did what, when - inherent to the timeline.
Ownership
Every timeline exports to open, portable formats. No lock-in, no data held hostage, no "contact us to retrieve your history." It runs on your storage; it leaves with you.


Where it runs every day
The same record follows a request from the resident who reports it, to the manager who approves it, to the tech who closes it - no re-keying, no lost context, no version that disagrees with another.
We'll walk you through every module on a private instance - self-hosted or managed. No public sign-up required.
no AI · one org per install · you own the storage