Commissioned Research
Top 10 Best Radiation Simulation Software of 2026

GITNUXSOFTWARE REVIEW

Science Research

Top 10 Best Radiation Simulation Software of 2026

Compare radiation simulation software options like SCALE, FLUKA, and MCNP, with practical tradeoffs for researchers and engineering teams.

20 min readUpdated Editorially scoped research
How we ranked these tools
01Editorial Scope

Vendors set the topic, but our editors set the inclusion criteria and the evaluation framework before research starts.

02Source Research

AI search agents find sources, extract figures with provenance, and aggregate written reviews. They also transcribe video reviews and podcasts.

Read our full methodology →

Framework: Features 40% · Ease 30% · Value 30%

Gitnux may earn a commission through links on this page. This does not influence our reviews. Editorial policy

Radiation simulation software matters for turning detector, shielding, and radiotherapy geometry into repeatable dose and interaction predictions that production teams can defend in engineering reviews. This comparison helps analysts and operators weigh Monte Carlo transport, clinical radiotherapy calculation, and integration needs such as API access, automation workflows, and data model fit, including platforms like FLUKA when mechanism-level fidelity is the deciding constraint.

SCALE is the best pick for enterprise teams doing licensing-grade shielding and source-term studies because it runs an end-to-end workflow that keeps nuclear-data prep and transport execution consistent across cases, whereas FLUKA suits research groups needing configurable, high-fidelity Monte Carlo physics with scoring for dose and activation in one run.

Editor’s top 3 picks

Three quick recommendations before you dive into the full comparison below — each one leads on a different dimension.

Editor pick
1

SCALE

Integrated nuclear-data preparation and radiation-transport execution inside a single SCALE run workflow.

Best for: Fits when teams need repeatable shielding and source-term simulations with controlled nuclear data handling.

2

FLUKA

Editor pick

Complete particle production and transport physics with configurable scoring to generate both dose and activation-related outputs in one Monte Carlo run.

Best for: Fits when research teams need high-physics-fidelity Monte Carlo shielding, dose, and activation with controlled scoring.

3

MCNP

Editor pick

High-fidelity photon, electron, and neutron scoring with integrated variance reduction and detailed tally controls.

Best for: Fits when radiation transport teams need benchmarkable Monte Carlo results for shielding and mixed fields.

Comparison Table

1
SCALEBest overall
enterprise
9.3/10
Overall
2
enterprise
8.9/10
Overall
3
enterprise
8.8/10
Overall
4
vertical specialist
8.3/10
Overall
5
vertical specialist
8.0/10
Overall
6
vertical specialist
7.8/10
Overall
7
vertical specialist
7.4/10
Overall
8
enterprise
7.2/10
Overall
9
vertical specialist
6.8/10
Overall
10
enterprise
6.5/10
Overall
#1

SCALE

enterprise

Standardized Computer Analyses for Licensing Evaluation nuclear safety analysis suite from Oak Ridge National Laboratory.

9.3/10
Overall
Features9.0/10
Ease of Use9.5/10
Value9.5/10
Standout feature

Integrated nuclear-data preparation and radiation-transport execution inside a single SCALE run workflow.

SCALE is most useful when simulations need reproducible nuclear data handling, including library selection and processing steps before transport runs. Its workflow centers on creating a complete model that includes source definition, material composition, and detector or tally locations, then running the transport and extracting results in the same project structure. This structure helps teams compare runs across shielding revisions without manually reassembling inputs each time.

A key tradeoff is that SCALE favors an opinionated workflow over highly free-form geometry or rapid GUI-driven iteration, so deeper changes often require input edits and careful verification of run settings. SCALE fits best when recurring studies target well-defined shielding layouts or source-term configurations, such as facility shielding design reviews or transport-backed dosimetry baselines.

Pros
  • +End-to-end case workflow with consistent inputs and outputs across runs
  • +Tightly integrated nuclear-data processing with transport execution
  • +Strong support for coupled reactor-physics and radiation-transport studies
  • +Deterministic and Monte Carlo paths for different accuracy and runtime tradeoffs
Cons
  • –Workflow-driven modeling reduces flexibility for highly custom setups
  • –Verification of geometry and source definitions can be time-consuming
  • –Advanced workflows require familiarity with input conventions and module choices
  • –Visualization and post-processing are less tailored than dedicated plotting tools
