OpenLOSFor wholesale lenders, credit unions, and banks
Publish your rate sheet once. Every approved broker gets it live.
ORSF Publisher is a free, open-source app you run in your own account. Upload the rate sheet you already produce, give each approved broker an access key, and their systems price from your current sheet, signed by you. Nobody re-keys it, and your rates never pass through anyone else's servers.
How it works
Deploy it in your own account
One click on Render, or a Docker container behind your existing HTTPS. A signing key is created automatically and kept on your server.
Upload today's sheet
Your usual Excel or CSV, read with a one-time layout template, or an ORSF file from your pricing engine. The template says where things are on your sheet; it never contains prices.
Approve brokers
Each broker shop gets its own access key. Revoke one any time, and see when each last checked.
Brokers price from your current sheet
Their systems check every few minutes, verify your signature, and price only from sheets you published and haven't expired.
Why publish this way
What brokers see is what you published
Every sheet is signed (Ed25519) over its exact bytes. No transcription errors, no stale PDFs.
Your data stays yours
The feed runs on your server. There's no central hub, aggregator, or middleman in between, and no one resells your pricing.
You control access
Pricing is confidential between you and your approved brokers. Per-broker keys, revocable instantly.
Free and open
Apache-2.0 code and a CC BY 4.0 spec. Use the app, build it into your own systems, or implement the spec in any language.
Programs and eligibility
Base price grids by lock period, adjustment grids and rules, caps, and programs including high-balance, jumbo, and non-QM.
Works with any system
OpenLOS reads it today. Any pricing engine or LOS can, from a documented standard.
Where it stands
ORSF is a draft standard (rate sheet v0.2, Feed API v0.1), and both projects are early. Planned next: reprice notifications, promotions, lock extensions and relocks, then live quote and lock APIs.
If you're in secondary marketing or on a lender technology team, your input decides what comes next. What would stop you from publishing this way? Open an issue or start a discussion.