About
DICOM connectivity
as a service
Any product that needs to receive DICOM data — from a hospital, an imaging center, a research lab, a modality, or an OEM device — needs DICOM connectivity. Dicomly makes that a one-API-call problem.
What we do
Dicomly is a stateless DICOM connectivity gateway for software teams. Companies building AI tools, EHR integrations, teleradiology platforms, research pipelines, or OEM device software use Dicomly to receive DICOM data — of any kind, from any source — without running DICOM infrastructure themselves.
You make one API call to create an endpoint — one destination URL.
That same call provisions a mutual-TLS client certificate bound to the endpoint.
You deliver the certificate to the sender through your own onboarding process.
The sender configures their PACS, modality, archive, or device to send DICOM C-STORE to
dicom.dicomly.io:11112. From that point every instance is authenticated,
translated to a DICOMweb STOW-RS POST, and delivered to your webhook in real time.
Dicomly is intentionally payload-agnostic. We don’t care what SOP class the bytes are — CT, MR, mammography, ultrasound, structured reports, RT plans, encapsulated PDFs, presentation states, waveforms. If it’s a valid DICOM instance, we route it.
Who we serve
AI & analytics startups
Stop building DICOM plumbing. Accept live data from day one without hiring a DICOM engineer or running a PACS. Add 100 sources with 100 API calls.
EHR / EMR vendors
Embed DICOM ingest into your platform without a dedicated DICOM team. Certificates map cleanly to your existing tenant model.
Teleradiology & telemedicine
Scale from dozens to hundreds of clinician-facing sites. Per-endpoint pricing maps directly to your own per-site billing model.
Research labs & academia
Ingest de-identified studies, structured reports, or RT plans from collaborating institutions. One cert per partner, revoke anytime.
OEMs & device makers
Provision connectivity at manufacturing time. Each device gets its own certificate, scoped to exactly one destination.
Imaging centers & clinics
Forward outputs from your modalities or local archive to a cloud destination of your choice — without procuring a VPN or running a DICOM router.
What we are not
Dicomly is deliberately narrow. We’re not a DICOM archive, viewer, study manager, or tag-normalization tool. We don’t inspect or transform the data — we just move it. That’s what makes us cheap to run, quick to integrate, and easy to clear with security.
And we’re not a data custodian. Dicomly never stores patient data — no disk, no queue, no cache. Bytes flow straight from the sender to your webhook and are gone. Nothing is kept on our side.
For compliance teams: that makes us a HIPAA conduit and a GDPR processor, not a custodian. Your backend is where the data lives — we’re just the pipe.
How data flows
When a sender opens a DICOM C-STORE association, Dicomly authenticates the client certificate, resolves it to your endpoint, and streams each DICOM instance directly to your webhook as a STOW-RS POST. The bytes travel socket-to-socket: in from the sender, out to your HTTPS endpoint. They never touch disk, a queue, or any durable storage on our side.
If your webhook is temporarily unavailable, Dicomly returns a DIMSE error to the sender, which retries on its own schedule — exactly as the DICOM standard requires. No data is buffered or held on our infrastructure, and no manual intervention is needed.
The only state Dicomly persists is routing metadata and usage counters (byte counts, instance counts, timestamps). No DICOM tags, no patient identifiers, no SOP UIDs are ever written anywhere.
Start receiving DICOM today.
Early access. No credit card. First endpoint free.