Use scenarios
  • Radiation safety engineers

    Facility shielding dose mapping

    Comparable dose results across revisions

  • Nuclear design analysts

    Coupled neutron and photon transport

    Integrated transport-backed conclusions

Show 2 more scenarios
  • Research teams

    Variance-managed Monte Carlo studies

    More stable tallies per run

    Define scoring regions and run multiple configurations to stabilize response for dose-relevant metrics.

  • Regulatory documentation teams

    Standardized simulation baselines

    Lower rework for revisions

    Use SCALE workflows to reproduce inputs and generate consistent output artifacts for review cycles.

Best for: Fits when teams need repeatable shielding and source-term simulations with controlled nuclear data handling.

#2

FLUKA

enterprise

Monte Carlo simulation package for particle transport and interactions with matter.

8.9/10
Overall
Features8.9/10
Ease of Use8.9/10
Value8.9/10
Standout feature

Complete particle production and transport physics with configurable scoring to generate both dose and activation-related outputs in one Monte Carlo run.

FLUKA targets Monte Carlo radiation transport work that needs detailed hadron, lepton, and photon physics in one code. Its core capabilities include dose scoring in voxelized geometries, particle production and transport through complex materials, and support for variance reduction to accelerate rare-event tallies.

FLUKA also supports shielding analysis workflows such as activation and particle-field characterization, with phase-space style I/O for coupling to external sources and downstream processing. The software’s strength centers on physics coverage and scoring control rather than deterministic optics or CAD-first meshing pipelines.

Pros
  • +Extensive particle interaction physics coverage for shielding and activation studies
  • +High-granularity scoring options for energy deposition and track-based quantities
  • +Variance reduction controls for efficient rare-event dose and flux estimation
  • +Material, geometry, and source definitions support repeatable batch runs
Cons
  • –Steeper learning curve for input configuration and scoring setup
  • –Less suited to deterministic transport pipelines and CAD-first coupled meshing workflows
Use scenarios
  • Shielding analysts

    Voxel dose scoring for mixed radiation

    Actionable shielding dose estimates

  • Radiation protection teams

    Activation modeling for facility components

    Safer maintenance planning

Show 1 more scenario
  • Detector simulation engineers

    Rare-event tallies with variance reduction

    Faster statistically stable results

    Improves throughput for low-probability interactions using variance reduction.

Best for: Fits when research teams need high-physics-fidelity Monte Carlo shielding, dose, and activation with controlled scoring.

#3

MCNP

enterprise

General-purpose Monte Carlo N-Particle radiation transport code developed at Los Alamos National Laboratory.

8.8/10
Overall
Features8.8/10
Ease of Use8.8/10
Value8.8/10
Standout feature

High-fidelity photon, electron, and neutron scoring with integrated variance reduction and detailed tally controls.

MCNP performs Monte Carlo radiation transport for photons, electrons, and neutrons across detailed 3D geometries. It supports tallies for dose, particle flux, and custom scoring tied to variance-reduction techniques and phase-space data workflows.

Coupled neutron-photon transport is handled within a single model, which is useful for shielding and mixed-field characterization. Geometry handling and repeatability depend heavily on input configuration and external preprocessing steps for complex CAD-derived models.

Pros
  • +Supports coupled neutron-photon transport in one Monte Carlo run
  • +Extensive tally options for dose-like metrics and particle scoring
  • +Strong variance reduction workflows for improving tally convergence
  • +Works with phase-space inputs for modular source modeling
Cons
  • –Input-file driven configuration slows iteration for complex studies
  • –Geometry setup effort rises sharply for CAD-derived solids and meshing
  • –Python-style automation and API surfaces are limited in core MCNP workflows
  • –Performance tuning relies on careful variance-reduction and tallies
Use scenarios
  • Nuclear safety engineers

    Mixed-field shielding dose tallies

    Defensible shielding margins

  • Radiation transport analysts

    Variance-reduced particle transport runs

    Lower run variance

Show 1 more scenario
  • Monte Carlo workflow teams

    Phase-space handoff between simulations

    Repeatable modeling pipelines

    Uses external preprocessing and phase-space tallies to reuse source data.

