Core workflows in Oplane, from your first repository to a committed fix (2 minutes).
What the video shows
What the video shows
The video follows six workflows on an example repository,
acme/docfolioworks. It has a voiceover.- Onboard a repository. Sam creates a workspace called DocFolioWorks for the repository. Oplane reads the code and suggests three threat models. Sam picks two, and Oplane builds each one with the security requirements the code has to meet.
- Review a pull request. Jordan opens pull request #5, “Verify SSO assertion signatures”. Oplane reviews it and its comment flags two requirements that need attention, so he clicks Fix with Oplane.
- Apply suggested fixes. Each suggested fix shows the reason behind it and the change to the code. Jordan clicks Implement all (2 fixes) and Oplane commits both fixes to the branch.
- Fix with your AI assistant. In an AI coding assistant connected to Oplane over MCP (Model Context Protocol), Jordan asks about the most critical unresolved tenant isolation issues and gets the open findings from the threat model. He asks the assistant to fix one, and it follows Oplane’s implementation advice.
- Track your security posture. Jordan asks the assistant to break down open requirements by severity. The same numbers are on the Analytics dashboard, where you can follow them over time.
- Produce the reports you need. A new chat asks for a security report. The assistant pulls the data from Oplane and writes a report that shows open critical and high requirements by risk category and what to fix first.
What Oplane does
Oplane analyses how your systems interact and where data flows, identifying potential security threats at the architectural level. Unlike scanners that look for code-level vulnerabilities, Oplane focuses on design-level risks such as broken access control, insecure data flows, or a missing authentication boundary. Every finding includes a specific security requirement and implementation guidance tailored to your codebase.
How it fits your workflow
While you code
Connect Oplane to your AI assistant via MCP. Describe what you’re building and get security requirements in real time, before you even open a PR.
MCP setup
Connect Oplane to your AI assistant and threat model while you work.
On every PR & MR
Connect your GitHub or GitLab repositories. Oplane reviews every pull request and posts a single summary comment listing the security requirements it found.
How reviews work
What triggers a review and what it produces.
Review pull and merge requests
Set up reviews on GitHub pull requests and GitLab merge requests.
Organisation security posture
Beyond individual requirements, Oplane gives you a bird’s-eye view of your organisation’s security posture. The analytics dashboard shows how quickly requirements get addressed across your repositories and what share of them are implemented versus still outstanding. It also tracks which teams are actively using Oplane and how that engagement trends over time, and it breaks down where your threat models come from (automated PR reviews versus manual or MCP work) and how much of your scope they cover. Filter by time period, workspace, or team to drill into specific areas. Export data for compliance reporting or security audits.Analytics dashboard
View your organisation’s security posture and adoption metrics.
Get started
Ready to try it? The Quick Start guide walks you through both paths in under 5 minutes.Go to quick start
Get security threat modeling running in your workflow in under 5 minutes.