pytm vs ThreatOpus
pytm
github.comThreatOpus
threatopus.comSide by side
| Figure | pytm | ThreatOpus |
|---|---|---|
| Price from | Free | £129.99/mo |
| Free plan | Yes | — |
| Free trial | — | Yes |
| Open source | — | — |
| Web | — | Yes |
| Windows | Yes | — |
| macOS | Yes | — |
| Linux | Yes | — |
| API | — | Yes |
| Plans published | 1 | 4 |
| Spec score · Threat Modeling Software | 7.6 (#10) | 7.5 (#17) |
| Intended users | The project describes its goal as shifting threat modeling earlier and making it more automated and developer-centric. | ThreatOpus describes its intended users as security teams, security champions, and platform engineers seeking governed threat models and clear merge decisions. |
Plans
ThreatOpus
- Starter£129.99 a month
- Pro£299.99 a month
- EnterprisePriced on request
- FreePrice not published
In their own words
pytm
pytm is a free, open-source Python framework for creating threat models from architectural descriptions. A model is defined in Python with elements such as servers, data stores, actors, processes, data flows, and trust boundaries. From it, pytm can generate data flow diagrams, sequence diagrams, and relevant threats. Templates can produce reports with diagrams and findings, and a RevealMD template can create slides for browser presentation. Data flow diagrams use Graphviz DOT, while sequence diagrams use PlantUML. Models can be imported from JSON with pytm's Python load function. Users can supply a custom threats file and change finding attributes such as CVSS score, response text, and severity. Requirements include Python 3.11 or later, Graphviz, Java OpenJDK 10 or 11, and plantuml.jar; Linux and macOS are listed, while Windows use is documented through Devbox in WSL. The project also documents container and Devbox dependency workflows. The README warns that strings in threats.json are evaluated with eval(), so the file's permissions need protection against unauthorized changes.
ThreatOpus
ThreatOpus combines threat modelling with security checks for pull requests, returning PASS, WARN or FAIL decisions in a CI pipeline. Teams can describe a system, import its design from OpenAPI or Terraform, or link a GitHub repository to generate STRIDE threats and track mitigations. STRIDE is available on every plan, while Pro adds nine further threat modelling frameworks. Merge Guard evaluates pull requests against policy bundles and posts decisions with reasons to CI checks. Listed integrations include GitHub, GitLab, Bitbucket, Jenkins, CircleCI, Azure DevOps, TeamCity, AWS CodeBuild and Travis CI. Outcome notifications can go to Slack or Microsoft Teams, and scoped API keys support custom pipeline steps or internal orchestration. Project settings let users control retention of raw architecture input and structured threat output. Signed-in users can export their data as JSON and delete content they created. ThreatOpus offers a free plan and free trial; paid plans start at £129.99/mo. Generated threats and mitigations support security work but do not replace professional assessment, penetration testing or formal risk acceptance.