Best for: Fits when radiation transport teams need benchmarkable Monte Carlo results for shielding and mixed fields.

#4

TracePro

vertical specialist

Monte Carlo ray-tracing software for optical radiation analysis, illumination design, and stray light studies.

8.3/10
Overall
Features8.3/10
Ease of Use8.3/10
Value8.3/10
Standout feature

Detector scoring is geometry-bound, which keeps exposure map definitions consistent from setup through output generation.

TracePro’s core workflow centers on building a scene from CAD-derived or simplified geometry, then running stochastic ray propagation to compute radiometric outcomes for defined target regions. Detectors and measurement definitions are explicit and tied to the geometry, which reduces ambiguity when mapping results back onto physical components. Source modeling supports point and extended emitters, including intensity control and source orientation, which helps when validating shielding and radiation pattern assumptions against measurements.

Pros
  • +Ray-based Monte Carlo scoring tied directly to detector geometries
  • +Point and extended source setups support repeatable dose and flux comparisons
  • +3D scene import workflow supports rapid iteration on real component shapes
  • +Measurement definitions reduce post-processing steps for exposure maps
Cons
  • –High-detail scenes can increase runtime and memory during ray propagation
  • –Limited support for fully coupled particle transport workflows compared with specialized solvers
  • –Material physics depth for complex radiation-matter processes may require external handling
  • –Requires careful detector placement to avoid sampling artifacts
Use scenarios
  • Radiation safety engineers

    Compare detector exposure across shielding variants

    Faster layout screening cycles

  • Opto-electronics designers

    Validate radiation patterns on components

    Clear design margin evidence

Show 2 more scenarios
  • Medical device R and D

    Study source placement effects on exposure

    More consistent bench-to-model checks

    Runs repeated scene variations to quantify exposure differences at predefined measurement regions.

  • Prototyping teams

    Evaluate geometry changes with quick reruns

    Shorter iteration loops

    Reuses scene structure and reruns measurement definitions to compare outcomes after CAD updates.

Best for: Fits when teams iterate on shielding and exposure patterns for product geometries with detector-focused ray scoring.

#5

PHITS

vertical specialist

Particle and Heavy Ion Transport code System for radiation transport simulations.

8.0/10
Overall
Features8.0/10
Ease of Use8.0/10
Value8.0/10
Standout feature

Integrated coupled transport and tallying workflows produce shielding and dose outputs in one run configuration.

PHITS is used for radiation transport studies that include neutron and photon interactions, such as material shielding, accelerator beamline components, and mixed-field occupational exposure scenarios. The package includes geometry and material definitions that feed directly into transport runs and tally generation, which supports end-to-end study setups without manual file stitching. Output is oriented around radiation quantities such as dose-like energy deposition and spectra, which helps when results must be compared across shielding configurations. PHITS also supports variance reduction techniques that are commonly needed for deep penetration and low-probability event regions.

Pros
  • +Single input workflow covers coupled neutron-photon transport and shielding tallies
  • +Voxelized geometry support enables direct dose mapping outputs
  • +Variance reduction controls target low-probability transport regions
  • +Phased source and beam modeling supports spectra and energy deposition studies
Cons
  • –Input-heavy configuration slows first runs for new users
  • –Automation via API is not the primary workflow compared with input-file execution
  • –Advanced setups can require careful physics and material library selection
  • –Debugging complex runs can be harder when input assumptions are opaque
Use scenarios
  • Radiation shielding engineers

    Assess neutron and photon shielding thickness

    Faster shielding configuration comparisons

  • Medical physics groups

    Model voxel phantom dose distributions

    Consistent phantom dose maps

Show 2 more scenarios
  • Accelerator beamline designers

    Simulate beamline component radiation fields

    Quantified component radiation outputs

    Models beam and material stacks and produces particle fluence and spectra outputs for components.

  • Nuclear research analysts

    Study mixed-field transport and interactions

    Unified mixed-field transport results

    Combines neutron and photon interactions to evaluate radiation outcomes across materials and geometries.

Best for: Fits when teams need repeatable transport runs for shielding and dose mapping from input files.

#6

PRIMO

vertical specialist

Monte Carlo simulation software for radiotherapy dose calculation in clinical linac geometries.

