Product family

Thirteen products, two platform tools.

The Synthology portfolio covers the imaging-stack lifecycle end-to-end: DICOM routing, vendor-neutral archiving, structured reporting, migration, whole-slide pathology, encounter workflows, the SynthIQ DICOM load balancer, the SynthCloudConnect result relay, and SynthInSight fleet analytics — thirteen products spanning the §520(o)(1)(D) non-device line. Plus SynthQMS and SynthVault, the platform tooling that runs underneath.

Router-pattern hosts · Specialized engines · Platform tooling

DICOM routing + archive

Router-pattern hosts

The Router and the five VNA sibling hosts — one binary per regulatory classification. They share architecture, share underlying libraries, and ship as separate executables on different ports so a regulatory class boundary is also a code boundary.

XyDromatics Router

Non-Device · §520(o)(1)(D)

DICOM routing platform.

Ingest from any modality, route by rules, transform tags, anonymize, prefetch, hold-and-release. The flagship workflow orchestrator — both the operating-control plane for an imaging department and the integration hub between modality, EMR, PACS, VNA, and reporting.

Learn more about Router →

Capabilities

  • C-STORE SCP + STOW-RS endpoints
  • Rule-driven routing with per-rule destinations
  • Tag transformation, anonymization, pixel redaction
  • Hold queue + manual release for sensitive studies
  • Q/R prefetch + scheduled forwarding
  • HL7 ingestion + worklist generation

XyDromatics VNA Repository

Non-Device · §520(o)(1)(D)

Long-term DICOM archive.

The DICOM archive host. C-STORE SCP, archive catalog, and DICOMweb endpoints. Pluggable archive store backends: local filesystem, S3-compatible object stores, on-prem NAS. PostgreSQL, SQL Server, or Oracle for the catalog.

Learn more about VNA Repository →

Capabilities

  • Pluggable archive store (local / S3 / NAS)
  • Pluggable catalog DB (PostgreSQL / SQL Server / Oracle)
  • DICOMweb (QIDO-RS, WADO-RS) for browser access
  • Lifecycle policies + tiering
  • Per-AE-Title access control
  • Hash-chain-verified write log for regulated retention

XyDromatics VNA Migration

Non-Device · §520(o)(1)(D)

Archive-to-archive migration.

Migrate studies from a legacy PACS/VNA into a target archive — any source, any destination, any DICOM-conformant target. Includes per-study verification, retry on transient failures, scheduling, and progress reporting.

Learn more about VNA Migration →

Capabilities

  • Multi-source ingestion (C-STORE SCU/SCP, STOW-RS, file watchers)
  • Per-study verification + checksum
  • Pause/resume + scheduled migration windows
  • Migration progress reporting
  • Tag transformation during migration

XyDromatics VNA Research

RUO · §520(o)(1)(D)

RUO research-only archive.

A Research-Use-Only sibling of the VNA archive line. PHI-anonymized by design, decoupled from clinical workflows, suited for de-identified study sets and longitudinal research projects.

Learn more about VNA Research →

Capabilities

  • PHI anonymization at ingest
  • Cohort-level access control
  • Project-scoped data partitioning
  • Export to research-friendly formats (NIfTI, CSV manifests)
  • NOT for clinical decision-making

XyDromatics VNA Clinical

Non-Device · §520(o)(1)(D)

Clinical archive.

Non-device software under §520(o)(1)(D). The clinical-grade DICOM archive of the family: license-gated clinical-tag-edit (DICOM metadata correction) behind a two-person approval workflow, hospital-grade availability, and a tamper-evident audit trail. Clinical-interpretation features (diagnostic viewer + report authoring) ship locked and are enabled for Synthology development partners only — never licensable to customers — which is what keeps the shipped product non-device.

Learn more about VNA Clinical →

Capabilities

  • Clinical-tag-edit (DICOM metadata correction, license-gated, two-person approval)
  • Hospital-grade availability (HA pair, automatic failover)
  • Full, tamper-evident (Merkle-chained) audit trail of every clinical-tag change
  • Report-object transport to your existing reporting platform
  • Clinical-interpretation features locked at GA — development-partner-only

