The QCIM Engine is synthesizable cryptographic IP for ASICs and FPGAs built on our compute-in-memory architecture. Its reprogrammable design allows multiple classical and post-quantum algorithms to share a compact hardware foundation with integrated side-channel protections.
QCIM replaces the one-core-per-algorithm model with a single compute-in-memory architecture that executes versioned cryptographic kernels. Device makers now have a practical way to adapt cryptography throughout the life of their product.
QCIM keeps sensitive operations within a controlled compute-in-memory structure designed to reduce leakage through timing, power, and electromagnetic emissions.
Optimized for low power and small die area. QCIM bundles all deployed algorithms in the same IP block, holding PPA down to a single crypto-engine footprint and shifting cryptographic work off general-purpose CPUs.
A highly parallel datapath keeps QCIM competitive with fixed-function accelerators across ML-KEM, ML-DSA, AES, and SHA-3.
Measured benchmarks available on request, supplied with test configuration, baseline, clock assumptions, and FPGA or simulation status.
Our new architecture makes all four possible. ↓
Traditional computer cores move data between memory and separate, fixed-function processing blocks. QCIM instead performs cryptographic operations where intermediate data is stored, allowing multiple algorithms to share the same logic.
New and updated algorithms can use the same protected hardware foundation rather than requiring a separate accelerator and security implementation for each one.
Sensitive intermediate values remain within QCIM's controlled compute-and-memory structure, reducing observable data movement and allowing protections to be applied consistently across algorithms.
Less data movement and duplicated circuitry reduce area and power requirements.
Compute-in-memory has been a long-standing idea in the cryptographic research community. The QCIM Engine is the first time it's available in deployable commercial hardware.
The Engine executes the cryptography, the Root of Trust establishes device trust, and the Platform maintains that trust after deployment.
Request evaluation RTL, benchmark documentation, integration specifications, or a technical session with our hardware team.
