Fusion · In beta

The people who model fusion are the heroes. The plumbing is the villain.

A first-of-a-kind machine takes a dozen realms of physics, codes from every decade, and teams who rarely share a language — literally. The physicists and engineers who make that work are extraordinary. What they spend most of their week on is not.

The machine

Where Morton Labs started and where the platform runs today. Plasma, neutronics, tritium, heat, structure — each its own department, its own codes, its own decades of hard-won validation. None of it was built to talk to the rest.

A tokamak-class chamber drawn as linework: vacuum vessel, first-wall tiles, D-shaped toroidal-field coils, central solenoid, and helical field lines through the plasma.
What this looks like in fusion

One question about one component pulls on every thread.

Each reactor design is built from millions of components. Each component's behavior in an extreme environment is its own realm of physics, with its own codes, built and maintained by different institutions, in different languages, leaving results scattered across scratch disks and archives. The highlighted thread is one question about one component.

The fusion simulation ecosystem: reactor designs, the realms of physics inside them, the simulation codes for each, who builds and maintains those codes, the languages they are written in, and where their results end up — with one component's question traced through all sixAReactor designsmillions of components eachBRealms of physicsbehavior in extreme environmentsCSimulation codeswhat runs the simulationsDWho maintains themuniversities · labs · industry · OSSELanguageswhat the codes are written inFWhere results livesimulation + experimental dataSTELLARATORLASER-DRIVENINERTIAL FUSIONMIRRORS & FRCSPLASMA & MHDIMPLOSIONNUCLEAR REACTIONS& ACTIVATIONHYDROGEN &TRITIUM TRANSPORTHEAT TRANSFERCFD &THERMAL-HYDRAULICSSTRUCTURAL &MATERIALSELECTROMAGNETICSGEANT4MOOSEOPENFOAMTMAP8FESTIMWARPXRAD-HYDRO CODES(RESTRICTED)COMMERCIALCAE SOLVERSUNIVERSITIESINTERNATIONAL LABSCOMMERCIAL VENDORSOPEN-SOURCECOMMUNITIESIN-HOUSE TEAMSFORTRANCPYTHONRUST (EMERGING)SHELL & BUILD GLUEEXPERIMENTAL RECORDS(FACILITY ARCHIVES)FUSION DATABASESNUCLEAR DATA LIBRARIES(ENDF/B, JEFF)SPREADSHEETS &SLIDE DECKSSOMEONE'SHOME DIRECTORYTOKAMAKNEUTRON TRANSPORTOPENMCU.S. NATIONALLABORATORIESC++LOCAL DISKS &HPC SCRATCHONE QUESTION ABOUT ONE COMPONENT PULLS ON A THREAD THROUGH EVERY COLUMN
Open-source codes and public data libraries by name; restricted codes, laboratories and vendors as categories.
The villain

More complex systems are harder to simulate.

Combine large datasets across multiple realms of physics, with modeling tools written in a variety of languages, and you have a systems engineering nightmare. It doesn't defeat your scientists. It taxes them — a little of every day.

The same fusion simulation ecosystem drawn as it is lived: the realms of physics in the middle, and designs, codes, institutions, languages and result stores around them, every dependency crossing every otherSTELLARATORLASER-DRIVENINERTIAL FUSIONMIRRORS & FRCSPLASMA & MHDIMPLOSIONNUCLEAR REACTIONS& ACTIVATIONHYDROGEN &TRITIUM TRANSPORTHEAT TRANSFERCFD &THERMAL-HYDRAULICSSTRUCTURAL &MATERIALSELECTROMAGNETICSGEANT4MOOSEOPENFOAMTMAP8FESTIMWARPXRAD-HYDRO CODES(RESTRICTED)COMMERCIALCAE SOLVERSUNIVERSITIESINTERNATIONAL LABSCOMMERCIAL VENDORSOPEN-SOURCECOMMUNITIESIN-HOUSE TEAMSFORTRANCPYTHONRUST (EMERGING)SHELL & BUILD GLUEEXPERIMENTAL RECORDS(FACILITY ARCHIVES)FUSION DATABASESNUCLEAR DATA LIBRARIES(ENDF/B, JEFF)SPREADSHEETS &SLIDE DECKSSOMEONE'SHOME DIRECTORYTOKAMAKNEUTRON TRANSPORTOPENMCU.S. NATIONALLABORATORIESC++LOCAL DISKS &HPC SCRATCHTHE SAME THREAD, DRAWN WHERE THE WORK ACTUALLY HAPPENS
Where the week goes
Rewriting the same glue
Format shims, mesh handoffs, unit conversions — rebuilt for every pair of codes, by hand.
Rebuilding packages
Compilers, dependencies, the one flag nobody wrote down. Physicists doing DevOps.
Verifying by hand
Did the run use the inputs we think it did? Which version? Against which benchmark?
Chasing results
The answer exists — on the scratch space of someone who has since moved on.
The plot twist

AI doesn't solve this. It multiplies it.

Frontier models and agents are very good at generating: more candidate designs, more runs, more surrogates, more results. Every one of them still has to be managed, integrated into the design, and validated before anyone will trust it. AI provides the brain. It does not provide the nervous system.

Agents generate designs, run campaigns and fit surrogates; the runs fan out and land on local disks, HPC scratch, home directories and slide decks with nobody validating them or connecting them to a designAGENT · GENERATE DESIGNSAGENT · RUN CAMPAIGNSAGENT · FIT SURROGATESMORE INTELLIGENCEMORE RESULTSLOCAL DISKHPC SCRATCHHOME DIRECTORYSLIDE DECKNOBODY OWNS THEM
Where Morton Labs fits

The engineering control plane.

Intelligence sits above. Physics codes, experimental data, and the hardware itself sit below. Morton Labs is the layer between: it securely connects, orchestrates, and validates the simulation capabilities your teams already trust, and keeps the record that turns results into decisions.

AI provides the brain. Morton Labs is the nervous system.

WE CONNECT INTELLIGENCE TO THE WORLD'S SIMULATION AND DATA ASSETS, ORCHESTRATE THE WORK, AND KEEP THE RECORD
  • More intelligence — more runs, designs and surrogates to coordinate.
  • More complexity — more results to keep consistent with each other.
  • More critical decisions — a higher bar for what anyone will trust.
Your scientists, doing their best work

Your people keep their tools. Morton Labs keeps them coordinated.

Plasma, neutronics, thermal-hydraulics, structural, tritium — each department keeps the codes it knows and trusts. Morton Labs is the harness that runs them as one workflow, the orchestration that executes campaigns on laptop, cluster, or cloud, and the system of record that makes every result traceable. Agents run the campaigns. People make the calls.

Five physics departments feed the Morton Labs layer — harness, orchestration, system of record — which feeds design, review, and operationsPLASMANEUTRONICSTHERMAL-HYDRAULICSSTRUCTURALTRITIUM & FUELMORTON LABSHARNESSORCHESTRATIONSYSTEM OF RECORDDESIGNREVIEWOPERATEORCHESTRATED · VERSIONED · AUDITABLE

The platform is in beta with first users. We work with leading fusion companies and U.S. national laboratories, connecting the codes they already trust into orchestrated, versioned workflows.

See it against your fusion stack

IN BETA · 48-HOUR RESPONSE
Get a demo