Top 9 Best Pbpk Modeling Software of 2026

GITNUXSOFTWARE ADVICE

Science Research

Top 9 Best Pbpk Modeling Software of 2026

Ranked roundup of pbpk modeling software for technical teams, weighing SimBiology, Pumas, Sisyphus against Gurobi, CPLEX, and OpenFOAM.

27 min readUpdated AI-verified · Expert reviewed
How we ranked these tools
01Feature Verification

Core product claims cross-referenced against official documentation, changelogs, and independent technical reviews.

02Multimedia Review Aggregation

Analyzed video reviews and hundreds of written evaluations to capture real-world user experiences with each tool.

03Synthetic User Modeling

AI persona simulations modeled how different user types would experience each tool across common use cases and workflows.

04Human Editorial Review

Final rankings reviewed and approved by our editorial team with authority to override AI-generated scores based on domain expertise.

Read our full methodology →

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

Gitnux may earn a commission through links on this page — this does not influence rankings. Editorial policy

PBPK modeling software matters when mechanistic absorption, distribution, metabolism, and excretion must be mapped to measurable clinical endpoints with reproducible workflows. This ranked list targets technical teams who need an auditable modeling data model, automation via API or scripting, and throughput under uncertainty, with placement based on integration depth, extensibility, and operational fit rather than feature checklists.

SimBiology is the best fit when you need end-to-end PBPK calibration automation inside a MATLAB-driven workflow, whereas Pumas suits technical teams that want code-driven PBPK iteration and simulation automation via a Julia-first approach.

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

SimBiology

SimBiology model objects integrate with MATLAB code execution for automated calibration loops and scenario reruns.

Built for fits when teams need end-to-end PBPK calibration automation inside a MATLAB-driven workflow..

2

Pumas

Editor pick

Model execution is fully scriptable through Python, enabling repeatable calibration and simulation pipelines.

Built for fits when technical teams need code-driven pbpk iteration, calibration, and simulation automation..

3

Sisyphus

Editor pick

Project-scoped model runs link definition, calibration, and scenario outputs into a single reproducible execution lineage.

Built for fits when technical teams need reproducible PBPK iteration with strong run orchestration..

Comparison Table

1
SimBiologyBest overall
enterprise
9.4/10
Overall
2
API-first
9.1/10
Overall
3
vertical specialist
8.7/10
Overall
4
enterprise
8.4/10
Overall
5
vertical specialist
8.1/10
Overall
6
enterprise
7.8/10
Overall
7
enterprise
7.5/10
Overall
8
7.2/10
Overall
9
API-first
6.9/10
Overall
#1

SimBiology

enterprise

MATLAB software for mechanistic pharmacology models, including PBPK and systems biology simulations.

9.4/10
Overall
Features9.4/10
Ease of Use9.1/10
Value9.6/10
Standout feature

SimBiology model objects integrate with MATLAB code execution for automated calibration loops and scenario reruns.

SimBiology’s modeling workflow centers on building whole-body compartmental systems from parameter definitions, dosing events, and kinetic rules, then running mechanistic pharmacokinetic simulation runs from a consistent model definition. It includes model validation hooks such as checks on mass balance and simulation outputs, then enables iterative parameter estimation loops for calibration against observed concentration-time data. Population variability work can be performed through virtual population generation driven by parameter distributions, which reduces manual scenario management when variability spans interindividual effects.

A practical tradeoff is that scaling to very large PBPK parameter sweeps typically depends on MATLAB execution efficiency and how teams structure model variants and parallel runs. SimBiology fits best when calibration and uncertainty analysis are repeated many times during a project lifecycle, and when teams already standardize on MATLAB for data cleaning, preprocessing, and results reporting.

Pros
  • +Model parameters and simulations are fully scriptable in MATLAB
  • +Population variability and virtual cohort runs connect directly to model states
  • +Reusable model variants support rapid scenario iteration
  • +Results are easy to integrate with MATLAB analysis pipelines
Cons
  • –Large parameter sweeps can hit MATLAB runtime and memory limits
  • –Some PBPK constructs need careful mapping to SimBiology compartment conventions
  • –Teams that require headless server execution may need extra engineering
