Architecture
Every part of an install, where it runs and what it holds, and the two ways to host it: your Azure subscription or your own servers.
Updated 2026-10-18
An install is one private deployment in your own Azure subscription, created by one installer that your IT runs under its own permissions. Every resource it creates is yours: the network, the GPU, the storage, the keys and the logs. Nothing in it is shared with Proxara or with another lender.
Your Azure tenant
Microsoft sign-in
What runs where
| Part | Where it runs | What it holds |
|---|---|---|
| Proxara’s screen and its API | Your tenant, behind your sign-in, opened from inside the loan in Encompass or Arive | Nothing of its own |
| Document processing | Your tenant | Page images and their text, while the loan is worked |
| The model | Your GPU, in your private network, with no route out | Nothing. It reads a page and returns what it read. |
| Rules engine | Your tenant | The published agency and lender rules, as signed releases |
| Encrypted store | Your storage account | The loan’s files, facts and state while it is worked |
| Logs | Your tenant | Who did what, and when. Never document text or borrower details. |
| Keys and secrets | Your Key Vault | Every key and credential the install uses |
| File scanner | Your tenant | Signatures only. Every file is scanned before it opens. |
How a loan moves through it
- A loan is created in Encompass or Arive. Proxara starts on it and takes the loan file and each document as it lands, with your own credentials. Each file is scanned before it opens.
- The model reads each page on your GPU and returns each fact with the words on the page it came from. Code checks every fact against those words.
- Code works out the qualifying income, checks every published limit and finds the change that clears them, citing the rule behind each number. The income goes into the loan’s own fields.
- A decision that is the loan officer’s reaches them as a task in the loan. The task opens Proxara inside the loan, as a Custom Tool in Encompass, signed in through Encompass or your Microsoft Entra ID.
- Proxara enters the chosen change in the loan and runs DU or LP through your own Encompass or your lender’s portal, with your credentials. The findings come back to the same loan.
- The results stay in your LOS: the income, the structure and the result PDF in the eFolder.
- When the loan officer closes the loan, or after 90 days untouched, the working copies are deleted. The results stay in your LOS.
Two ways to host it
In your Azure subscription. The usual way. The installer checks your region, GPU quota, permissions and network policy before it creates anything, then prints each stage as it runs and the address of the finished install. Installation has the detail.
On your own servers. For an additional fee. The same signed release runs on a GPU server in your office or data center, with the same controls. The boundary is then your own network, and nothing in the install needs Azure.
What Proxara runs on its own side
Two things, and neither receives anything from your install. The release registry holds the signed releases your install pulls. Rule authoring turns each agency guide into code from a dated copy of the published text, with the quote, the citation and the tests behind every rule. Both run in Proxara’s own Azure subscription.