What Is ScanDrix And How Does It Work?

ScanDrix is an autonomous AI-powered code review and AST security scanning platform built for modern engineering teams. It integrates into your Git providers (GitHub, GitLab, Bitbucket, Azure Repos) to automatically review pull requests, detect vulnerabilities, suggest code fixes, and enforce custom Drixy rules.

How Does ScanDrix Differ From Traditional Linters Like SonarQube?

Traditional linters analyze files in isolation using rigid regex or pattern rules, resulting in high false-positive rates and zero understanding of code intent. ScanDrix performs deep Abstract Syntax Tree (AST) analysis combined with multi-model AI reasoning, understanding whole-codebase context, taint flows, and architectural boundaries.

What Are Drixy Rules And How Do I Configure Them?

Drixy rules are customizable code review and security policies. You can define rules globally across your organization, per repository, or choose from a library of community best practices. You can also run 'Dry Run' previews to test rule modifications against real historical PRs before enforcing them.

Which Git Providers And CI/CD Tools Does ScanDrix Support?

ScanDrix supports GitHub, GitLab, Bitbucket, Azure Repos, and Forgejo out of the box. It also provides a CLI and team API keys for local developer workflows, pre-commit hooks, and custom CI/CD runners.

Does ScanDrix Train On Our Private Source Code?

No. ScanDrix never uses customer source code to train AI models. All code diffs are processed in ephemeral, isolated environments with strict zero-data-retention guarantees. For enterprise deployments, ScanDrix supports Bring Your Own Key (BYOK) and self-hosted on-premise installations.

How Fast Are ScanDrix Code Reviews On New Pull Requests?

ScanDrix is built for sub-minute reviews: an async worker architecture picks up webhook events without blocking CI pipelines. That is a design goal, not a measured guarantee — live service state is on the status page.

Can ScanDrix Suggest Inline Code Fixes?

Yes. When ScanDrix detects bugs, security vulnerabilities, or rule violations, it generates precise inline diff suggestions directly in the pull request review comments that developers can apply with a single click.

Can We Deploy ScanDrix On-Premise Or In Our Own VPC?

Yes. Enterprise customers can deploy ScanDrix in their own AWS, GCP, or Azure VPC, or in fully air-gapped on-premise environments with support for internal LLM endpoints (vLLM, Ollama) and enterprise SSO.

Business Logic Validation

Connect Jira and Linear to verify that pull requests fulfill issue requirements and acceptance criteria before merge.

Traditional static analysis only looks at syntax and common vulnerabilities. ScanDrix extends review intelligence to business logic verification by linking pull requests directly to project management tickets in Jira or Linear.

How it works

Ticket Extraction: ScanDrix parses the PR branch name, commit titles, or PR description for ticket keys (e.g. PROJ-104 or ENG-421).
Context Ingestion: ScanDrix queries the Jira or Linear API to retrieve the ticket description, acceptance criteria, and technical constraints.
Semantic Verification: The AI reasoning engine compares the code diff against the requirements to verify:
- Are all stated acceptance criteria implemented in the changes?
- Are there unintended side effects or modified endpoints not mentioned in the issue specification?
- Are corresponding automated tests added for each new business condition?
Summary Feedback: ScanDrix posts a Business Requirements Checklist directly inside the PR summary table.

Example PR check

When a PR titled feat: add tiered billing upgrade handler (PAY-842) is opened, ScanDrix renders:

markdown

### 📋 Business Logic Verification (PAY-842)
- [x] **Requirement 1**: Capture Razorpay order ID and payment signature — *Implemented in `verify/route.ts:24`*
- [x] **Requirement 2**: Update PostgreSQL workspace tier atomically — *Verified via `UpgradeWorkspacePlanAtomic`*
- [ ] **Requirement 3**: Send invoice confirmation email to account owner — ⚠️ *Missing from diff; no mailer service invoked*

Setup instructions

Connect your project tracker

Go to Settings → Integrations in the ScanDrix dashboard and authenticate with Jira Cloud or Linear.

Define ticket matching format

Configure regex patterns to detect issue identifiers in branch names:

yaml

# .scandrix.yaml
integrations:
  jira:
    project_keys: ["SEC", "PAY", "CORE"]
    require_acceptance_criteria: true

Configure blocking policy

Optionally configure ScanDrix to flag a warning if a PR modifies core business modules without referencing a valid open ticket.

PreviousDry Run Testing NextCLI & Team Keys