Architecture and residency.

Radial deploys as an on-premise appliance with a browser UI and no cloud dependency. Patient data stays inside your network — the trust posture is a fact of the architecture, not a policy promise.

The shape of the system

Under the browser UI, Radial is a web application backed by a relational database, a built-in DICOM service, and background workers that handle imports, computation, and ambient monitoring. It installs on hardware or a VM your institution controls, and clinicians reach it like any internal web tool, with nothing to install at the desk.

Residency, literally

Every component runs inside your network: the database, the imported studies, the computed metrics, and the UI serving them. Radial does not sync patient data to any vendor cloud and runs without internet access. After the one-time container-image pull at install, nothing in the platform needs a connection. One disclosure, because this page is a trust document: current builds of the browser UI include crash-and-error reporting (Sentry) that fires only if a workstation's browser can reach the internet. The server, workers, and database make no outbound calls, and a disconnected deployment sends nothing at all.

A procurement-friendly footprint

There is no GPU requirement and no per-seat cloud subscription shape. The appliance runs on ordinary server hardware, which tends to fit equipment budgets and research-computing environments better than a data-egress conversation with a review board.