Skip to main content
Get security threat modeling running in your workflow in under 5 minutes. Choose your path below.

Local with MCP

Run threat models directly in Cursor, GitHub Copilot, or Claude Code while you write code.~2 min setup

Connect GitHub

Automated threat modeling on every pull request with inline review comments.~5 min setup

Connect GitLab

Automated threat modeling on every merge request. No app install needed.~3 min setup

​
How Oplane Works

1

Describe what changed

Oplane reads your code diff or you describe the feature you’re building.
2

Get security requirements

Oplane generates targeted requirements based on your specific changes — not generic checklists.
3

Implement & resolve

Get implementation advice, mark requirements as resolved, or accept risks with justification.
4

Track your security posture

View organisation-wide analytics — resolution rates, requirement completion, and adoption across teams.

​
Two Ways to Use Oplane

​
In your IDE

Connect via MCP and threat model while you code. Works with Cursor, GitHub Copilot, Claude Code, and any MCP-compatible client. No Git provider connection needed.

Set up MCP

Connect Oplane to your IDE for in-editor threat modeling.

​
On PRs & MRs

Automated reviews on every pull request and merge request. Posts inline comments on affected lines. Trigger on-demand with @oplane.

Learn about PR reviews

See how Oplane reviews your pull requests and merge requests.
Use both together for full coverage — catch issues locally while you develop, and let automated reviews ensure nothing slips through in code review.