7.8/10
Overall
Features7.8/10
Ease of Use7.9/10
Value7.7/10
Standout feature

Study configuration templates for parameter sweeps that keep geometry, sources, and outputs consistent across runs.

PRIMO from primoproject.net targets radiation simulation workflows with a focus on practical engineering outputs like dose mapping and shielding analysis. The tool’s core strength is running repeatable radiation transport studies that translate geometry and source definitions into analyzable results.

Pros
  • +Workflow-oriented runs that convert geometry and source inputs into analyzable dose outputs
  • +Scenario iteration is faster than manual rework when study parameters change
  • +Results are organized for comparison across multiple shielding and dose cases
  • +Configuration-driven study definitions reduce reliance on ad hoc run scripts
Cons
  • –Monte Carlo style inputs and tuning require careful setup discipline
  • –Integration depth with external CAD and mesh pipelines depends on additional tooling
  • –Automation and API capabilities are limited compared with broader engineering tool ecosystems
  • –Advanced coupled workflows need stronger documentation than a typical first-time setup
Use scenarios
  • Shielding design engineers

    Scenario-based dose mapping for builds

    Faster design iteration

  • Facility engineering teams

    Repeatable shielding studies across layouts

    Comparable results

Show 1 more scenario
  • Radiation test coordinators

    Dose-response studies for test articles

    Clear test planning inputs

    Transforms defined sources into analyzable shielding and dose outputs.

Best for: Fits when engineering teams need repeatable radiation transport study runs with consistent dose and shielding outputs.

#7

matRad

vertical specialist

Open-source treatment planning toolkit for intensity-modulated radiation therapy research.

7.4/10
Overall
Features7.4/10
Ease of Use7.4/10
Value7.4/10
Standout feature

Integrated treatment-planning style voxel dose workflow that supports batch scenario runs for reproducible radiotherapy studies.

matRad is a radiation simulation software focused on treatment-planning style dose calculations for voxelized patient geometries. It supports Monte Carlo style dose engines alongside deterministic transport workflows, and it targets clinical and research dose mapping with tissue heterogeneity.

Pros
  • +Voxel-based dose mapping tailored to radiotherapy planning workflows
  • +Automation-friendly batch runs for parameter sweeps and scenario studies
  • +Multiple transport approaches for dose calculation in heterogeneous media
  • +Study-grade outputs for comparing dose distributions across plans
Cons
  • –Less suited for full accelerator-to-detector modeling than general-purpose multiphysics tools
  • –Advanced Monte Carlo setup choices can require domain tuning
  • –Data exchange with external geometry sources often needs preprocessing
  • –Governance and enterprise-grade audit trails are limited in typical deployments
Use scenarios
  • Radiation oncology researchers

    Plan comparison with uncertainty outputs

    Quantified plan differences

  • Treatment planning engineers

    Heterogeneity-aware dose calculation

    More realistic dose maps

Show 1 more scenario
  • Clinical physics teams

    Scenario sweeps for planning parameters

    Repeatable study runs

    Automates repeatable runs to assess parameter sensitivity in planning.

Best for: Fits when radiotherapy researchers need repeatable dose mapping studies with heterogeneous voxels and scripted scenario runs.

#8

Geant4

enterprise

Open-source Monte Carlo toolkit for simulating particle transport through matter.

7.2/10
Overall
Features7.2/10
Ease of Use7.2/10
Value7.2/10
Standout feature

Physics-process modularity via Geant4 physics lists lets teams swap interaction models without rewriting the event loop.

Geant4 is a radiation simulation framework built for Monte Carlo radiation transport with a physics-process architecture used across detector and shielding studies. It provides configurable geometry with voxelized and CAD-derived workflows via user code, plus material definitions that support realistic interaction modeling. Geant4 exposes extensibility through C++ physics lists, custom processes, scoring primitives, and event-level hooks for dose mapping and particle production tracking.

Pros
  • +Deep Monte Carlo physics-process customization through user-defined physics lists
  • +High control over geometry and material definitions via C++ construction code
  • +Fine-grained scoring with user hooks at track, step, and event levels
  • +Established extension ecosystem for detector components and analysis