Use scenarios
  • Clinical pharmacology teams

    Repeated-dose PBPK calibration cycles

    Faster model refinement

  • Modeling automation engineers

    High-throughput virtual cohort simulations

    Consistent variability analysis

Show 1 more scenario
  • Regulatory submission working groups

    Scenario-managed mechanistic simulations

    Tighter documentation traceability

    Versioned model configurations support reproducible outputs for model qualification packages.

Best for: Fits when teams need end-to-end PBPK calibration automation inside a MATLAB-driven workflow.

#2

Pumas

API-first

Julia-based pharmacometric software for population PK, PBPK, and pharmacodynamic modeling.

9.1/10
Overall
Features9.3/10
Ease of Use9.1/10
Value8.8/10
Standout feature

Model execution is fully scriptable through Python, enabling repeatable calibration and simulation pipelines.

Pumas supports end-to-end physiologically based pharmacokinetic modeling with mechanistic model definitions and repeated-dose simulation for scenarios like clinical trial regimen testing. It supports population-style work where model parameters and variability terms can be estimated from datasets and then carried into simulation. Automation is strong because model runs and downstream analyses can be driven from Python scripts that encode dosing, covariates, and analysis settings. The governance story is practical for technical teams since model definitions live in versioned code and runs can be orchestrated through repeatable scripts.

A tradeoff is that deeper governance and reproducibility depends on disciplined code and environment management since core artifacts are model code plus execution scripts rather than a fully locked graphical audit trail. Pumas fits best when a technical group needs to iterate on model structure quickly, generate virtual cohorts, and run uncertainty or sensitivity analyses on a controlled pipeline.

Pros
  • +Python-first model definitions make runs reproducible from code
  • +Mechanistic simulation workflow supports complex dosing regimens
  • +Uncertainty workflows integrate naturally with parameter estimation runs
  • +Programmatic extensibility fits custom model components
Cons
  • –Governance features for non-coders are limited compared with UI-driven tools
  • –Model iteration requires software workflow maturity and testing discipline
  • –Large projects can become slow when parameter grids and cohorts grow
  • –Debugging requires familiarity with model equations and estimation outputs
Use scenarios
  • Pharmacometrics teams

    Population model calibration and regimen simulation

    Consistent predictions across cohorts

  • Research groups

    Virtual cohort generation for hypothesis testing

    Rapid hypothesis screening

Show 1 more scenario
  • Clinical trial modeling teams

    Dose selection for study protocols

    Better-informed dose selection

    Run simulation experiments that mirror planned dosing and follow-on sampling schedules.

Best for: Fits when technical teams need code-driven pbpk iteration, calibration, and simulation automation.

#3

Sisyphus

vertical specialist

Graph-based whole-body PBPK simulation engine that converts SMILES strings and dosing inputs into pharmacokinetic predictions with uncertainty quantification.

8.7/10
Overall
Features8.9/10
Ease of Use8.7/10
Value8.5/10
Standout feature

Project-scoped model runs link definition, calibration, and scenario outputs into a single reproducible execution lineage.

Sisyphus targets teams that build whole-body PBPK designs and need consistent simulation runs across model revisions. The software is documented around a project workflow that connects model definition, parameter estimation runs, and downstream simulation reporting for virtual cohort or scenario outputs. Integration depth is strongest inside a modeling workflow, because the automation surface is oriented toward run orchestration rather than external pipeline control.

A key tradeoff is that Sisyphus is less suited to teams that require deep programmatic control of the model graph from external systems, since its extension points prioritize UI and project execution. Sisyphus works well when a technical pharmacometrics team standardizes a PBPK build for repeated-dose scenarios and uses the same project structure for uncertainty or sensitivity experiments.

Pros
  • +Project-driven PBPK runs keep model revisions reproducible
  • +Mechanistic tissue parameterization supports iterative calibration
  • +Scenario outputs support repeated-dose reporting workflows
  • +Run orchestration fits uncertainty and sensitivity experiments
Cons
  • –Automation is oriented toward project execution over external scripting
  • –Complex model graph edits can be slower than code-based editors
  • –Advanced governance controls like fine-grained RBAC are limited
  • –Third-party integration relies more on export than API
