Use case library

Find the Oryon page that matches the problem you are actually trying to solve

These pages are built for teams evaluating a concrete workflow problem: security inside Cursor, lower false-positive load, local-first scanning, or shared team memory after the first scan.

Talk to engineering Browse comparisons

Use case pages

Choose the angle that matches your real evaluation

Each page is written for a specific intent, so teams can land directly on the question they are trying to answer instead of starting from generic product messaging.

Cursor Security Extension

For teams using Cursor and compatible VS Code forks that want local analysis, conservative triage, and less workflow drag.

Security inside Cursor, not only later in CI.
Local-first code and dependency analysis.
Same operational model as the VS Code extension.

View page

Reduce SAST False Positives

For teams whose main AppSec problem is not finding scanners, but trusting the output enough to act on it.

Heuristic prefilter before AI review.
Two-pass consensus before dropping a finding.
Shared suppressions tied to the repository fingerprint.

View page

Local-First Code Security

For engineering teams that need early security feedback without turning the cloud into the scanner or uploading the entire codebase by default.

Local scans in the editor for speed and privacy.
Minimal sync only when team memory matters.
Clear boundary between analysis and shared reporting.

View page

Shared Security Memory

For teams that need scan history, shared suppressions, and project context to survive beyond a single developer session.

Repo-linked state across scans.
Shared false-positive handling.
Dashboard memory without moving the scanner to the cloud.

View page

Where to start

Start with the page that reflects your blocker

Adoption inside the editor

If the question is whether security can live inside Cursor or VS Code-based editors without slowing developers down, start with the editor-specific pages first.

Signal quality and noise

If the scanner already exists but teams do not trust the findings, start with the false-positive page. That is usually the fastest path to a serious evaluation.

Privacy and operating model

If the debate is about where the analysis should run and what should be synced to the dashboard, start with local-first code security and shared security memory.

Navigation

When to read use cases vs comparison pages

Start with use cases if

You know the pain point but not yet the shortlist.
You want to understand Oryon through workflow, not through a feature matrix.
You need to align engineering, AppSec, and leadership around one problem statement.

Jump to comparisons if

The shortlist already includes a known vendor.
You need a head-to-head view for a buying decision.
Your team is comparing operating models across tools, not only internal blockers.

Choose the angle that matches your real evaluation

Cursor Security Extension

Reduce SAST False Positives

Local-First Code Security

Shared Security Memory

Start with the page that reflects your blocker

Adoption inside the editor

Signal quality and noise

Privacy and operating model

When to read use cases vs comparison pages

Start with use cases if

Jump to comparisons if

Preferences