Product1 publisher2 min readPublished
Blykalla is running Microsoft-built reactor filings past the NRC before any formal application
The platform converts engineering data and safety analyses into licensing documents in English and Swedish, and Blykalla's head of AI puts the goal at cutting documentation time and resources by 90 percent. The American test is a pre-application discussion with the NRC.
The Product Desk · Product desk

What happened
- Blykalla has deployed a computational platform developed with Microsoft that automates the evaluation of reactor data against regulatory criteria and converts test datasets into technical licensing filings.
- In the United States the platform is handling technical filings for pre-application discussions with the Nuclear Regulatory Commission, and in Sweden it supports plans to build two advanced reactor parks.
- SEALER, the lead-cooled design behind those filings, uses Blykalla's patented aluminium-alloyed steel to stop molten lead leaching iron and nickel out of the steel at high temperature.
Compiled by The Product DeskSomething wrong?How this is made
Why it matters
- constraint The 90 percent target covers preparing documents, so it touches Blykalla's own clock. How long an authority spends reviewing the package sits outside the platform entirely.
- exposure Anyone quoting the 90 percent as a benchmark for their own compliance program is quoting a goal stated by the vendor's head of AI, not a result measured against a published before figure.
- decision Teams building a similar drafting pipeline have to choose which submission they test it on, and a pre-application discussion costs less to get wrong than a filed application.
- capability Bilingual output lets one document pipeline feed a Swedish submission and an American one, work that otherwise needs two separate teams writing to two authorities.
Somebody at Blykalla still has to take the test data from a reactor cooled by molten lead and turn it into a document a licensing authority will accept. The platform built with Microsoft works on that step, converting engineering documentation, test data and safety analyses into compliant filings for European and American authorities, and it does that work in English and Swedish [14][4].
The 90 percent and the "years to months" are one target counted twice. Ten percent of a 24-month preparation cycle is 2.4 months, and ten percent of a 60-month cycle is 6 months [15]. Blykalla has not published the cycle time it is measuring against [16].
"Together with Microsoft, we aim to take licensing documentation from years to months, cutting time and resources by 90% while keeping the rigor regulators expect," said Jon Christensen, Head of AI at Blykalla [7]. The company describes the system as designed to cut documentation time and resources by 90% without lowering nuclear safety standards [3].
The document being compressed is an unusual one. Lead-cooled reactors were first deployed in the 1960s [11], and the failure they are known for is chemical: at sustained high temperatures liquid lead pulls iron and nickel out of standard stainless steel and weakens structural components over time [9]. Blykalla's answer is a patented aluminium-alloyed steel, where the aluminium forms a stable protective boundary on the surface and stops the lead stripping those elements out [10]. That material case goes into a SEALER filing alongside the reactor case [8].
The American work is pre-application discussions with the Nuclear Regulatory Commission [6]. In Sweden, the same platform supports plans for two advanced reactor parks [5]. Pre-application is the cheap place to find out how a reviewer reacts to a machine-assembled package.
For anyone considering a pipeline like this against a regulated submission, the first thing to test is whether the stage it touches runs on your clock or the reviewer's, because drafting is yours and review is not. The other is whether a qualified person can check the output faster than they could have written it themselves. Where both hold, a large cut is genuinely available. Where the second fails, the saving moves instead of appearing: three weeks off the writer plus one week added to the only person who can sign leaves a saving of two weeks.
What to watch
- Whether NRC staff comment in pre-application discussions on how the technical filings were assembled.
- Whether Blykalla publishes a baseline cycle time or page count that the 90 percent target can be measured against.
- Whether the two Swedish reactor parks move from plans to a formal submission using the same document pipeline.