Compare
Where Dicomly fits
in your stack
Dicomly doesn't really compete with storage, PACS, or routers — it sitsin front of all of them. Storage is the easy part; receiving DICOM from a hospital is the hard part. Dicomly does the hard part, then hands you the bytes over plain HTTPS — keep them wherever you like.
Cloud DICOM stores
AWS HealthImaging · Azure DICOM Service · Google Cloud Healthcare API
Durable storage and DICOMweb APIs for images that have already arrived.
The gapYou still build and operate the C-STORE receiver, manage certificates, and run ingestion. They store; they don’t connect.
When it fitsGreat as the place you keep studies — after Dicomly delivers them to you.
Cloud PACS platforms
PostDICOM · Medicai · Ambra · Intelerad
Full PACS: storage, a diagnostic viewer, sharing, and workflow — sold to radiology groups.
The gapA whole platform to adopt, usually enterprise sales, and not API-first. Overkill if you just need DICOM arriving in your own product.
When it fitsRight choice if you need a viewer and clinical workflow, not a connectivity layer.
On-prem / self-managed routing
Laurel Bridge Navigator · Rhapsody · Orthanc
Powerful DICOM routers and integration engines you install and run yourself.
The gapYou own the servers, scaling, patching, and certificate lifecycle. No self-serve REST provisioning, no managed mTLS, no SaaS model.
When it fitsRight choice when you need full on-prem control and have the team to operate it.
Side by side
| Cloud stores | Cloud PACS | On-prem routing | Dicomly | |
|---|---|---|---|---|
| Category | Storage archive | Full PACS + viewer | Router / engine | Connectivity layer |
| You build the C-STORE receiver | Yes | N/A (their app) | You run it | No |
| Managed mTLS / cert lifecycle | No | Partial | No (DIY) | Yes |
| Stores your PHI | Yes | Yes | Yes | No — nothing at rest |
| Self-serve REST provisioning | Build it | Limited | No | Yes |
| Delivery to your app | Pull via SDK | Within platform | You configure | HTTPS POST (STOW-RS) |
Dicomly pricing is two numbers: €10 / endpoint / month and€0.15 / GB delivered. No metered instance fees, no seats, no tiers.See full pricing →
When Dicomly is not the right tool
We'd rather you pick the right thing than churn. Dicomly is a narrow connectivity layer — if what you need is something else, use something else:
- You need long-term image storage or an archive → use a cloud DICOM store (and let Dicomly deliver into it).
- You need a diagnostic viewer or clinical workflow → use a cloud PACS platform.
- You need full on-prem control of routing → run an engine like Orthanc yourself.
- You need DICOM tag normalization or de-identification → Dicomly never parses tags; do that in your own pipeline after delivery.
Need to receive DICOM from hospitals into your product, without running DICOM infrastructure? That's exactly what Dicomly is for.
Start receiving DICOM today.
Early access. No credit card. First endpoint free.