# Oplane

> AI-powered threat modeling for development teams. Identify and fix architectural security vulnerabilities automatically.

## Docs

- [Security posture analytics dashboard](https://oplane.io/docs/analytics.md): Track your organisation's security posture with the Analytics dashboard: monitor requirement resolution, team adoption, and remaining coverage gaps.
- [May 22, 2026 — Analytics in MCP](https://oplane.io/docs/changelog/2026-05-22.md): Ask analytical questions about threat models, security requirements, and workspaces directly from your IDE with the new Oplane MCP analyze tool.
- [Connect GitHub](https://oplane.io/docs/connect-github.md): Connect Oplane to your GitHub repositories to enable automated threat modeling on pull requests. The setup takes just a few minutes.
- [Pull & Merge Requests](https://oplane.io/docs/github-prs.md): Automate threat modeling on GitHub pull requests and GitLab merge requests with Oplane, surfacing security feedback in code review before merging.
- [Connect GitLab](https://oplane.io/docs/gitlab-setup.md): Connect Oplane to GitLab projects for automated threat modeling on merge requests. No app install required — just sign in with your GitLab account.
- [Introduction to Oplane threat modeling](https://oplane.io/docs/introduction.md): Oplane is a threat modeling platform that helps development teams identify and address security risks in their architecture — in minutes, not weeks.
- [Linked accounts for sign-in and integrations](https://oplane.io/docs/linked-accounts.md): Link GitHub, GitLab, Atlassian, Miro, and Google accounts to your Oplane user for sign-in, repository access, PR/MR reviews, and workflow actions.
- [Oplane MCP server and Claude Code plugin](https://oplane.io/docs/mcp-agent.md): Use Oplane in your IDE via the Model Context Protocol (MCP) server or Claude Code plugin to get threat modeling and security guidance while you code.
- [Oplane Miro app for threat model diagrams](https://oplane.io/docs/miro-app.md): Install the Oplane Miro app to browse threat models and import them as visual diagrams with components, data flows, and security requirement cards.
- [Quick start guide for Oplane threat modeling](https://oplane.io/docs/quick-start.md): Set up Oplane threat modeling in under 5 minutes: connect your GitHub or GitLab repository, run your first scan, and review security findings on a PR.
- [Roles & Permissions](https://oplane.io/docs/roles.md): Understand Oplane's layered access model: organisation roles (Org Admin, Org Member), workspace membership, and inherited threat model permissions.
- [Oplane vs. AI Security Scanners](https://oplane.io/docs/security-comparison.md): See how Oplane's use-case driven threat modeling compares to Claude Code Security and Codex Security across workflow, compliance, and OWASP coverage.
- [Working with Requirements](https://oplane.io/docs/solvers-guide.md): How to respond to security requirements Oplane raises on your pull requests or merge requests, and how to run threat modeling locally before pushing.
- [Statuses & Severity](https://oplane.io/docs/statuses-severity.md): A quick reference for the statuses, severity levels, and check results you'll encounter in Oplane's PR/MR reviews and threat models.
- [Workspaces for organising threat models](https://oplane.io/docs/workspaces.md): Workspaces organise your threat models by project, team, or repository. Each workspace has its own members, access controls, and threat model history.