Don’t take our word for it — open DevTools and watch the Network tab while you work.
- ✓Intended viewer workflows keep images browser-local — verify ordinary traffic in your DevTools Network tab
- ✓AI segmentation runs in your browser — no upload, no GPU server, no queue
- ✓DICOMweb connections you configure go directly from your browser to your PACS, with no proxy in between. The built-in demonstration connection, “Orthanc Demo (UCLouvain)”, is the exception: its requests go to the website that serves the viewer, which relays them to a public demonstration server. It is read-only, and the viewer labels it “Public demonstration server — do not enter or send patient data”
- ✓DICOM files are parsed and rendered entirely in the browser
- ✓Annotations, measurements and reports are stored locally — as plain files on disk once you connect a data directory — with no routine ImagiVue cloud upload
- ✓The cloud serves application code and AI model weights, and relays DICOMweb requests only for the built-in demonstration connection — no analytics or tracking pixels touch patient data
Cloud (No PHI)
CDN → App Code + AI Model Weights
Auth Service → Account Management Only
↓ Internet ↓Your Browser
DICOM Parser → WebGPU Renderer
ONNX Runtime Web → AI Models
Annotations → IndexedDB
↓ Direct Connection (bypasses our cloud) ↓Hospital PACS
DICOMweb ←→ Browser (direct)