# Proxara Technologies > Proxara does the file work a mortgage business does by hand, from the documents it already holds. Models only read pages and match; code computes every number and assembles every output. Nothing borrower-identifying leaves the customer's environment. The real AUS, HUD and the customer's own people make every decision. Proxara Technologies makes software for two kinds of mortgage business. Each has its own site. ## Proxara for lenders and broker shops Proxara gets a mortgage file to approval by itself. The loan officer talks to the borrower; Proxara does the file, from the first document to clear to close. It works out the qualifying income under the rules of every program the shop offers (Fannie Mae, Freddie Mac, FHA and VA; a lender's own overlay once that lender's document is on file). It finds the best loans this borrower can get, compares every program and structure and ranks the ones that work by the borrower's cash, the monthly payment and how little has to change; the borrower chooses. It clears every published limit before anyone submits, with one combined change where several fail, so the first submission is built to be the last. It submits the loan through the lender's own access, and when DU or LP comes back with something only the AUS can judge, it works the answer within seconds, round after round, until the loan is approved. It matches every underwriter condition to the document that clears it, asks the borrower in plain words for what is missing, and watches the file until closing: a low appraisal, a rate move or a document going out of date is caught the day it happens and the loan is fixed again. The real AUS judges; nothing is called approved until DU or LP says so. It works inside the systems the shop already uses and runs in the shop's own cloud. - [Proxara for lenders](https://proxara.ai/lenders): the product on one page. - [How it works, for lenders](https://proxara.ai/lenders/how-it-works): one loan from its first document to clear to close. - [Structuring](https://proxara.ai/lenders/structuring): every published limit checked before DU or LPA sees the loan, the loan file answering its own questions, and the changes that clear every limit at once, ranked for the borrower. - [See it in action](https://proxara.ai/lenders/see-it): a walkthrough of one loan, the free sandbox with sample loans (it opens its own sign-in in a new tab), or a call to walk a loan through it. - [Security, for lenders](https://proxara.ai/security): for a lender's IT. Borrower files stay in the lender's own Azure account; what the installer creates, the pinned model, who can open a loan, every outbound destination, and the questions security teams ask. ## Proxara for servicers Proxara finds every extension a servicer's defaulted FHA loans are entitled to and applies it while the loan is still in default, so the dates on the HUD-27011 are the extended ones and the documentation HUD requires is already in the claim file. It reads the bankruptcy feed, the attorney record, the loss-mitigation history and the court record. It runs in the servicer's own Azure tenant off the MSP files it already receives, and writes the extended dates and holds into MSP's own fields, with a note saying why, and the claim into the claims system, so nobody opens anything new. Automatic extensions are applied without a task; a question reaches the team only when a fact is missing or the extension is theirs to decide, and a lender employee certifies the claim. It starts with a Docket Run: the servicer's own live FHA foreclosures in one county, reconstructed from the public court record, with the page each date came from, before anything of the servicer's is shared. - [Proxara for servicers](https://proxara.ai/servicers): the extension position on every live FHA default; type the company name and we run the public docket. - [How it works, for servicers](https://proxara.ai/servicers/how-it-works): one case from the docket to the claim file. - [Sample](https://proxara.ai/servicers/sample): the Docket Run report on one live FHA foreclosure, and what lands in MSP, SharePoint, the morning email and the claim once it runs. - [Update 18](https://proxara.ai/servicers/update-18): what Handbook 4000.1 Update 18 changes on 10 November 2026, and what the claim file has to carry. - [Security and IT, for servicers](https://proxara.ai/servicers/security): the installer, what it connects to, the reader with no route to the internet, the named hosts, and what it costs to run. ## Shared - [Company](https://proxara.ai/company): who is building it and how to reach them. - [Blog](https://proxara.ai/blog): how the income is worked out in code, how a findings report is read and worked round by round, what stays in the lender's tenant, and the one installer. - [Trust Center](https://proxara.ai/docs/trust-center/overview): the site policies and the security overview. - [Servicer review pack](https://proxara.ai/docs/servicers/data-statement): the data statement, the egress manifest, the installer and the integrations, as a servicer's compliance and IT teams read them. - [Lender guides](https://proxara.ai/docs/lenders/overview): the lender workspace, one loan from the first drop to approval, what changes for a leader, the rules and evidence, installation and integrations. ## Boundary For lenders, Proxara submits the loan to DU or LP through the lender's own access and never calls a loan approved until the AUS says so; it never produces an adverse action. For servicers, people answer what the record cannot settle and certify the claim; the system prepares the claim and never submits it. Corrections are kept as history, never overwritten. Findings from public records say what the record shows, not what a company did internally; a gap is an unexplained lapse, never a loss.