Corintis as Thermal Packaging IP
Corintis
The real prize is not selling more cold plates, it is becoming part of the chip design kit that engineers use before a package ever gets built. Once Corintis moves from a bolt on cooling part to a foundry validated channel library and process recipe, a GPU or ASIC team can plan cooling at the same time it plans floorplans, power delivery, and 3D packaging, which makes the technology harder to replace and easier to carry across future nodes and stacked dies.
-
Corintis already has the upstream workflow needed for an IP model. Customers upload chip heat maps into Glacierware, generate channel layouts, then test them in silicon or copper inserts before production. That is the same design flow a foundry or chip vendor would want to turn into repeatable reference blocks instead of one off hardware projects.
-
There is a clear precedent for this business model in adjacent chip markets. OpenLight sells a process design kit, charges design and production licenses, and lets customers manufacture at licensed foundries. That shows how a specialist can turn deep process know how into a standard library that many chip teams reuse, rather than a component sold one module at a time.
-
The reason this matters more in 2.5D and 3D is that cooling stops being a server level problem and becomes a package reliability problem. Industry roadmaps have long pointed to within tier microfluidic cooling for silicon interposers and stacked systems, and Microsoft now publicly shows coolant flowing inside silicon chips for data center use.
If foundries and accelerator vendors adopt microfluidic channels as a standard design element, Corintis can evolve into the thermal equivalent of a packaging IP layer. That would shift the company toward recurring license and software revenue, while pulling its hardware into validation, prototyping, and high performance deployments where standard recipes still need custom execution.