Every analysis type

Seventeen analysis types on one solver — code_aster, the research code EDF assesses nuclear plant with, built natively for Windows.

Thermal does not get a solver of its own. It belongs to whichever solver is already in the case — which is a design decision, not a limitation.

One Elmer integration covers electromagnetics, thermal, elasticity and acoustics — with coupled-field solution built in rather than bolted on.

No new solver, no new mesh path, no new results reader. The whole family is a loop over the existing case model, which is why it is the cheapest capability on the roadmap and the one that changes how the product is used.

Structure-borne and air-borne noise on the same mesh path as everything else — and the aeroacoustic half already exists inside the CFD module.

A coupled case is its own case type, not a checkbox on an existing one. The cheap half answers most of the question and needs no coupling library at all.

Justified by one thing only — the adjoint. Shape sensitivities across many design variables at roughly the cost of a single run, which a parameter sweep cannot match.

The right tool for events no implicit solver can touch — milliseconds, large deformation, contact everywhere, and no equilibrium to iterate towards.

Local only. OpenRadioss is AGPL-3.0, so it ships as a desktop subprocess and is deliberately not offered on the provisioned backend — running it as a remote service is the case where AGPL section 13 would reach the whole work. Remote execution stays available for every other module.