Why we built this

The nuclear industry is scaling faster than it has in a generation. More than 30 countries operate reactors today, over 75 are under construction, and roughly 35 more are preparing to start. The thing that breaks first under that kind of growth is not the reactor physics. It is the supply chain and the coordination around it.

A developer reaches detailed design and finds that much of its bill of materials has no qualified supplier at scale. An operator takes a unit offline because one forging sits on a fourteen-month lead time and there is no fast way to find an alternative. A capable manufacturer never hears about the work, because the tools for finding it are directories from another era: gatekept, thin, and blind to whether a supplier is actually qualified.

nuclear.supply is the operational hub for that supply chain. It is open to search and verified to transact. Suppliers carry their real qualifications in the open, NQA-1, ISO 19443, safety-class scope, so buyers can see who can do the work rather than who paid to be listed. Every order, inspection, and non-conformance is recorded, so trust compounds across the industry instead of starting from zero on every project.

We built it open and on a shared set of objects rather than a fixed set of features. A quality manager at a forging shop and an operator at an MSR developer work with the same underlying things but need different views of them. Our roadmap makes that practical: a published object model, an interface teams can adapt, and an API that exposes the data directly.

We are building this to help the nuclear industry develop faster, without cutting the corners the industry exists to protect. What you are using now is our first attempt at the shape. It is wrong in places. Tell us where.

nuclear.supply