Outbound only
Makes HTTPS calls out to Aegis and opens no inbound ports, so nothing in your network is exposed to the public internet.
On-prem connector
Run Aegis inside your network.
For hospitals whose PACS cannot be exposed to the internet. A lightweight connector runs on your side, reaches out to Aegis, and fulfills approved requests from your local imaging, with no inbound ports and no PHI sitting in the cloud until it is requested.
Windows, ~14 MB
Zero dependencies
A single executable. Nothing to compile, no database. Run it directly or as a Windows service / systemd unit.
Request-driven
Only releases the specific patient that was requested and approved, never bulk-pushes. Unmatched requests are left for review.
Managed updates
The connector reports its version and health to the Aegis console, which can push config, trigger a restart, and roll out signed updates.
Install
Up and running in four steps.
- 01
Unzip inside your network
On a machine that can read your imaging exports. The Windows build needs no Node.js install.
- 02
Activate
Enter your issued
serialinconfig.json. The connector activates and receives a scoped key automatically. - 03
Point it at your studies
Drop DICOM into the
dicom/folder (or connect your PACS export). Synthetic data only in the demo. - 04
Run
Double-click
aegis-agent.exe. It polls your request queue and fulfills approved requests automatically, or install it as a Windows service.
Need help deploying it?
We'll help you run the connector as a managed service inside your own cloud or on-prem boundary.