Use scenarios
  • Pharmacometrics modelers

    Iterative PBPK calibration and qualification checks

    Fewer mismatched model versions

  • Clinical programming teams

    Repeated-dose simulation for trial simulation

    Stable trial simulation inputs

Show 2 more scenarios
  • Modeling scientists

    Uncertainty and sensitivity testing

    Faster sensitivity throughput

    Orchestrate batch experiments that reuse the same PBPK structure with controlled parameter perturbations.

  • Regulated environment teams

    Audit-ready model revision lineage

    Traceable simulation outputs

    Maintain an execution history tied to each project revision so results can be regenerated for comparison.

Best for: Fits when technical teams need reproducible PBPK iteration with strong run orchestration.

#4

GastroPlus

enterprise

PBPK software for mechanistic drug absorption, distribution, metabolism, and excretion modeling.

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

Built-in GI absorption and formulation-linked mechanistic setup tied directly into disposition simulations and calibration runs.

GastroPlus from Simulations Plus is used for mechanistic pharmacokinetic simulation with a workflow tuned for oral and formulation-relevant processes. It couples gastrointestinal and permeability and dissolution style absorption modeling with whole-body physiologically consistent disposition models.

Parameter estimation workflows support calibration against clinical or preclinical concentration-time data for deterministic and stochastic uncertainty runs. Drug–drug interaction handling focuses on enzyme and transporter mediated effects within the PK structure used by GastroPlus.

Pros
  • +Mechanistic oral absorption modeling integrated into the PK simulation workflow
  • +Supports uncertainty and sensitivity runs around calibrated parameters
  • +Drug–drug interaction modeling via enzyme and transporter effect settings
  • +SBML import and export supports model portability for downstream tooling
Cons
  • –Automation and API surface are limited compared with code-first PBPK toolchains
  • –Custom physiology beyond built-in tissue and transport patterns takes more manual configuration

Best for: Fits when teams need mechanistic oral absorption plus PBPK disposition calibration in one workflow.

#5

PK-Sim

vertical specialist

Open-source PBPK software for mechanistic pharmacokinetic modeling and simulation.

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

PB-Sim’s physiology-driven model builder ties parameter changes to whole-body tissue compartments through a configurable PBPK model setup.

PK-Sim builds physiologically based pharmacokinetic models using a whole-body compartment structure and tissue perfusion-limited representations. It supports mechanistic PBPK workflows that connect physiological parameters, drug-specific processes, and simulation outputs into a reusable model setup.

The project also provides SBML import and export paths for model exchange, which reduces manual re-encoding when models must move between tools. Model calibration and virtual population generation workflows are designed to support parameter inference and interindividual variability studies.

Pros
  • +Physiological whole-body model templates that map to PBPK structure directly
  • +SBML import and export for exchanging PBPK structures with external tools
  • +Virtual population generation for interindividual variability and repeat simulations
  • +Parameter estimation workflows that support uncertainty-driven calibration loops
Cons
  • –Governance discipline is needed to keep model versions and parameter sets consistent
  • –Some model variants require extra configuration to cover specific absorption and transport edge cases

Best for: Fits when teams need mechanistic PBPK model reuse and SBML-based exchange across modeling workflows.

#6

NONMEM

enterprise

Nonlinear mixed-effects modeling software for population pharmacokinetic and pharmacodynamic analysis.

7.8/10
Overall
Features7.9/10
Ease of Use7.5/10
Value8.0/10
Standout feature

Nonlinear mixed-effects inference with the NONMEM control stream as the primary modeling interface for PBPK calibration.

NONMEM supports physiologically based pharmacokinetic model development with nonlinear mixed-effects parameter estimation using a long-established estimation engine. It is distinct for handling population variability and interindividual variability directly within model fitting workflows, including covariate-driven effects and repeated-dose simulation.

The core PBPK workflow centers on defining compartments, structures, and likelihood-based estimation in NONMEM’s control stream, then validating model behavior through simulation and diagnostics. For teams needing regulatory-grade nonlinear mixed-effects calibration and Bayesian-style uncertainty workflows, NONMEM remains a primary choice inside mechanistic pharmacokinetic simulation pipelines.

Pros
  • +Proven nonlinear mixed-effects estimation engine for PBPK parameter fitting
  • +Control-stream workflow supports reproducible mechanistic model definitions
  • +Population variability modeling supports covariates and individual-level parameter draws
  • +Simulation and diagnostics support iterative model qualification cycles
