Installation
One installer, run by your administrator in your own Azure account. What it creates, what it verifies, and what never leaves.
Updated 2026-09-26
Installation
One installer, run once by your administrator, in your own Azure account. Every resource it creates belongs to you: the network, the compute, the storage, the keys and the logs. Proxara holds no credential, no role and no standing access.
Before it creates anything
Preflight checks the GPU quota for the serverless A100 profile, the region, the permissions the installer will use, your network policy, the model licence, and the complete monthly price. A missing quota or an incompatible policy is a named blocker; the installer stops and says which. The quote shows every known price and any item still to be confirmed.
What it creates
One right-sized compute slot, and around it what that slot needs:
- the authenticated page and its API, one local model server, the local OCR and parser, a virus scanner that checks every file before anything opens it, the mortgage modules, the work queue and the store
- encrypted Files shares for the model weights, the working files, and, separately, your result PDFs
- Key Vault for every secret
- logging of loan tokens, component versions, timings, rule identifiers and error classes, and a logged deletion when a loan ends
Inference is loopback only. One HTTPS address is reachable: the page, behind your tenant's sign-on, and the API for your own systems, behind a key one of your specialists issued.
Operating hours
The model runs on a serverless A100 profile billed per second while awake, about USD 2.16 an hour, and costs nothing while stopped except storage. The hours are an install choice, and the preflight quote prices each one, all in, on a 31-day month before tax. Always on is shown for comparison.
| Window | About, per month |
|---|---|
| 06:00 to 20:00 Eastern | USD 992 |
| 06:00 to 22:00 Eastern | USD 1,126 |
| Always on | USD 1,663 |
A wake takes about twenty minutes today. Unfinished work is checkpointed before the stop and resumed after the start.
Updates and support
Proxara publishes signed releases of the application, the model manifest and the rulebook. Your tenant pulls each with its limited token, verifies the signature, and upgrades in place under its own identity. A private health endpoint and a diagnostics bundle expose versions, timings, rule identifiers, error classes and health state, and your IT exports the bundle when support needs it.
The same package runs on a GPU host you have prepared. The security overview says the same in the words a security team asks for.