XyDromatics VNA Clinical Research

Non-Device · §520(o)(1)(D)

Dual-posture clinical + research.

A combined Clinical + Research host for institutions that operate both production clinical archives and de-identified research workflows. Non-device software under §520(o)(1)(D) — the full VNA Clinical feature set plus PHI-anonymized research-mode lanes with per-lane access control. As with VNA Clinical, clinical-interpretation features ship locked and are development-partner-only, never licensable to customers.

Learn more about VNA Clinical+Research →

Capabilities

  • Full clinical-archive feature set
  • PHI-anonymized research lanes
  • Per-lane access control + audit trail
  • RUO research lanes alongside the clinical archive

Focused subsets

Specialized engines

Smaller-footprint products extracted from the Router for specific use cases — structured reporting, migration, whole-slide pathology, encounter workflows. Each is a standalone licensed SKU.

XyDromatics SR Engine

Non-Device · §520(o)(1)(D)

Structured-report ingest + forwarding.

A standalone licensed subset of the Router focused on SR (Structured Report) DICOM objects. Ingests SR from modalities, applies tag transformations, forwards to PACS/VNA + reporting platforms.

Learn more about SR Engine →

Capabilities

  • SR DICOM SOP class support
  • SR-specific tag transformations
  • Forward to PACS/VNA + report distribution
  • Standalone licensable SKU

XyDromatics Migration Engine

Non-Device · §520(o)(1)(D)

Standalone migration appliance.

A standalone migration appliance distinct from VNA Migration. HL7/MWL-driven archive ingest and scheduled sends. Suited for short-lived migration projects where deploying the full VNA Migration product is overkill.

Learn more about Migration Engine →

Capabilities

  • HL7/MWL-driven ingest
  • Scheduled sends with retry
  • No persistent archive (transient routing)
  • Standalone licensable SKU

XyDromatics Pathology Engine

Non-Device · §520(o)(1)(D)

Whole-slide imaging ingest sidecar.

WSI conversion sidecar for the VNA family. Watches an intake folder, converts native pathology formats (SVS, NDPI, MRXS) to DICOM Supplement 145 WSI, and forwards via STOW-RS to your VNA. The only Windows-only product in the family (OpenSlideNET dependency).

Learn more about Pathology Engine (IPE) →

Capabilities

  • Native pathology format conversion (SVS, NDPI, MRXS)
  • DICOM Supplement 145 WSI output
  • STOW-RS forwarding to VNA
  • Watch-folder ingest pattern
  • HIPAA mode (license feature)

XyDromatics Encounter Engine

Non-Device · §520(o)(1)(D)

POCUS-style encounter workflow.

Encounter-driven imaging workflow with mandatory human verification gate. Receives DICOM, matches against an HL7 ADT feed, blocks on human verification, then forwards enriched studies to PACS/VNA. Closes the encounter loop with HL7 ORM^O01 / FHIR ServiceRequest back to the EMR.

Learn more about Encounter Engine →

Capabilities

  • DICOM ingest + HL7 ADT matching
  • Mandatory human-verification gate
  • Forward to PACS/VNA after verification
  • HL7 ORM^O01 / FHIR ServiceRequest emission
  • POCUS-style encounter UX

SynthIQ

Non-Device · §520(o)(1)(D) Patent Pending

Vendor-neutral DICOM load balancer.

Drop-in replacement for F5, NetScaler, or HAProxy in front of any PACS or DICOM Router pool. Routes by Study Instance UID, not TCP 5-tuple — keeps every clinical study together on one backend across associations, follow-up imaging days later, and SynthIQ restarts. Works with any DICOM-conformant backend (Synthology fleet, vendor PACS, research VNAs, cloud-native endpoints).

Learn more about SynthIQ →

