Quantum arrives on two fronts at once: a platform deal and a security deadline

Two announcements, one week

Quantum computing stopped being a single story this week. Intel announced a definitive agreement to acquire Classiq, a provider of quantum computing software, to create a full-stack quantum computing platform. The transaction is expected to close in the first half of 2027, subject to regulatory approvals and other customary closing conditions. The same week, Oracle announced that Database 19c Release Update 19.32 introduces a new cryptographic provider framework supporting TLS 1.3, post-quantum cryptography, and FIPS 140-3 mode. One announcement is about building quantum machines. The other is about defending today's data against a future quantum machine. An executive now has to hold both ideas at once. m:…2925 m:…5639

What Intel is buying

Intel says the acquisition combines Classiq's synthesis platform with Intel's silicon spin-qubit technology, with the aim of becoming a full-stack quantum solutions provider. Classiq's platform uses AI agents and a high-level quantum modeling language, according to Intel, and it enables developers to create scalable quantum applications without requiring deep expertise in quantum circuit design. That last detail is the commercial point. Quantum software that only a small group of specialists can use stays a research project. Software that lets ordinary developers model a problem at a higher level can reach product teams. m:…6456

On hardware, Intel says it is currently the only company capable of producing qubit chips and complex cryogenic control electronics at scale using conventional semiconductor manufacturing processes, and that it has been investing in quantum computing development since 2015. Intel plans to add Quantum Processing Units to its compute portfolio alongside CPUs, GPUs, and ASICs, and says it uses processes common to conventional silicon-based semiconductor manufacturing for quantum chips. This suggests Intel is betting that its existing factory advantage, not just a lab breakthrough, is what makes a quantum platform scalable. That claim comes from Intel itself, so it should be read as the company's argument for the deal, not as independent market analysis. m:…6456 m:…2925

Intel also says it intends to maintain Classiq's modality- and hardware-agnostic software solution after the acquisition closes, and to support Classiq's existing multi-platform integrations. Until the transaction closes, Intel and Classiq will continue to operate as separate, independent companies. For a customer or partner, that commitment matters more than the deal headline. A platform that only works on one vendor's hardware is a narrower bet than a platform that keeps working across hardware types, and Intel is explicitly promising the broader version, at least in its announcement. m:…6456 m:…2925

What Oracle is shipping

Oracle's update is less dramatic and more immediately actionable. Database 19c Release Update 19.32 introduces a new cryptographic provider framework that supports TLS 1.3, post-quantum cryptography, and FIPS 140-3 mode, and allows switching between Legacy and Next Generation providers. The new provider supports hybrid post-quantum key establishment using ML-KEM. In plain terms, a database can start using cryptography designed to resist quantum decryption, while still talking to older clients, rather than waiting for a single cutover day. m:…5639

The compatibility details in Oracle's announcement are what make the update usable. Existing TLS 1.2 clients do not require immediate updates after patching to 19.32, according to Oracle, while the Next Generation provider removes support for TLS 1.0 and TLS 1.1. TLS 1.3 reduces connection-establishment overhead by reducing handshake round trips, according to Oracle. FIPS 140-3 disallows SHA-1, MD5, 3DES, DES, and RC4. A team can therefore move the database forward without breaking every old client at once, but it cannot keep the oldest and weakest protocols in the new mode. m:…5639

The timing pressure comes from standards, not from a single vendor. NIST recommends that all new projects use FIPS 140-3 starting September 21, 2026, according to Oracle's announcement. Oracle also says Oracle Database 26ai clients support TLS 1.3, JDBC 19c supports TLS 1.3 through JDK 11 and later, and ODP.NET 19c version 19.16 and later supports TLS 1.3. The practical reading is that new database work has a clear default now, even if older systems migrate more slowly. The cited material does not give a deadline for existing systems, so it would be wrong to present September 21, 2026 as a cutoff for everything already running. m:…5639

Opportunity and deadline, together

Put together, the two announcements reframe quantum for a tech executive. It is no longer only a question of when a useful quantum computer arrives, or which vendor wins. It is also a question of how long today's encrypted data stays safe, and whether the systems that hold it can move to post-quantum cryptography without a rebuild. Intel's deal is about capability in the future. Oracle's update is about protection in the present. A company that only watches the first story will miss the second, and the second is the one with a patch available now. m:…2925 m:…5639

This suggests a sensible split for planning. On the opportunity side, watch whether Intel's full-stack platform actually stays hardware-agnostic after the deal closes in the first half of 2027, and whether developers without deep quantum circuit expertise can build useful applications on it. On the security side, inventory which database clients and protocols are still in use, test the Next Generation provider where old protocols can be dropped, and apply the new-project standard to new work first. Neither step requires believing a specific forecast about quantum hardware. Both follow from announcements that are already public, and both can be started before the acquisition closes. m:…2925 m:…5639