Cons
  • –C++-centric configuration makes automation and CI integration harder than GUIs
  • –Variance reduction workflow requires explicit setup and careful validation
  • –Large geometry and high particle counts can drive steep memory and runtime costs
  • –Coupled neutron and photon transport workflows often require tailored physics lists
Use scenarios
  • Detector development teams

    Custom scoring for particle production

    Detailed detector response

  • Shielding simulation engineers

    Event-hook dose mapping in complex geometry

    Region-specific exposure estimates

Show 1 more scenario
  • Physics list authors

    Process customization for interaction studies

    Targeted physics modeling

    Builds physics lists and processes to model specific interactions.

Best for: Fits when teams need configurable Monte Carlo radiation transport for detectors, shielding, or dosimetry with custom physics.

#9

OpenMC

vertical specialist

Community-developed Monte Carlo neutron and photon transport simulation code.

6.8/10
Overall
Features6.8/10
Ease of Use6.8/10
Value6.8/10
Standout feature

Tally system that supports mesh scoring and derived outputs with consistent geometry and particle tracking.

OpenMC is a Monte Carlo radiation transport code built around explicit source and tally definitions, with configuration driven by Python input files. It targets neutron and photon problems with support for coupled workflows through shared geometry and material data.

Pros
  • +Python-driven input configuration with a clear model-to-run workflow
  • +Flexible mesh tallies for spatial dose or flux mapping outputs
  • +Variance reduction controls for handling deep shielding problems
  • +Open source core that supports custom extensions and research workflows
Cons
  • –Input modeling requires careful attention to materials, sources, and tallies
  • –High runtime cost for fine voxel geometry and dense tally grids
  • –Limited built-in GUI tooling for geometry editing and results exploration
  • –Integration with CAD or accelerator-specific pipelines needs external scripts
Use scenarios
  • Shielding analysts

    Mesh tally dose mapping for neutrons

    Spatial dose distributions

  • Criticality and safety teams

    Variance-reduced neutron-photon transport

    Stable tallies faster

Show 1 more scenario
  • Simulation automation engineers

    Python-driven batch generation of inputs

    Reduced setup overhead

    Builds multiple OpenMC runs from Python configuration logic.

Best for: Fits when research teams need auditable Monte Carlo radiation transport with scriptable configuration and mesh scoring.

#10

Serpent

enterprise

Continuous-energy Monte Carlo code for reactor physics and radiation transport.

6.5/10
Overall
Features6.5/10
Ease of Use6.5/10
Value6.5/10
Standout feature

Built-in weight-window generation and adjoint-source sampling for variance reduction in Monte Carlo radiation transport.

Serpent performs Monte Carlo radiation transport for shielding, source, and dose-response studies using geometry, materials, and tallies configured for particle tracking. It supports advanced variance-reduction workflows like weight-window generation and adjoint sampling to improve throughput for rare-event questions.

Pros
  • +Monte Carlo engine supports advanced variance-reduction control for hard-to-sample regions
  • +Tally system covers common radiation outputs for shielding and detector response studies
  • +Input-deck workflow fits HPC batch execution and reproducible simulation runs
  • +Interoperates with phase-space files for coupling into external dose and analysis steps
Cons
  • –User experience relies on text-based configuration rather than a guided GUI
  • –Complex coupled workflows can require careful setup to avoid bias from scoring choices
  • –Large geometries and fine tallies can become memory-bound without tuning
  • –No built-in RBAC or audit log features for multi-admin environments
Use scenarios
  • Reactor shielding analysts

    Weight-window variance reduction for hotspots

    Quicker hotspot estimates

  • Dose-response study teams

    Adjoint sampling for source-response mapping

    Actionable sensitivity results

Show 1 more scenario
  • Radiation postprocessing teams

    Phase-space output for mesh superimposition

    Reusable transport outputs

    Exports phase-space data for downstream dose mapping pipelines.

Best for: Fits when teams need configurable Monte Carlo shielding studies with variance reduction and HPC batch control.

Conclusion

After evaluating 10 radiation simulation software, SCALE stands out as our overall top pick — it scored highest across our combined criteria of features, ease of use, and value, which is why it sits at #1 in the rankings above.

Our Top Pick
SCALE

Use the comparison table and detailed reviews above to validate the fit against your own requirements before committing to a tool.

