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.

Bitbucket & Azure Repos

Connect Bitbucket Cloud and Azure Repos for automated pull request reviews.

Bitbucket Cloud

Create an app password: Personal settings → App passwords with repositories read/write and pull requests read/write.
In ScanDrix: Settings → Integrations → Bitbucket and paste the workspace + app password.
Register the webhook (see Webhook Setup) for pullrequest:created and pullrequest:updated.

Reviews post as pull request comments with the ScanDrix merge check attached.

Azure Repos

Create a Personal Access Token (PAT) with Code (read & write) and Pull Request Threads (read & write) scopes.
In ScanDrix: Settings → Integrations → Azure Repos — enter organization, project, and the PAT.
Register the service hook for Pull request created and Pull request updated (Azure DevOps → Service hooks → Webhooks), pointing at the ScanDrix webhook URL with the provided secret.

Azure service hooks deliver JSON payloads with a custom X-VSS-Auth header; ScanDrix validates the shared secret, so treat it like any webhook credential and rotate it from the dashboard if leaked.

Forgejo

Forgejo uses a personal or project access token plus a push/MR webhook. Add it under Settings → Integrations → Forgejo with instance URL, token, and webhook secret.

Common behavior across providers

Review posting — inline comments, severity labels, and a summary; identical rule engine and scandrix.yml support everywhere.
Blocking — provider-native merge checks/required reviewers are updated from ScanDrix findings.
Scopes are minimal — each integration grants comment/read permissions only; code write access is never requested.

Troubleshooting

PreviousGitLab CI/CD NextJira & Linear Integration