Cons
  • –PBPK model implementation relies on manual control-stream coding
  • –Integration with external model management and automation requires added engineering effort
  • –Governance controls like fine-grained RBAC and audit logs are not the focus
  • –Automation for high-throughput batch runs needs scripting around the core

Best for: Fits when technical teams run PBPK population calibration with scripted, reproducible NONMEM control workflows.

#7

ADAPT 5

enterprise

Adaptive control, pharmacokinetic, and pharmacodynamic modeling software developed at USC.

7.5/10
Overall
Features7.7/10
Ease of Use7.5/10
Value7.2/10
Standout feature

SBML import/export support tied to ADAPT 5’s native compartment modeling workflow for PBPK model artifact portability.

ADAPT 5 couples a whole-body compartment modeling workflow with nonlinear mechanistic simulation suited to physiologically based pharmacokinetic model development. The software supports parameter estimation and population variability workflows for interindividual differences, including virtual population generation and repeated-dose simulation.

ADAPT 5 also provides SBML import and export for integrating model artifacts into external toolchains and reporting pipelines. Built-in visual and code-driven model building supports calibration, uncertainty analysis, and model qualification style iterations for mechanistic system studies.

Pros
  • +SBML import and export for cross-tool model exchange
  • +Whole-body compartment modeling workflow with mechanistic simulation support
  • +Population variability workflows for virtual population generation
  • +Integrated estimation loops for parameter calibration
Cons
  • –Extensibility and automation depend on scripting patterns and workflow discipline
  • –Model build and validation cycles can take longer than template-heavy tools
  • –Complex PBPK structures require careful data and parameter mapping
  • –Integration depth with non-SBML ecosystems can be limited

Best for: Fits when technical teams need mechanistic PBPK modeling with estimation and population simulations plus SBML-based exchange.

#8

Simcyp Simulator

enterprise

Physiologically based pharmacokinetic and pharmacodynamic simulation software for clinical development.

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

Population-driven PBPK simulations that couple mechanistic absorption and tissue disposition within repeat-dose study definitions.

Simcyp Simulator from Certara is built for mechanistic physiologically based pharmacokinetic modeling workflows using population-driven simulation rather than purely deterministic PK fitting. It provides virtual population generation, mechanistic tissue modeling tied to blood flow and permeability assumptions, and repeatable clinical-trial style simulation scenarios.

The tool supports parameter estimation and uncertainty analysis for population variability, with model calibration that can be iterated across dosing regimens and exposure endpoints. Its strongest differentiation is end-to-end support for PBPK workstreams that move from mechanistic structure through population simulation to qualification-ready artifacts.

Pros
  • +Virtual population generation supports interindividual variability in simulation studies
  • +Mechanistic tissue models map physiology to exposure outcomes for repeated dosing designs
  • +Parameter estimation workflows support iterative calibration against observed data
  • +Clinical-trial style scenario setup keeps model runs reproducible across regimens
Cons
  • –Automation depth depends on project setup conventions and scripting add-ons
  • –SBML interchange is limited compared with broader PBPK ecosystems
  • –Model performance can be sensitive to population size and uncertainty run settings
  • –Deep customization of internal components often requires specialized modeling expertise

Best for: Fits when teams need population-based PBPK simulation with mechanistic tissue structure for trial scenarios.

#9

mrgsolve

API-first

Open-source R and C++ simulation framework for pharmacometric and mechanistic models.

6.9/10
Overall
Features6.9/10
Ease of Use6.6/10
Value7.1/10
Standout feature

The mrgsolve model definition compiles to a high-performance simulation engine using C++ code blocks integrated into R-centric workflows.

mrgsolve is a PBPK modeling tool that executes mechanistic pharmacokinetic simulations from a C++-backed model definition workflow. It generates population-level predictions using a NONMEM-style interface for compartments, covariates, and event streams.

The tool supports configuration-driven dosing and sampling schedules, plus parameter estimation workflows built around nonlinear mixed-effects modeling. Extensibility comes through custom model code that compiles into simulation-ready executables.

