Built to be examined.
REOMind is designed for institutions that answer to examiners, boards and auditors. Here is how it handles decisions, data and AI, and what we do not claim yet.
AI recommends. People decide. Everything is recorded.
Disposition path, list price, investor outreach and overrides require an authorized human decision. Agents cannot approve their own recommendations.
Rejecting or overriding a recommendation requires a written reason, stored with the decision.
Human, agent and system events are written to an activity log tied to the asset and institution. A failed log write is surfaced, never silently dropped.
If two reviewers act at once, only the first decision is recorded and the second is told to refresh.
Each institution sees only its own data.
Every asset belongs to an institution. Users can read only institutions where they hold an active membership; platform administrators are the exception, by design.
From executive and REO manager to compliance officer, valuation reviewer, broker, investor, analyst and read-only auditor, each with explicit permissions.
Automated tests cover institution isolation, who may approve, outreach approval, and read-only auditors.
Periodic access review reports and single sign-on for institutions.
Decision support with a visible evidence trail.
Source data, agent analysis and human decisions are displayed separately on every asset.
Agent findings carry their sources and the date of the data they used.
Agent runs on an institution record the agent version, method, models used and the code build in the audit trail, so each recommendation traces to the logic that produced it.
Make legal determinations, approve compliance matters, bind an institution, send outreach without approval, or change a valuation without recording why.
Plain facts about where data lives.
- • Hosted on Vercel (application) and Neon Postgres (database). Data is encrypted in transit (TLS) and at rest by those providers.
- • Nightly encrypted database backups are kept off-platform, and restores are tested.
- • Secrets and API keys stay on the server and are never sent to the browser.
- • We ask institutions not to send loan tapes or borrower data by email; we arrange a secure transfer.
No certifications we haven’t earned.
REOMind is not SOC 2 certified today and has not been approved by any regulator. We describe controls as “designed to support” institutional governance, not as compliance guarantees. A SOC 2 readiness program is on the roadmap, and we will say so plainly when it is complete. Our vendor-due-diligence materials are available on request.
Bring your vendor-management questions.
We’ll walk your compliance and risk teams through the controls, the audit trail and the roadmap.