Questions

Not for real borrowers yet. It's alpha: the full 1003, pricing, compliance basics (a TRID clock, NMLS license checks, Section 8), and security basics work, but it hasn't had an independent security review, and direct credit-vendor and DU/LPA connections and lender integrations are still on the roadmap. Try the demo and tell us what's missing for your shop.

An independent developer publishing under the name greenstripe7, and anyone who contributes. Pseudonymous maintainers are common in open source; what matters is that everything can be checked. There's no company and nothing for sale. Everything is in public: the code, the specs, the history of every change, and the decisions in the roadmap. Judge it by what's there, and verify the releases.

The licenses guarantee anyone can fork and continue both projects, and every line of code, spec text, and decision is public. The governance document spells out the continuity plan.

It isn't, beyond the maintainers' time. The software is free and open source. The project accepts small donations and takes no money from lenders or settlement service providers, so it can't be paid to favor anyone.

Only in your own copy. Each shop runs OpenLOS in its own account or on its own server, with its own database and encryption key. SSNs, dates of birth, documents, and two-step secrets are encrypted at rest. The project never hosts borrower data; the public demo holds fictional data only.

No. With ORSF, pricing goes directly from the lender's server to each approved broker's copy, signed by the lender. Spreadsheet templates hold layout only, never prices, so they can be shared safely.

Never. Anti-steering rules (Reg Z §1026.36(e)) forbid steering a borrower to a loan because it pays the originator more. OpenLOS ranks only by what the borrower pays, blocks dual compensation, and archives the loan options disclosure from real pricing.

The software is free. Hosting is whatever your provider charges; a small shop on Render is about $18 a month, paid to Render.

OpenLOS is AGPL-3.0: use and change it freely; if you offer a modified version to others over a network, you share your changes. ORSF's specification is CC BY 4.0 and its code is Apache-2.0, so any product, open or closed, can implement it.

Privately, as described in the security policy. Please don't open a public issue for a vulnerability.

Try the demo and say what's missing. If you run a broker shop, review the workflow. If you work on a lender's secondary or technology team, read the ORSF spec and say what would stop you from publishing. Developers: issues labeled good first issue.