The open source Backline extension of Xanadu's PennyLane quantum software framework lets a quantum processor and standard AMD chips exchange data in a few microseconds, fast enough for real time error correction.
Xanadu and AMD released Backline on Thursday, an open-source wiring layer that lets a quantum processor hand measurements to off-the-shelf AMD server silicon and get correction decisions back in a few microseconds. That round-trip is the latency budget real-time quantum error correction (QEC) actually needs, and the bet behind the release is that standard enterprise chips can hit it without the custom control hardware the field has depended on.
Backline plugs into Xanadu's PennyLane quantum software platform, the same one many academic and industry labs already use to design quantum circuits. It extends PennyLane's existing MLIR-based Catalyst compiler so a developer can write, in Python, the kind of feedback loop that used to require hand-rolled hardware description languages running on custom control chips. Xanadu and AMD announced the release on Thursday, and the code is now public on GitHub under an open-source license. A companion technical paper titled "Python in the front, party in the Backline" went up on arXiv the same day.
According to the joint release, the end-to-end loop from a quantum measurement to a correction decision runs at a mean of 2.3 microseconds when an AMD EPYC or Threadripper CPU does the work, and 4.4 microseconds when an AMD Instinct MI200 or MI300 GPU runs the syndrome decoder. The syndrome decoder is the routine that reads error signatures from the quantum chip and decides what gate to apply next. Those figures are vendor-reported. No independent benchmark has been published yet, and Backline is one wiring layer in a system whose scale-up problem is unsolved above it.
QEC is the real-time feedback loop a quantum computer needs to stay accurate: read the qubits, infer which errors just happened, push the corrective gate. Most published QEC work assumes custom ASIC controllers to keep that loop tight. Backline's design uses Remote Direct Memory Access (RDMA) over RoCE v2, a low-latency network protocol that lets servers share memory directly, plus zero-copy user-space transfers through libibverbs, the Linux library that lets a program place data into a network adapter's memory without copying through the kernel.
That pipeline lets a Python-based syndrome decoder on an AMD EPYC CPU pull measurements from an AMD Versal VPK120 FPGA, the programmable chip that sits next to the quantum processor and acts as its real-time controller, and return a correction in single-digit microseconds. For heavier decoders, the same loop can offload to an AMD Instinct GPU, which is where the 4.4 microsecond figure comes from. Transport runs over an AMD Pensando SmartNIC, a network card with its own programmable processor, so the host CPU does not become the bottleneck.
The deeper effect is on who can build this. Writing a QEC feedback loop used to mean hiring a hardware engineer to write Verilog or VHDL against a vendor-locked control box. Backline replaces that with a unified Python workflow that calls Triton, the open-source GPU kernel compiler, to generate the custom decoders. A lab that owns an AMD-equipped workstation and a quantum processor can now prototype the wiring that used to require a partnership with a control-electronics vendor. AMD's developer article lays out the same silicon taxonomy, EPYC and Threadripper for the CPU slice, Instinct for GPU acceleration, Versal for the FPGA controller, Pensando for the network, as a single AMD stack covering the whole loop. That is the displacement the release is making: the bespoke-ASIC narrative that has dominated QEC control hardware to date, and the vendor lock-in it carried.
The 2.3 and 4.4 microsecond figures are Xanadu and AMD's own measurements. The arXiv preprint has not been peer-reviewed. Quantum error correction at the scale needed to run useful algorithms remains an open problem above this wiring layer. Backline solves the integration step, not the qubit-count problem.
What changes today is the build surface. The public repository is open, the arXiv paper lays out the design, and any team with an AMD-equipped workstation and a quantum backend can now wire up the same kind of feedback loop that, until this release, was a vendor-locked project.