Fifteen years of DICOM infrastructure,
distilled into one API call.

Dicomly isn't a slick tool wired together overnight with AI to ride the trend — it has a story. It comes from a tech team building secure DICOM systems in production since 2010, including a platform acquired by Philips.

  1. 2010

    FetView goes live: a cloud DICOM SaaS

    First production deployment of FetView, an OBS/GYN reporting platform built on DICOM 3.0. Studies were received over the public Internet, routed to the cloud receiver via server firewall and IP rules.

  2. 2011

    FetView DICOM Gateway

    Shipped the FetView DICOM Gateway, an on-premise device deployed at the imaging site. It wrapped the DICOM stream in a VPN tunnel and forwarded it to the cloud receiver.

  3. 2013

    Cloud storage

    Built a sharded storage layer on CIFS/SMB (Samba), accessed by the imaging devices. TLS in transit, encryption at rest.

  4. 2014

    Cloud storage decommissioned

    Retired the CIFS/SMB (Samba) storage system. Samba over WAN was unreliable in production: connection timeouts, session loss, and high latency variability.

  5. 2015

    A service fleet, TLS-secured throughout

    FetView, now operated by Zeitgeist Health SE, ran as a fleet of independent services with DICOM connectivity TLS-secured end to end. The platform earned ISO 9001:2008 and ISO/IEC 27001:2013 certification.

  6. 2015

    Fully containerized

    Moved the entire service fleet to Docker, about a year after the Docker 1.0 release — an early production Docker adopter in healthcare, running stateful DICOM services in containers.

  7. 2016

    Self-hosted AI: DICOM image categorisation

    Built a TensorFlow Serving prototype to categorise OBS/GYN DICOM studies in FetView, running inference on in-house servers with no images sent to external services. Shelved after validation.

  8. 2017

    First Kubernetes prototype

    Migrated the FetView microservice fleet to Kubernetes. The service setup became declarative and repeatable, and recovery under load was predictable.

  9. 2018

    No more hardware: pure TLS connectivity

    Retired the on-premise FetView DICOM Gateway. The device was the largest source of operational burden and onboarding friction. Moved to pure TLS connectivity, no hardware at the imaging site.

  10. 2020

    Going all-in on AWS

    Migrated production infrastructure entirely to AWS: managed services, global regions, and auditable compliance. Removed the last self-managed server overhead.

  11. 2021

    Acquired by Philips

    Philips acquired Zeitgeist Health SE, the company behind FetView. Independent validation that the team understood medical imaging, security, and production healthcare software.

  12. Today

    Dicomly — the connectivity API

    Dicomly packages more than a decade of running DICOM over the Internet into a connectivity API. Receiving DICOM from a hospital is one API call.

The hard parts are done. What's left for you is a single API call.

Start receiving DICOM today.

Early access. No credit card. First endpoint free.