Built for Organizations That Manage Complexity
For organizations where more than one team touches the portfolio, and where who can do what has to be provable rather than assumed.
Enterprise Control Without Operational Friction
Most platforms describe their security. Ours is asserted automatically on every build — if a change would let one organization see another's data, the build fails and the change does not ship.
Isolation you can verify
One organization's data cannot be reached from another. It is enforced by the database itself, and a gate proves it on every build by trying to break it and failing.
Roles separated from scope
A role says what someone may do; an assignment says where. A closed catalogue of permissions means a role cannot be invented past what the system allows.
An immutable ledger
Financial records are append-only and double-entry, with a conservation check asserted on every build. Corrections are new records, never edits.
Every action attributable
Who did what, when, and to which record — including support access, which is logged like everything else.
Sessions that can be revoked
Access is a record that can be withdrawn, not a token that has to expire on its own.
Multi-region by design
Region-specific vocabulary, payment methods, tax artefacts and consent rules — a US portfolio and an India portfolio behave the way each market expects.
Built for a Multi-Region Operating Model
Not one product translated. Property vocabulary, payment methods, tax artefacts, date formats and consent rules differ by market, and the platform carries the difference so your team does not have to remember it.
Modelled means the platform carries that market's vocabulary, tax artefacts, deposit rules and consent regime — not that money is moving. No payment rail is live in any market yet. What runs today is set out in full on the roadmap.
Transition Your Portfolio With Confidence
Import handles structured files today — spreadsheets and system exports. Every input row lands in either the imported set or the error list; nothing is ever silently dropped, and a dry run writes nothing at all.
- 1 Discover — we look at what you actually have — spreadsheets, exports, whatever the last system produced.
- 2 Map — your columns to properties, units, tenants, leases and balances.
- 3 Clean — errors come back as a list of rows to fix, never as a silent drop.
- 4 Validate — a dry run writes nothing and shows you exactly what would land.
- 5 Migrate — valid rows import; anything invalid is reported rather than guessed at.
- 6 Verify — you check the imported book against your own before it goes live.
- 7 Go live — the first rent run goes out — that is the moment that has to be right.
Your Property Platform Should Not Exist in Isolation
Modern businesses run on several systems. These are the connections we intend to build. To be plain: none of them is available today.
Payment integrations
Payment infrastructure and region-specific payment workflows.
Accounting integrations
Connect property and transaction information with your financial systems.
Identity integrations
Enterprise authentication and identity management.
Communication integrations
Email, SMS, notifications and messaging.
Analytics integrations
Connect operational information to enterprise BI and reporting platforms.
CRM integrations
Connect customer and prospect relationships where required.
Build on a Connected Technology Foundation
Enterprise organizations often need property information inside their own applications. The API is in design; there is nothing to call yet. These are the domains it would expose:
Connect your systems. Extend your workflows. Build around your data — when it exists.
See everything that is built and everything that is not →Managed Implementation for a Seamless Transition
A transition that works is a managed one, shaped around how the organisation actually operates. Seven steps, in this order.
- 1 Configure — organisation, users, roles, properties, portfolios and workflows.
- 2 Import — bring the existing book in — and check it before anything goes live.
- 3 Connect — configure what needs connecting. Note that third-party integrations are not available yet.
- 4 Customize — business rules and operational workflows set to your practice, not ours.
- 5 Train — the people who will use it daily, and the administrators who will govern it.
- 6 Validate — run the operational checks before a single tenant sees anything.
- 7 Launch — go live as a controlled transition rather than a switch-flip.
Transform Your Property Operation
The software is the smaller half. These are the managed services around the transition — availability depends on portfolio size and our onboarding capacity.
Platform configuration
Set the environment up around how your operation actually runs, rather than making you fit ours.
Data migration
Move and validate the existing portfolio — properties, units, tenants, leases and open balances.
Workflow design
Translate the manual processes your team already follows into workflows that run themselves.
User enablement
Train the people who will use it daily, and the administrators who will govern it.
Adoption
Help the operation settle into consistent practice, which is where most platform changes actually fail.
Let's Talk About Your Portfolio
Tell us how many properties, how many people and how many regions — we will tell you what fits and what does not.