# Oplane > AI-powered threat modeling for development teams. Identify and fix architectural security vulnerabilities automatically. - [Introduction to Oplane threat modeling](https://www.oplane.com/docs/start/what-is-oplane.md): Oplane is a threat modeling platform that helps development teams identify and address security risks in their architecture within minutes rather than weeks. - [Quick start guide for Oplane threat modeling](https://www.oplane.com/docs/start/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. - [How Oplane reviews pull and merge requests](https://www.oplane.com/docs/how-it-works/reviews.md): What triggers an Oplane review, what Oplane reads, and what it produces for each GitHub pull request or GitLab merge request. - [Workspaces for organising threat models](https://www.oplane.com/docs/how-it-works/workspaces.md): What a workspace is in Oplane, how repo-connected and standalone workspaces differ, and how namespace claims decide which organisation owns a repository. - [Connect GitHub repositories to Oplane](https://www.oplane.com/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. - [Connect GitLab projects to Oplane](https://www.oplane.com/docs/connect/gitlab.md): Connect Oplane to GitLab projects for automated threat modeling on merge requests. No app install required, just sign in with your GitLab account. - [Connect a self-managed GitLab instance](https://www.oplane.com/docs/connect/gitlab-self-managed.md): Add a self-managed GitLab integration in Oplane organisation settings so your workspaces can connect repositories from a self-hosted GitLab instance. - [Oplane Miro app for threat model diagrams](https://www.oplane.com/docs/connect/miro.md): Install the Oplane Miro app to browse threat models and import them as visual diagrams with components, data flows, and security requirement cards. - [Automated threat modeling on pull and merge requests](https://www.oplane.com/docs/find/pull-and-merge-requests.md): Set up Oplane reviews on GitHub pull requests and GitLab merge requests, and act on the security feedback in code review before merging. - [Oplane MCP server and IDE plugin setup](https://www.oplane.com/docs/find/mcp.md): Connect Oplane to Cursor, Claude Code, GitHub Copilot CLI, opencode, or Codex via MCP for in-editor threat modeling and security guidance. - [Responding to Oplane security requirements in PRs](https://www.oplane.com/docs/find/respond-to-requirements.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. - [Fix security requirements with Oplane](https://www.oplane.com/docs/fix/click-to-fix.md): Review the code fixes Oplane suggests for a pull or merge request and commit them to the branch in one click. - [Block merges on unresolved security requirements](https://www.oplane.com/docs/prove/merge-gating.md): Make the Oplane Security Review check block GitHub pull requests and GitLab merge requests while unresolved requirements sit at or above a severity you choose. - [Security posture analytics dashboard](https://www.oplane.com/docs/prove/analytics.md): Track your organisation's security posture with the Analytics dashboard: monitor requirement resolution, team adoption, and remaining coverage gaps. - [Create and manage workspaces](https://www.oplane.com/docs/administration/workspaces.md): Create Oplane workspaces, find and organise them on the Workspaces page, and track requirement progress inside each one. - [Roles and permissions for Oplane organisations](https://www.oplane.com/docs/administration/roles.md): Understand Oplane's layered access model: organisation roles (Org Admin, Org Member), workspace membership, and inherited threat model permissions. - [Linked accounts for sign-in and integrations](https://www.oplane.com/docs/administration/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. - [Applications for API and MCP access](https://www.oplane.com/docs/administration/applications.md): Create an application in Oplane organisation settings to give CI/CD pipelines, automation, and other tools their own API key with scoped permissions. - [Oplane MCP tool reference](https://www.oplane.com/docs/reference/mcp-tools.md): Every tool the Oplane MCP server exposes to your AI assistant, with what each one does. - [Threat model statuses and severity reference](https://www.oplane.com/docs/reference/statuses-and-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. - [August 21, 2026: Check failure threshold, namespace claims](https://www.oplane.com/docs/changelog/2026-08-21.md): Set a severity threshold to control when the Oplane Security Review check fails, and use namespace claims to manage Git providers across teams. - [May 22, 2026: Analytics in MCP](https://www.oplane.com/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. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.