| Free tier | Personal Learning Edition, never expires | Student and demo edition, never expires | Bizagi Modeler, never expires | FlexSim Express, never expires | None published | Personal License, never expires | None published | None published | None published |
|---|
| Shared libraries and approvals | A cloud platform carrying model versions, cloud run experiments, shared storage and a documented interface for automation, offered as a public tier and as a private deployment. Separately, the desktop product documents version control through a standard source control system and a file format designed to be split across a team. | None documented. There is no cloud tier, no browser version and no published model library or approval workflow. The published system requirements describe a desktop installation only. | Shared modeling with collaboration around a documented process, feeding a low code automation platform where a modeled process can be executed rather than only analyzed. Collaboration belongs to the paid Enterprise plan; the free plan is for one person working locally. | None documented as a separate tier. The published material describes a desktop application, with no browser version, cloud service, shared library or approval workflow. | The strongest governance position in this assessment, and the reason the product exists. A process repository holds the models centrally, the platform is delivered as a service rather than as a desktop install, and risk and compliance management are documented as part of the product rather than as an add on. Where the desktop simulation products in this comparison govern a library of files, this governs a system of record that other people are expected to read. | Not stated in the published material. Team packages are priced for four and ten users, but no shared model library or approval workflow is described on the publisher's public pages. | Not established from published material. A cloud offering, ProModel.ai, is described as maintaining a digital twin from live operational data through an API, which implies a hosted component. Nothing published describes a model library, an approval workflow or a permissions scheme. | A Portal Edition, documented in the publisher's release notes, takes experiments uploaded from the desktop product and shows them in a browser with dashboards. It publishes results rather than models: it is a way to distribute an answer, not a way to govern how models are built. | A browser version sharing one interface with the desktop product, which lets a model be opened by somebody who has not installed anything. No separate approval or model governance layer is documented. |
|---|