Deployment
On your hardware, on your terms.
No containers, no application server, no reverse-proxy project — three services, one database, one storage path, all on a single machine you already control.
- One server
- Windows or Linux
- Offline licence validation
- Browser-only clients
Architecture
One server, three services
Modalities talk DICOM to the node on 11112. Browsers talk HTTP/S to the application, which also serves the viewer — same origin, so there is no CORS configuration and no separate web server to maintain.
DICOM node
C-STORE · C-FINDMWL · MPPSlistens on :11112Application
DICOMweb · RESTserves the viewerHTTP/S :80 · :443Worker
thumbnailsasync jobsno external queueRequirements
What you need to have ready
| Item | Detail |
|---|---|
| ServerRecommended | Windows Server 2019+ / Windows 10+ or a current Linux distribution · 4+ CPU cores · 24 GB RAM · SSD for the database · bulk storage sized to study volume and retention policy. |
| Workstations | Any modern browser — Chrome, Edge, Firefox or Safari. No client installation, plug-in or Java runtime. WebGL2 is used for 3D rendering where available. |
| Network | Standard hospital LAN. Web traffic on port 80/443, DICOM on port 11112 (configurable). Works with or without a domain; TLS supported and recommended for clinical use. |
| Licensing | Signed, node-locked licence file validated offline — no internet connection required. Entitlements cover connected modality count and modality types, with optional modules per licence. |
Browser-only clients
Nothing to install, patch or license on the workstations.
Offline licensing
A signed, node-locked licence file — validated without an internet connection.
Fits your LAN
Works with or without a domain; TLS supported and recommended for clinical use.
Rollout
From installer to first read
A typical department is receiving studies the same day. The order matters more than the effort — each step is a configuration change, not a project.
Install
One installer on one machine brings up the DICOM node, the application and the worker against your PostgreSQL and storage path.Register modalities
Add each device by AE title, IP and port from the browser, then C-ECHO it to confirm connectivity — no service call.Connect the RIS
Point order push at the REST API so orders reach the modality worklist, and wire one-click study launch back into your RIS/EHR.Go live
Create users, assign roles, enable TLS, and read the first study in a browser tab on the workstations you already have.What you do not have to build
- No containers or orchestration to learn
- No Java application server
- No reverse-proxy project — the app serves the viewer itself
- No per-seat viewer licence and no per-study cloud fees
- No internet connection for licence validation
- No specialist on site to add a modality or a user
Specifications are indicative and subject to change without notice. Availability of individual features may depend on edition, licence entitlements, deployment configuration and the capabilities of connected modalities and third-party systems. Sizing guidance should be confirmed against your study volume and retention requirements. Regulatory status for diagnostic use varies by territory; please confirm the applicable status for your market before clinical use.
Request a demo
See it read your studies.
The fastest way to evaluate qPACS is to point a modality at it. We install a full working system, connect it to your equipment and walk your team through a live read — on your images, on your network.
- 01Connect a modality
- 02Send a study
- 03Read it in the browser