RentRedi
Property management platform for landlords with rent collection, tenant screening, and maintenance tools.
RentRedi is rebuilding around multi-property operators, with its first model-facing feature at the tenant boundary.
◆Recent moves
- 6d ago
Notification Preferences: Choose What You Get and How
A single Notification Settings page groups every notification by subject and lets each one be routed to email, push, or off entirely, with the record still kept in the notification bell. The natural consequence of a product that has added portfolios, leases, documents and maintenance triage in quick succession: more events to be told about, and a need to choose.
- 7d ago
Edit Leases & Convert to Month-to-Month
Leases can now be edited in place and converted to month-to-month, with paid charges preserved and unpaid future charges updated to match. It removes a delete-and-recreate workaround, which is characteristic of the lifecycle gaps RentRedi has been closing.
- 12d ago
AI Maintenance Helper: Faster, Clearer Maintenance Requests
⚡ SPARKThis is RentRedi's first model-facing feature and the clearest change of direction in the window. It sits at the tenant boundary, where the product previously accepted whatever text arrived, and it feeds structured output into the landlord's queue.
- 13d ago
Global Documents Tab & Folders for Better Document Organization
A global Documents tab makes every uploaded file searchable in one list, with folders on properties and tenant profiles and a place for business-level documents. Another instance of the product accommodating operators whose records do not belong to a single unit.
- 15d ago
Restyled Chat View with Unit & Tenant Displays
Chat gets unread counts in the side navigation, a split list-and-conversation view, attachments on the first message, and unit and tenant context on each thread. A UX overhaul of a surface that becomes harder to manage as portfolios grow.
- 1mo ago
Introducing Portfolios
⚡ SPARKPortfolios introduced the grouping primitive the rest of the product has been building on since — the Performance rollups and document organisation both assume it. It marked the point where RentRedi started treating multi-entity operators as the default user.