Qedma, an Israeli startup specializing in quantum noise resilience solutions, has raised US$26 million in a series A funding round.

The round was led by Glilot Capital Partners’ early growth fund, Glilot+, with contributions from IBM, Korean Investment Partners, and existing investor TPY Capital.

The company focuses on software designed to reduce errors in quantum computing.

These errors are often caused by environmental noise affecting quantum bits, or qubits.

Founded in 2020 by Prof. Netanel Lindner, Dr. Asif Sinay, and Prof. Dorit Aharonov, Qedma describes its software as a critical “operating layer” for quantum hardware.

This layer addresses the industry’s need for effective error correction to scale quantum computing.

Qedma’s technology is integrated with IBM’s quantum computers.

🔗 Source: Calcalist

🧠 Food for thought

1️⃣ Error correction remains the quantum computing industry’s biggest technical hurdle

The $26 million investment in Qedma highlights how critical error correction has become to advancing practical quantum computing applications.

Error correction has been a fundamental challenge since the field’s earliest days in 1995 when Peter Shor developed the first quantum error correction code to protect fragile qubits from noise and decoherence 1.

For nearly three decades, the overhead required for traditional quantum error correction has been prohibitive, requiring up to 1,000 physical qubits to maintain just one logical (error-corrected) qubit, as mentioned in Qedma’s announcement.

This correction challenge explains why, despite billions in investment and significant hardware advances, we have yet to see quantum computers solving practical real-world problems at scale.

IBM’s recent paper in Nature demonstrated their own breakthrough with a new quantum error-correcting code that is reportedly ten times more efficient than previous methods 2, showing how the entire industry is prioritizing this critical bottleneck.

Qedma’s approach of analyzing device-specific noise profiles represents one of several competing strategies emerging to address this limitation, alongside IBM’s QLDPC codes and Google’s surface code implementations 3.