Login
Quantum-safe · QKD monitoring

Your QKD network, in one pane of glass.

QBER, photon rates, key pools. Watched like any other signal.

ProDCIM monitors your QKD links, photon detectors and key-management servers alongside the rest of your critical infrastructure, in the NOC you already run.

  • QBER
  • Key rate
  • Detector health
  • Eavesdropping alarms
  • ETSI QKD-API

The problem

The quantum layer is a blind spot.

QKD hardware ships with its own vendor tools that never reach the NOC. Photon rates, error rates and key pools live in a separate world, so the on-call engineer can't see them next to power, cooling and the network.

  • Vendor consoles that don't talk to your operations tooling
  • No view of QBER or key rate beside the rest of the estate
  • Reading quantum telemetry shouldn't need a physics degree

QKD vendor console

QBER

0.42%

Key rate

9.8 kb/s

SPAD dark counts

312 Hz

Key pool

87%

not in the NOC

Locked in the vendor tool · sample values

What we watch

Catch eavesdropping in the QBER.

A sustained jump in quantum bit error rate is the classic signature of an intercept. ProDCIM trends QBER per link and raises one alarm the moment it breaches threshold.

QBER · link DC1 to DC2Eavesdropping alarm
threshold 6%9.4%

QBER

2.1 to 9.4%

Key rate

48 to 6 kb/s

Action

Investigate

Illustrative QKD telemetry · sample data

prodcim.local · Monitoring
ProDCIM monitoring, quantum and classical signals in one NOC

What this helps you do: work a QBER excursion the same way you work a thermal or power alarm, in the same console, with the same runbook. Sample data shown.

Quantum layer, familiar dashboards

Three slices of a QKD network, one pane.

Dark-fibre & free-space links

Quantum bit error rate, photon arrival rate, attenuation and synchronisation drift, per link.

  • QBER
  • Key rate
  • Drift

QKM servers & APIs

Key generation rate, key-pool depth and ETSI QKD-API consumer counts and freshness.

  • Key pool
  • Freshness
  • ETSI QKD-API

Hybrid PQC + QKD

Visibility into the seam between QKD-derived keys and post-quantum classical envelopes.

  • Hybrid mode
  • Failover
  • PQC

What we watch

Six signals every QKD operator needs.

Most NOC tools were not designed for the quantum layer. These are the metrics and events that matter, exposed the same way as power and cooling.

QBER trend

Real-time quantum bit error rate per link, with thresholds tuned to your hardware vendor.

Key generation rate

Usable key per second as it varies with link conditions, temperature and load, see brownouts early.

Detector health

SPAD dark counts, after-pulse rate and temperature, flag a failing detector before keys stop.

Fibre link integrity

Optical loss, polarisation drift and OTDR-style step changes that can hint at tampering.

Eavesdropping alarms

Sudden QBER excursions, decoy-state anomalies and Bell-test deviations, rolled up as one alert.

Classical correlation

Quantum events line up with network, power and environmental events, on one timeline.

Detect, correlate, alert, verify

From a photon-rate dip to an actioned response.

The same workflow ProDCIM runs on classical infrastructure, extended to quantum signals.

1. Detect

Continuously poll QKD links and KMS endpoints into the same time-series store.

2. Correlate

Cross-reference photon-rate dips with fibre alarms, temperature drift and load.

3. Alert

Route incidents through the same NOC runbook as IT and network events.

4. Verify

Confirm recovery: QBER below threshold, key rate restored, consumers reconnected.

ProDCIM monitors your QKD network. It does not replace your QKD hardware.

Vendor-agnostic·ETSI QKD-API·one NOC for classical and quantum·SOC 2 Type II Certified

Part of the platform

Quantum signals, in the same model.

QKD telemetry joins the assets, sites and metrics that power the rest of ProDCIM.

FAQ

Frequently asked questions

Can ProDCIM monitor a Quantum Key Distribution (QKD) network?
Yes. ProDCIM monitors QKD links, photon detectors and key-management servers alongside the rest of your critical infrastructure, so QBER, key rates and key-pool depth appear in the NOC you already run instead of staying locked in a separate vendor console.
How does ProDCIM detect eavesdropping on a QKD link?
A sustained jump in quantum bit error rate (QBER) is the classic signature of an intercept, so ProDCIM trends QBER per link and raises an alarm the moment it breaches threshold. Sudden QBER excursions, decoy-state anomalies and Bell-test deviations are rolled up into one alert your NOC can work like any other incident.
Which QKD metrics does ProDCIM track?
Six core signals: QBER trend per link, key generation rate, detector health (SPAD dark counts, after-pulse rate and temperature), fibre link integrity (optical loss, polarisation drift and OTDR-style step changes), eavesdropping alarms, and correlation of quantum events with network, power and environmental events.
Does ProDCIM replace my QKD hardware or key management system?
No. ProDCIM monitors your QKD network, it does not replace your QKD hardware. It is vendor-agnostic and watches your key-management servers too, tracking key generation rate, key-pool depth, freshness and ETSI QKD-API consumer counts.
Can ProDCIM correlate QKD alarms with power, cooling and network events?
Yes, that is the point of putting quantum telemetry in the same platform. QKD links and KMS endpoints are polled into the same time-series store as the rest of the estate, so a photon-rate dip can be cross-referenced with fibre alarms, temperature drift and load on one timeline.
Does ProDCIM support hybrid PQC and QKD deployments?
Yes. ProDCIM gives you visibility into the seam between QKD-derived keys and post-quantum classical envelopes, including hybrid mode and failover, so both halves of a hybrid key setup are watched in one place.

Bring the quantum layer into view

Book a walkthrough and we'll show QBER trends, eavesdropping alarms and classical correlation on a live NOC.