Pros
  • +C++-backed model code gives fast simulation throughput
  • +NONMEM-style model syntax helps teams reuse existing domain patterns
  • +Event-table dosing and sampling make study replication repeatable
  • +Extensible model functions support custom absorption and clearance logic
Cons
  • –Model compilation adds friction for frequent small edits
  • –Population-level workflows require disciplined data formatting
  • –Uncertainty analysis and calibration are possible but not out-of-the-box for all users
  • –Interoperability around SBML and external tools can be limited by workflow fit

Best for: Fits when teams need code-driven PBPK simulation and fast repeat runs for clinical study planning and model iteration.

Conclusion

After evaluating 9 science research, SimBiology 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
SimBiology

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

How to Choose the Right pbpk modeling software

PBPK modeling software covers physiologically based pharmacokinetic workflows where whole-body compartments, tissue partitioning, and dosing scenarios are assembled into mechanistic simulation runs.

This guide covers SimBiology, Pumas, Sisyphus, GastroPlus, PK-Sim, NONMEM, ADAPT 5, Simcyp Simulator, and mrgsolve, with an integration-first lens on automation and API surface. The coverage also highlights how model definition can be code-driven in Python and MATLAB, project-orchestrated in Sisyphus, or control-stream scripted in NONMEM.

PBPK modeling software for mechanistic physiologically based PK simulation and calibration

PBPK modeling software builds mechanistic PBPK model graphs that connect physiological structures to exposure outputs, then runs population or scenario simulations for tasks like parameter estimation and uncertainty analysis.

SimBiology targets MATLAB-centered teams by making model parameters and simulation runs scriptable for automated calibration loops and scenario reruns, and it connects population-style cohort execution directly to model states. Pumas targets code-first teams by running model execution through Python so calibration and simulation pipelines stay reproducible from versioned code. Tools like PK-Sim emphasize physiology-driven whole-body model setup and SBML-based exchange for sharing PBPK structures across modeling workflows.

PBPK modeling evaluation: automation, execution control, and model exchange

Automation determines whether PBPK parameter estimation and scenario reruns happen as repeatable runs instead of manual rerun sessions. SimBiology scripts model parameters and simulations in MATLAB so calibration loops and scenario reruns execute from the same code path.

Execution control matters because PBPK teams need to reproduce exactly which model revision produced which trial scenario output. Sisyphus keeps project-scoped model runs linked across definition, calibration, and scenario outputs into a single execution lineage.

  • Scriptable model execution for calibration loops

    SimBiology model parameters and simulations are fully scriptable in MATLAB, and Pumas runs model execution through Python so calibration and simulation pipelines remain reproducible from code.

  • Project-scoped reproducibility and run orchestration

    Sisyphus ties model definition, calibration inputs, and scenario outputs into project-scoped runs so model revisions stay traceable across iteration cycles.

  • SBML model interchange for cross-tool PBPK artifacts

    PK-Sim supports SBML import and export to exchange PBPK structures with external tools, and ADAPT 5 provides SBML import and export tied to its native compartment workflow.

  • Mechanistic oral absorption integration with disposition modeling

    GastroPlus integrates mechanistic oral absorption modeling directly into disposition simulation and calibration runs, while Simcyp Simulator couples mechanistic absorption and tissue disposition for repeated-dose study definitions.

  • Population simulation and interindividual variability workflows

    Simcyp Simulator uses virtual population generation for interindividual variability across simulation studies, and SimBiology connects population-style cohort execution to model states for virtual cohort runs.

Selecting PBPK modeling software around code control, interchange, and governance depth

The fastest way to narrow choices is to start from the execution philosophy a team will standardize on. Teams already centered on MATLAB typically prioritize SimBiology because model states, parameters, and runs become scriptable in MATLAB for automated calibration.

