Skip to content
Security

Boring on purpose.

Last updated: July 9, 2026

A mortgage platform holds the most sensitive consumer data there is. Our posture is conservative and unexciting: keep secrets off the client, keep data minimal, keep tenants apart, keep records append-only, and fail closed when anything is ambiguous.

Credentials never reach the browser

Every vendor call — credit, pricing, valuation, compliance, LOS — executes server-side. API keys and OAuth secrets live in managed environment configuration and vaults; no key ships in client code, ever. The server decides simulated-versus-live, so a misconfigured client cannot fake a live result.

Data minimization

The platform stores references and statuses, not vendor payloads: a service order keeps its transaction id, timestamp, actor, and status — the full record lives in your LOS’s document store where it belongs. Analytics events carry outcomes and signals, never SSNs or documents.

Tenant isolation

White-label tenants are isolated at the database layer with row-level security, separated infrastructure per product line, and per-tenant configuration for brand, programs, and vendor connections. One lender’s data is structurally invisible to another’s.

Append-only records

Attribution ledgers and milestone events are written once — corrections append, never overwrite. Combined with deterministic math, any disclosed scenario can be replayed and any record explained.

Fail-closed everywhere

The same reflex runs through the whole platform: the disclosure gate holds on ambiguity, scheduled jobs reject unauthenticated callers, and the pre-launch access wall denies by default if its own configuration goes missing.

Compliance path

Infrastructure isolation and control discipline are maintained with a SOC 2 audit path in view; security review artifacts and architecture documentation are available to serious evaluators under NDA.

Questions we welcome

  • Where does each category of borrower data live, and for how long?
  • Show us the path of a credit pull — who holds the credentials at each hop?
  • What happens to the file when a vendor errors mid-order?
  • How is a white-label tenant prevented from reading another tenant’s rows?

These are the right questions, and the walkthrough answers them with the actual system, not a slide. Bring your security team →

Ask us the failure-mode questions.