
Intel has agreed to acquire Classiq, an Israeli quantum computing software company, for $2.2 billion — the largest acquisition in quantum computing history, and Intel’s biggest deal since Mobileye in 2017. The deal closes in H1 2027. For developers, the financial details are the least interesting part. What matters is what Classiq actually does and whether you should start using it now.
What Classiq Does (and Why It’s Different)
Most quantum SDKs — Qiskit, Cirq, Q# — require you to program at the gate level. You specify individual qubit operations, manage circuit depth, handle transpilation manually. It works, but it assumes you know quantum physics well enough to think in gates.
Classiq takes a different approach. You write quantum programs using Qmod, a modeling language embedded in Python. You describe what your algorithm should do, and Classiq’s synthesis engine handles the rest — generating an optimized, hardware-aware gate-level circuit for whatever backend you’re targeting. Current backends include IBM, IonQ, AWS Braket, Azure Quantum, and NVIDIA.
pip install classiq
from classiq import *
@qfunc
def main(x: Output[QNum], y: Output[QNum], z: Output[QNum]):
allocate(1, x)
H(x)
y |= 2
z |= x + y
qprog = synthesize(main)
show(qprog)
You never write a gate. The synthesis engine converts your functional intent into an optimized circuit. The Classiq getting-started docs walk through installation and authentication in minutes. The 2026 SDK adds runtime conditionals, mid-circuit measurements, and a Fault Tolerance Engine for translating circuits to fault-tolerant hardware execution plans.
Qiskit has won the community battle — more tutorials, more Stack Overflow answers, more direct IBM hardware access than anything else. But Classiq’s synthesis approach is the right direction for the field. Writing quantum programs at the gate level is the equivalent of writing modern web apps in assembly: technically correct, practically unsustainable as algorithms grow.
The Multi-Platform Question
The acquisition raises an obvious concern: Intel now owns the software layer that runs on IBM and Google hardware. That’s an uncomfortable position for everyone involved.
Intel’s official announcement commits to maintaining multi-platform support after close. The company says Classiq will continue supporting IBM, IonQ, AWS Braket, Azure Quantum, and NVIDIA backends. That’s the right thing to say. Whether it stays true twelve months after the deal closes is worth watching.
The honest risk: Intel has strong incentive to deepen Classiq’s integration with its own Tunnel Falls hardware. The multi-platform commitment should be treated as a current intention, not a permanent guarantee. Watch the post-acquisition roadmap closely — especially any changes to pricing or hardware preferences in the six months after H1 2027.
Intel’s Quantum Bet
Intel’s approach is contrarian. IBM and Google both use superconducting qubits, which require cooling to near absolute zero and purpose-built facilities. Intel uses silicon spin qubits — encoding quantum information in electron spin states inside standard silicon structures, manufactured in the same wafer fabs Intel uses for classical chips.
The current chip, Tunnel Falls, has 12 qubits and is available to researchers. The roadmap calls for 100 qubits by 2028. That’s not competitive with IBM or Google on qubit count today, but Intel’s argument is that classical semiconductor manufacturing is the eventual scaling path for quantum. Intel CEO Lip-Bu Tan frames it as quantum computing working “alongside CPUs and GPUs” — the only realistic near-term picture anyway.
Adding Classiq gives Intel the software stack it needs before that hardware matures. A synthesis-based SDK works whether you have 12 qubits or 10,000. The SiliconANGLE analysis notes this deal is specifically designed to address quantum routing overhead — a real performance bottleneck that Classiq’s compiler is built to minimize.
Should You Adopt Classiq Now?
If your team wants to start working with quantum computing without hiring quantum physicists, Classiq is the most practical entry point available. The Classiq library on GitHub is the largest collection of quantum algorithms in any single repository. The Python SDK installs in one command. Classiq Studio gives you a browser-based IDE if you’d rather skip local setup.
If you’re already running workloads on IBM or IonQ, the multi-platform support means switching your synthesis layer to Classiq doesn’t require changing your hardware backend.
The caution: Intel’s acquisition closes in H1 2027, and the post-acquisition roadmap isn’t public. Watch what happens to pricing, platform support, and open-source commitments after close. For now, the SDK is free-tier available and the synthesis model is where quantum programming is heading regardless of who owns the company.