Code-first teams that standardize on Python typically prioritize Pumas because the model execution workflow is fully scriptable in Python for repeatable calibration and simulation pipelines. Teams that need SBML-based exchange across modeling environments can choose PK-Sim or ADAPT 5 because SBML import and export are native to their workflows.

  • Match the runtime language to the calibration loop harness

    If calibration automation lives inside MATLAB orchestration, SimBiology supports fully scriptable model parameters and simulations in MATLAB so reruns and parameter estimation loops share one code path. If calibration pipelines run inside Python services, Pumas executes model definitions through Python for repeatable run execution from versioned code.

  • Pick the reproducibility mechanism that fits the team workflow

    If reproducibility must be carried by the modeling project itself, Sisyphus links definition, calibration, and scenario outputs into project-scoped model runs with a single reproducible execution lineage. If reproducibility is carried by scripts, NONMEM support through a control-stream workflow can keep PBPK estimation runs reproducible through scripted control streams.

  • Choose the interchange route when PBPK artifacts move across tools

    If cross-tool artifact exchange is required, PK-Sim provides SBML import and export for exchanging PBPK structures across modeling workflows. If the workflow must stay aligned with a whole-body compartment modeling workflow while still exchanging artifacts, ADAPT 5 also offers SBML import and export tied to its native modeling workflow.

  • Decide whether mechanistic oral absorption must be native to the PBPK run

    If mechanistic oral absorption and formulation-linked setup must be tied directly to disposition simulations and calibration runs, GastroPlus integrates oral absorption modeling into the same workflow. If repeated-dose trial scenario definitions must couple mechanistic absorption and tissue disposition inside one population simulation engine, Simcyp Simulator provides population-driven PBPK simulations designed for study scenario modeling.

  • Plan around automation limits tied to model graph editing and throughput

    If frequent small model edits happen during iteration, mrgsolve’s model compilation friction can slow changes because its model definition compiles into a high-performance simulation engine using C++ code blocks. If large parameter sweeps require heavy runtime and memory, SimBiology can hit MATLAB runtime and memory limits during broad sweeps.

Who should buy which PBPK modeling software based on execution and interchange needs

PBPK teams should select tools that match how they intend to run calibration and scenario simulations at scale. The right choice depends on whether the standard workflow is script-driven in MATLAB or Python, project-driven through orchestrated run lineage, or interchange-driven via SBML artifacts.

  • MATLAB-centered PBPK teams running automated calibration loops

    SimBiology supports fully scriptable model parameters and simulations in MATLAB so virtual cohort runs and scenario reruns can be executed from the same MATLAB codebase.

  • Python engineering teams building reproducible PBPK pipelines

    Pumas executes model runs through Python so calibration and mechanistic simulation workflows remain reproducible from versioned code.

  • Teams that need run-level lineage across model revisions and scenarios

    Sisyphus keeps project-driven PBPK runs reproducible by linking definition, calibration, and scenario outputs into a single execution lineage.

  • Organizations exchanging PBPK model artifacts across multiple modeling ecosystems

    PK-Sim and ADAPT 5 both provide SBML import and export so PBPK model structures can be exchanged as artifacts rather than rebuilt from scratch.

  • Trial teams requiring population-driven repeated-dose simulation definitions

    Simcyp Simulator supports population-driven PBPK simulations that include mechanistic tissue disposition and repeat-dose study definitions tied to virtual population generation.

Common PBPK modeling buying mistakes that cause avoidable rework

Many buying mistakes come from choosing a tool based on model-building familiarity rather than execution automation requirements. Another mistake is underestimating how much governance discipline is needed to keep model revisions and parameter sets consistent when workflows involve multiple artifacts or exports.

  • Selecting a tool for model editing comfort but ignoring how calibration runs will be automated

    Teams that need repeatable calibration and scenario reruns should evaluate SimBiology scriptability in MATLAB or Pumas Python execution rather than relying on manual rerun habits.

  • Assuming SBML exchange is always equally complete across tools

    SBML interchange is strongest when PK-Sim or ADAPT 5 are used in a workflow where SBML import and export are central rather than an afterthought.

  • Underestimating the configuration overhead for mechanistic edge cases outside built-in physiology patterns

    GastroPlus offers built-in GI absorption and formulation-linked setup, and custom physiology beyond its built-in tissue and transport patterns takes more manual configuration.

  • Choosing a code-compiled simulation engine without accounting for iteration friction

    mrgsolve compiles model definitions into a high-performance C++-backed engine, so frequent small edits can slow the iteration loop when compilation becomes frequent.

  • Expecting UI-first governance controls when the team workflow is code-first

    Pumas supports Python-first reproducibility, and governance features for non-coders are limited compared with UI-driven tools, so non-technical review workflows may need additional process design.