Capabilities

  • Persistent SUID-keyed study affinity routing
  • Three-tier waterfall: persistent affinity → least-busy → fallback
  • Health-aware backend selection (5s heartbeat polling)
  • Persistent affinity cache (SQLite, PostgreSQL, or SQL Server)
  • Read-only admin SPA + JSON APIs for operators
  • Vendor-neutral by design (heterogeneous pools supported)
US Patent Applications
64/074,191 — Patent Pending
64/081,343 — Patent Pending

SynthCloudConnect

Non-Device · §520(o)(1)(D)

Cross-site DICOM result relay.

Bridges AI-vendor result delivery into firewall-isolated on-prem Router fleets. The AI vendor C-STOREs results to a SynthCloudConnect endpoint; the on-prem Router pulls them down over an existing outbound-initiated mTLS WebSocket. No inbound firewall holes; no Synthology-to-customer initiated traffic. Generally available — self-hosted or hosted multi-tenant.

Learn more about SynthCloudConnect →

Capabilities

  • Cross-site DICOM C-STORE bridging (cloud sender → firewall-isolated receiver)
  • Per-tenant result queue with TTL retention + audit
  • Outbound-initiated mTLS WebSocket from on-prem (no inbound firewall changes)
  • Pseudonymization-preserving — round-trips through customer keypair tree
  • Compatible with existing Router AI-vendor routing rules
  • Self-hosted single-tenant deployment (Terraform / MSI / Helm) plus a Synthology-hosted multi-tenant variant

SynthInSight

Non-Device · §520(o)(1)(D)

Historical + cross-router fleet analytics.

A standalone analytics surface over the operational history your Synthology products archive. Each product writes a compact, gzipped-NDJSON event archive off its hot database; SynthInSight reads that archive with an embedded columnar (DuckDB) query engine and answers all-time and cross-router questions the live operational dashboards can't — without ever touching the ingest path. Aggregate-only by design: counts, distinct-counts, and daily series — never row-level PHI. Deploys independently of every other product.

Learn more about SynthInSight →

Capabilities

  • All-time + cross-router aggregate analytics (count, distinct-count, daily series)
  • Reads the gzipped-NDJSON archive each product's EventArchiver writes — off the hot operational DB
  • Embedded DuckDB columnar query engine (managed-writer / native-reader split)
  • Aggregate-only by design — never returns row-level PHI
  • Bearer-token-gated HTTP API; deploys independently of any other product
  • Windows MSI or Linux tarball

Underneath everything

Platform tooling

The internal control plane (SynthQMS) and the regulated-document vault (SynthVault) that the regulated products run on. Available to customers as standalone products as well.

SynthQMS

Internal control plane (non-medical-device)

Quality management + CRM control plane.

The internal control plane for the Synthology product family. Document control, training, audits, CAPAs, complaints, MDR, change control. Plus customer / contact / pipeline / estimate / invoice tracking. 21 CFR Part 11-aligned audit trail. ISO 13485 + SOC 2 structured.

Learn more about SynthQMS →

Capabilities

  • Controlled-document workflow (draft → review → approve → archive)
  • 21 CFR Part 11 audit trail
  • Training, audits, CAPAs, complaints, MDR
  • CRM (accounts, contacts, leads, pipeline)
  • Estimates, invoices, billing, accounting integration
  • Booth PWA for trade-show lead capture

SynthVault

RUO + optional Part 11 mode

Versioned document vault.

Generic file versioning with checkout/checkin, hash-chain audit, integrity sweeps, webhooks, backup/restore. The regulated-document storage backbone of the Synthology product family. Customers can opt into Part-11-friendly retention via a license feature.

Learn more about SynthVault →

Capabilities

  • Checkout / checkin / version history
  • Hash-chain-verified audit log
  • Integrity sweep (re-verify all blobs)
  • Webhooks on every checkin
  • Project + folder organization
  • Optional Part-11 retention mode (license feature)

Want a deeper look at any product?

Tell us which products are interesting and we’ll walk through them in detail with the right engineer on our side. 30 minutes, your imaging stack, our products.

Request a Demo Regulatory Posture