Frequently Asked Questions About Radiation Simulation Software

Which tool is better for detector-focused ray scoring with consistent exposure maps from setup through output?
TracePro fits detector-focused ray scoring because its geometry-bound detector scoring keeps exposure map definitions consistent from setup through output generation. OpenMC also scores with mesh tallies, but it separates mesh output and downstream visualization rather than keeping detector scoring logic tied to ray-based definitions in one environment.
How do ANSYS SPEOS and COMSOL Multiphysics handle radiation transport compared with Monte Carlo codes like OpenMC and MCNP?
Monte Carlo codes like OpenMC and MCNP track particle histories and compute tallies from explicit source and scoring definitions. OpenMC uses Python-driven configuration with mesh-based tallies and postprocessing for dose mapping, while MCNP emphasizes photon, electron, and neutron scoring with integrated variance reduction and detailed tally controls.
What breaks if coupled neutron-photon transport is modeled in a single workflow versus stitched postprocessing across separate tools?
PHITS can keep coupled neutron-photon transport and tallying in one run configuration, which reduces drift between source, geometry, and scoring setup. When neutron and photon results are stitched across separate pipelines, MCNP-style repeatability can degrade if variance reduction settings and tally definitions change between preprocessing and postprocessing.
When does CAD-to-geometry conversion become a bottleneck in radiation shielding analysis workflows?
Geant4 can accept CAD-derived workflows through user code and voxelized geometry handling, but model-specific geometry conversion effort still determines iteration throughput. PHITS and MCNP depend heavily on input configuration and external preprocessing steps for complex CAD-derived models, which can shift time from transport runs to preprocessing and validation.
How do OpenMC and Serpent differ in variance reduction workflow control for rare-event dose questions?
Serpent includes built-in weight-window generation and adjoint-source sampling, which directly targets throughput for rare events. OpenMC relies on variance reduction through its tally and history sampling setup, and mesh scoring plus postprocessing keeps the simulation output data flow separated from visualization tools.
Which tool is best for treatment-planning style voxel dose mapping with scenario batch runs?
matRad targets voxelized patient geometries with a treatment-planning-style dose workflow and scripted batch runs for scenario comparisons. TracePro can compute radiation effects in a geometry-aware environment, but it does not match the treatment-planning workflow structure used for clinical-style dose mapping pipelines.
How do SCALE and FLUKA manage nuclear data and transport execution consistency across repeated shielding studies?
SCALE couples nuclear-data preparation and radiation transport execution inside a single SCALE run workflow, which reduces inconsistencies between tally inputs and transport parameters. FLUKA centers on physics coverage and configurable scoring with dose and activation-related outputs in one Monte Carlo run, which improves scoring control but shifts repeatability emphasis to run configuration and physics settings.
What is the impact of choosing phase-space style workflows when coupling sources to shielding or dose mapping pipelines?
OpenMC’s data flow centers on variance reduction, particle histories, and tally scoring, which makes mesh-tally outputs well suited for downstream dose mapping. FLUKA supports phase-space style I O for coupling to external sources and downstream processing, while Serpent integrates phase-space workflows that fit into mesh-tally superimposition pipelines.
How do admin controls and security expectations differ between a scriptable Monte Carlo codebase like Geant4 and a managed nuclear workflow like SCALE?
Geant4 extensibility uses C++ physics lists, custom processes, and user code hooks, so governance typically targets configuration control over build artifacts and source code changes. SCALE emphasizes a consistent case-management workflow that centralizes nuclear data handling and run execution structure, which reduces the surface area for ad hoc changes across repeated shielding runs.
Which tool supports structured configuration templates for parameter sweeps while keeping geometry, sources, and outputs consistent?
PRIMO provides study configuration templates designed for parameter sweeps so geometry, sources, and outputs remain consistent across runs. SCALE also supports repeatable shielding and source-term studies, but PRIMO’s workflow emphasis is on structured study outputs for comparison rather than integrated nuclear-data preparation plus radiation-transport execution inside one run.

Tools reviewed

Primary sources checked during evaluation.

Referenced in the comparison table and product reviews above.

How to Choose the Right Radiation Simulation Software