How We Selected and Ranked These Tools

We evaluated the nine PBPK modeling options by weighting features at 40 percent, ease and value each at 30 percent, and we mapped each tool to the execution and interchange mechanisms teams rely on for PBPK calibration and scenario runs. SimBiology set the top position because model parameters and simulations are fully scriptable in MATLAB, and the platform connects population-style cohort execution to model states for automated virtual cohort runs.

We also checked how each tool supports reproducible iteration, including Sisyphus project-scoped run lineage, Pumas Python-driven repeatability, and SBML import and export through PK-Sim and ADAPT 5. We then adjusted ranking for iteration friction and governance fit by considering known constraints like MATLAB runtime and memory limits in large sweeps for SimBiology and compilation friction in mrgsolve.

Frequently Asked Questions About pbpk modeling software

How does SimBiology handle automated PBPK calibration compared with Pumas?
SimBiology builds PBPK model objects inside MATLAB and runs automated calibration loops through MATLAB scripting with repeated-dose simulation reuse. Pumas runs the same kind of iterative fit and rerun workflow through Python, which makes model execution and scenario pipelines script-first rather than MATLAB-first.
Which tool is better for PBPK model exchange using SBML import or export?
PK-Sim supports SBML import and export paths that reduce manual re-encoding when models move across modeling workflows. ADAPT 5 also provides SBML import and export tied to its native compartment modeling workflow for artifact portability.
When should a team choose a Python-driven workflow in Pumas over a C++ execution workflow in mrgsolve?
Pumas fits teams that want the full PBPK iteration loop expressed in Python, including calibration runs and programmatic simulation control. mrgsolve fits teams that need high-throughput repeat runs because its model definition compiles into a C++-backed simulation engine and executes fast event-stream dosing and sampling schedules.
What breaks if the modeling pipeline needs regulatory-grade nonlinear mixed-effects fitting controlled in a control stream?
NONMEM depends on its control stream to define the PBPK model structure, estimation, diagnostics, and repeated-dose simulation behavior. Tools like SimBiology and Pumas can run mechanistic simulations and fits, but the control-stream-first estimation workflow is the core interface for NONMEM’s nonlinear mixed-effects calibration.
Where does GastroPlus fall short for tissue-level partitioning work compared with PK-Sim or ADAPT 5?
GastroPlus emphasizes mechanistic oral and formulation-relevant absorption plus disposition calibration that includes enzyme and transporter mediated effects in its PK structure. PK-Sim and ADAPT 5 focus more directly on physiology-driven compartment setup and tissue parameterization tied to whole-body model structure rather than primarily GI absorption configuration.
How does Sisyphus support reproducible PBPK iteration across multiple scenarios?
Sisyphus structures work as project-scoped model runs that connect model definition, calibration, and scenario outputs into a single reproducible execution lineage. This approach makes regenerated scenario comparisons traceable at the project execution level rather than only through external scripting.
How do population workflows differ between Simcyp Simulator and NONMEM for uncertainty analysis?
Simcyp Simulator centers on population-driven PBPK simulation with virtual population generation tied to clinical-trial style scenario definitions. NONMEM centers on nonlinear mixed-effects inference in its control stream for population variability and covariate-driven effects, which changes how uncertainty analysis is expressed and validated.
Which tool supports mechanistic oral and GI absorption models tied directly into PBPK disposition calibration?
GastroPlus provides built-in GI absorption and formulation-linked mechanistic setup that ties directly into disposition simulations and calibration runs. SimBiology and Pumas can implement mechanistic structures through their model-building environments, but GastroPlus’s workflow is specialized around GI absorption configuration as a native starting point.
How should teams plan data model and event scheduling when moving from a Python workflow in Pumas to a C++ engine in mrgsolve?
Pumas uses Python-side model scripting and simulation pipelines to define compartments, covariates, and dosing logic for scenario runs. mrgsolve expects dosing and sampling schedules as configuration plus event streams that compile into a simulation-ready engine, so teams must map their schedule representation into mrgsolve’s event-stream format.

Tools reviewed

Primary sources checked during evaluation.

Referenced in the comparison table and product reviews above.

Logos provided by Logo.dev

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.