Deployment
Self-hosted, on infrastructure you already run
No multi-tenant service, no vendor copy of your studies, and no requirement to send imaging data anywhere you did not choose.
The shape of it
One Windows service
A single deployable service hosting the DICOM SCP, the HL7 listeners, the routing workers, the API, and the management UI. Not a fleet of components to sequence.
PostgreSQL behind it
Configuration, routing state, durable job queues, and the audit log live in PostgreSQL. Your database, your backup policy, your retention.
Runtime state outside the install
Bootstrap config, secrets, logs, staging, and data live under ProgramData rather than inside the application directory, so an upgrade does not walk over them.
Browser-managed
Everything operational is configured in the console - interfaces, rules, destinations, schedules, certificates - without editing a file on the server or restarting the service.
Scaling
Grow by adding nodes, not by rewriting the design
Single node
The normal starting point, and where most installs stay. One service, one database, as many interfaces and rule sets as the environment needs.
Multiple routers, one database
Several routers can share one PostgreSQL behind a load balancer. Study completion, routing, and every scheduled poller claim their work, so nothing fires or sends twice. Talk to us about the limits before designing around it.
Remote sites
Sites you do not control get a Remote Gateway rather than a second full install - outbound-only, managed centrally, spooling locally when the link is down.
Getting started
What an evaluation looks like
Scope the connections
What sends, what receives, and over which protocols. This is the conversation that decides everything else, and it is usually short.
Stand it up on your infrastructure
Evaluations run in your environment against your modalities. A demo on our hardware answers a question nobody asked.
Import or author the rules
Bring a Compass or Unifier export and import it, or build the rule sets from scratch in the console. Imported configuration lands disabled.
Cut over deliberately
Enable interfaces and rules one at a time, with the routing decision record and System Health showing what each change actually did.
Licensing and installers
Issued through the customer portal
Licences, signed installers, and release notes are distributed from the customer portal at dicomassist.app. Licensing is per deployment with capability licensing for optional modules - there is no per-study or per-image metering.
Sign-in happens on the portal's own origin. This marketing site never asks for your credentials, and no link here will ever ask you to enter them.
Ready to scope a deployment?
Tell us what has to connect to what. We will tell you what it takes, including the parts that are not ready.
Request a demo