BTR OS

Build-to-rent operators need operational intelligence they own. Compliance evidence still needs a person's sign-off.

I designed BTR OS and its operator console. I offer a one-building design-partner pilot.

These are on the console today:

A Blazor operator console designed to run in Azure's Australian regions. Staff log in with email and password, with role-based access and an audit trail.

Residents, units and leases.

Resident documents with review states.

Service requests.

Amenities and bookings.

Payments through a commercial payments provider.

Operator analytics for the selected site.

Access control through a built integration with a commercial access-control platform. The vendor is not named here.

A tool server with access-control tools behind a key. No model is wired, and nothing in the product calls those tools on its own.

BTR OS is ready for a one-building design-partner pilot.

The compliance-evidence module is not built yet; the pilot is the work that delivers it. It tracks a building's compliance deadlines, collects the evidence, and has a person approve it before anything is filed.

Planned, not live: bulk import, live connections to leasing systems, and a governed agent layer where a person approves each step.