AuraPACS runs an on-premise node on the centre's own network. Modalities send to it, the browser viewer serves from it, and reports are written against it. A thin cloud layer adds remote viewing and an encrypted offsite copy, but the day's work never depends on the uplink.
An on-premise PACS keeps the archive, the DICOM receiver and the viewer on a machine inside your centre. Your CT, MR, X-ray or ultrasound sends each study to that node over the local network, the radiologist opens it in a browser from the same network, and the report is saved beside the images. None of that traffic leaves the building.
AuraPACS is built around exactly this node. The cloud layer sits on top for remote viewing and encrypted offsite backup, which is why the product is described as hybrid, but if the internet drops the node carries on receiving, storing and serving studies on its own.
The reasons are practical rather than ideological. A centre that scans all day cannot have its viewer stop because a fibre line was cut on the road outside.
A cloud-only system uploads each CT before anyone can read it, so a slow afternoon connection becomes a slow reporting afternoon.
When the connection fails the technician can still scan, but nobody can open, compare or report until it returns.
Images sit in a provider's storage under a per-study contract, and getting them back at the end is rarely simple.
Multi-slice CT and MR series are heavy. Pulling them down from a remote server is slower than reading from a machine in the next room.
Legacy on-premise systems needed installed viewer software on every reading PC, a server room and an engineer on call.
AuraPACS is installed on a Windows machine on your network and given an AE title and port.
Each scanner is configured to send DICOM to the node, the same way it would to any archive.
Images land automatically and are filed by patient, study and series.
Any authorised laptop on the local network opens the study with nothing installed.
The radiologist writes on a template and finalises a PDF against the study.
When the connection is up, an encrypted backup and remote-view copy sync to the cloud layer.
Workflow: The CT keeps sending to the node. The radiologist keeps opening studies from the reading room. Reports are finalised as usual.
Result: Only WhatsApp sharing and remote viewing wait for the connection to return.
Workflow: The study is served from the node over the local network rather than pulled from a remote server.
Result: Scrolling and windowing feel local because they are.
Workflow: Front desk searches the patient's history on the node and the prior opens beside today's scan.
Result: No CD to find, no upload to wait for.
Workflow: Images stay on hardware the centre bought, in a folder structure it can see.
Result: There is no per-study rent and no lock-in at renewal time.
Daily CT, MR and ultrasound volume that cannot pause for the ISP.
Casualty and wards need images available at 2 am regardless of connectivity.
Towns and outskirts where the uplink is shared and unreliable.
Centres that want to know exactly which machine holds their patients' images.
One capable person can install the node with remote guidance.
Yes. The on-premise node receives studies from the modalities, stores them and serves the browser viewer over your local network. Remote viewing, WhatsApp sharing and offsite backup need a connection, and they catch up when it returns.
A Windows machine on the centre's network with enough disk for your study volume. The demo installer is 200 KB and runs against the demo server; after activation by Site ID the full system runs on that machine. Sizing is agreed on a call based on your modalities.
It is the same product. The on-premise node is the foundation; the cloud layer adds remote viewing and encrypted backup. See hybrid PACS for how the two parts share the work.
You do. They are stored on your hardware, on your premises, and the encrypted backup copy exists so a disk failure does not cost you the archive. There is no per-study charge for keeping them.
No. The node is a single machine on the network. Heavy tasks such as offsite backup and remote access are handled by the cloud layer rather than by extra hardware at the centre.
Your own IT person, with remote guidance from Elevate Aura over WhatsApp and screen share. In Chennai the installation and modality connection can be done in person.
Tell us how you work today. We will show you what the platform would look like for you, and give you a clear scope and timeline.
Founder-led · Chennai, India · Built and supported by the person who wrote it