Releases and updates
How the application, the model and the rules reach your install: signed, verified before they run, and applied when you choose.
Updated 2026-10-16
Everything that reaches your install from Proxara is a signed release: the application, the model and the rules. Your install pulls it, checks it and runs it only if the check passes. Proxara never pushes anything in.
What a release is
| Release | What it carries | How often |
|---|---|---|
| Application | The install’s own software, as signed container images | When Proxara publishes one, applied when you choose |
| Model | The pinned model’s manifest and weights | Rarely, applied when you choose |
| Rules | The agency and lender rules as code, with their effective dates | Pulled hourly |
Checked before it runs
Each release is signed in Proxara’s build and verified inside your environment before anything in it runs. A release whose signature doesn’t verify is refused and the install keeps running the release it has. The install pulls from Proxara’s registry with a limited token that can read releases and nothing else.
You choose when
An application or model release waits until your administrator applies it, by running the same installer in place. If something isn’t right, the previous release is one command away. A rule release applies as it arrives because rules carry their own effective dates: a rule that takes effect next month is in the install today and is used from that date.
How a release is built
- Reviewed code: every change is reviewed before it is merged.
- Tested against the rules: every rule has its passing, failing and boundary cases, written from the published guide before the code that applies it. A change that gets any of them wrong doesn’t ship.
- A software bill of materials: every release lists each component and version it contains, from the base image to the packages inside it, in the signed package. Ask for the current one.
- A vulnerability check: every release is checked against published security advisories. A release with a known vulnerability that has a fix published is stopped before it ships.