A .NET operator console
A Blazor console designed to run in Azure's Australian regions. Staff log in with email and password. Role-based access and an audit trail keep the change. Hosting is confirmed per deployment.
BTR OS
Build-to-rent operational intelligence, owned by you.
It starts with compliance: a fixed-fee pilot for one building that tracks your deadlines and needs a person's sign-off on every filing. Your data and the system stay yours.
Fixed-fee pilots, scoped per building.
The pilot
What the one-building pilot delivers.
Not shipping today.
The compliance-evidence module is not built yet. The one-building pilot is the work that delivers it.
The pilot is a human-approved works and compliance evidence layer. It tracks a building's recurring compliance deadlines, collects the evidence from your existing exports and records, and has a person approve it before it is filed.
That includes evidence an operator may need to keep for NSW land tax concessions, such as whether three-year leases were offered, ATO build-to-rent obligations, and Victorian minimum-standards and safety-check records. This is not legal advice. It is a record of evidence the operator needs to keep.
Now taking design partners for a one-building pilot. Fixed-fee pilots, scoped per building.
Roadmap
What exists, and what is next.
On the console today.
Access control
Credentials, doors, events and visitor passes through a built integration with a commercial access-control platform. The vendor is not named here.
Residents, units and leases
A roster of who lives where, with unit records and tenancy terms. Operators add and edit one record at a time.
Documents
Resident documents with pending, approved and rejected states. Types are lease, identity, insurance and other.
Service requests
Maintenance and resident requests with open, in progress, resolved and closed states. There is no due date or SLA.
Amenities and bookings
Bookable shared spaces with capacity rules. Reservations sit on a bookings screen.
Payments
Rent and amenity charges through a wired commercial payments provider. The provider is not named here.
Operator analytics
Current occupancy, arrears, amenity and access counts for the selected site. There is no export or board pack.
Governed access tools
A tool server with forty-seven access-control tools behind a key. No model is wired. Nothing in the product calls those tools on its own.
Planned, not live.
- Bulk import of units, residents and tenancies: not built. The pilot starts from existing exports and uploads.
- Live connections to leasing systems: not built. Those stay later, using access the customer already has.
- A governed agent layer: designed for governed AI agents with a person approving. No model is wired into the product today. Agents do not run the building.
Product screens
The operator console.
Table crops from the running build. Demo dataset. Names, units and amounts are sample data.
Open full-size view
Open full-size view
Open full-size view
Open full-size viewSwipe for the next crop.
How I build sits on the platform page.
Microsoft and Azure are trademarks of their owners. ARK360 is an independent company.