The questions a diligence reviewer asks first, answered on the page rather than in the third meeting.
Galinstan is built as software you install and run inside your own perimeter. There is no tenancy and no console on our side.
What leaves. Nothing, by design. The software never connects to the internet: not for licensing, not for telemetry, not for model weights, not for updates. It is built to run on a machine with no route to the internet, and it has nothing to reach if it is given one.
What you buy. Galinstan is built to run on hardware you already know how to procure.
What we are to your register. We license Galinstan annually with support, patches and calibration. None of your data reaches us, and no part of the analysis depends on us being reachable.
Upgrades. Every version is cut as a signed release: an offline bundle with a checksum for every file and a software bill of materials. It installs with no package index and no network, and the instance never reaches out for it.
Escrow and exit. Every release is built to be deposited: source, bundle and checksums as one versioned artefact. We agree escrow and exit terms in the contract rather than pointing at a policy page.
Who does what. We follow a shared responsibility model, as cloud providers do. We are responsible for the correctness of the evidence: the regulatory parameters read from the primary text, the calculations, the reconciliations to what you report, and the signed software that produces them, each with evidence your reviewer can re-perform. You are responsible for the perimeter it runs in, the data you give it, and the decisions and submissions you make on it. Calibration and updates are shared: we supply them, and you approve and install them. Together, the two complete the steps each regulation asks for.