We can usually tell radiation simulation software apart by how it builds and reuses geometry and physics inputs, then how transparently it reports results and convergence. Look first at the radiation transport model coverage, then at dose mapping output control, and finally at automation depth for repeat runs.

Transport model coverage for your case

Why it matters

Transport model coverage affects whether the solver matches your radiation mix and problem type without brittle workarounds. It also controls how trustworthy comparisons will be across runs.

How to check

On a demo, ask the vendor to run your closest sample scenario (similar particle type and energy range) and show which transport modes it enables. Then review the docs for explicit support of coupled vs separated radiation transport and how it handles interfaces.

Geometry and mesh workflow control

Why it matters

Geometry and mesh workflow control determines whether your voxelized phantom, surfaces, and region definitions survive preprocessing and stay consistent. Poor handling here often turns results into a geometry artifact.

How to check

Bring a small geometry/phantom example and ask for an end-to-end run from import to region assignment. Check whether the product logs mesh/region stats and whether you can reproduce the exact processed geometry on a second run.

Dose mapping and tally mapping control

Why it matters

Dose mapping and tally mapping control matters because outputs must line up with the same anatomy/grid you used for the inputs. If mapping is opaque, validation becomes hard.

How to check

In the demo, generate a dose/dose-rate output and then change one tally/binning or grid setting to confirm the mapping responds predictably. Look for output reports that show where values are placed (grid definition, coordinate system, normalization).

Convergence and uncertainty reporting

Why it matters

Convergence and uncertainty reporting tells you whether results are statistically stable and comparable across parameter sweeps. Without clear uncertainty, you can’t judge whether differences come from physics or noise.

How to check

Run the same input twice with increased compute budget or sampling and confirm the uncertainty estimate decreases in a documented way. Verify the output includes convergence criteria indicators and per-region/per-tally uncertainty summaries.

Automation and API for repeat runs

Why it matters

Automation depth reduces manual transcription errors when you batch many scenarios or iterate shielding and beam parameters. A clear API also makes it easier to plug into your lab workflow.

How to check

Ask for a sample batch workflow: parameter sweep over source or geometry settings, producing a consistent folder structure and machine-readable outputs. Check whether there are documented hooks for launching runs, reading results, and setting run parameters programmatically.

Validation examples against published benchmarks

Why it matters

Validation examples against published benchmarks show whether the product reproduces known reference results, not just pretty outputs. That lowers risk when you move from demos to research datasets.

How to check

Request a list of benchmark validations relevant to your radiation type and ask to inspect the figure-level comparison (inputs, assumptions, metrics). Confirm the benchmarks align with the current release notes and solver settings you would use.

Red flags

  • Results lack clear uncertainty or convergence indicators per output region/tally
  • Geometry preprocessing changes regions/coordinates without a reproducible log
  • Automation outputs require manual file edits to reproduce runs consistently

Fit by situation

  • If you frequently rerun shielding or source variants, prioritize automation and API for repeat runs.
  • If your work depends on anatomy grids or voxel phantoms, prioritize geometry and mesh workflow control.
  • If you must compare dose outputs to validation figures, prioritize dose mapping and tally mapping control.
Commissioned Research

Funding and competing interests

This study was co-funded by several of the vendors assessed in it. No single vendor funded it. Funders could propose the market studied.

They had no role in selecting vendors, setting or weighting criteria, analysing data or drawing conclusions, and they received the same factual-accuracy check as every other vendor assessed.

Market definition, inclusion rules and criteria weights were fixed by an editor before research began and did not change afterwards. Editorial process →

Keep exploring

FOR SOFTWARE VENDORS

Not on this list? Let’s fix that.

Our best-of pages are how many teams discover and compare tools in this space. If you think your product belongs in this lineup, we’d like to hear from you—we’ll walk you through fit and what an editorial entry looks like.

Apply for a Listing

WHAT THIS INCLUDES

  • Where buyers compare

    Readers come to these pages to shortlist software—your product shows up in that moment, not in a random sidebar.

  • Editorial write-up

    We describe your product in our own words and check the facts before anything goes live.

  • On-page brand presence

    You appear in the roundup the same way as other tools we cover: name, positioning, and a clear next step for readers who want to learn more.

  • Kept up to date

    We refresh lists on a regular rhythm so the category page stays useful as products and pricing change.