Question 1

What is VERDiiiCT?

Accepted Answer

VERDiiiCT is a SaaS platform that automates pull request code reviews using AI. It integrates with GitHub and Azure DevOps, analyzes your code changes when a PR is opened, and delivers a verdict (Approved, Needs Work, or Rejected) with line-level comments — all within minutes.

Question 2

How does the AI review my code?

Accepted Answer

When a pull request is opened, a webhook sends the PR diff to our review engine. The AI model (Claude or GPT) analyzes the changes for bugs, security issues, style problems, and best practice violations. It then posts line-level comments directly on the PR and assigns an overall verdict.

Question 3

Which AI models are supported?

Accepted Answer

VERDiiiCT supports Anthropic Claude and OpenAI GPT models. You can select your preferred model from your organization's settings in the dashboard. Both models provide high-quality, actionable code review feedback.

Question 4

Is my code secure? Does the AI store my code?

Accepted Answer

Security is a top priority. Your code diffs are sent to the AI provider for analysis over encrypted connections and are not stored permanently. Review comments and metadata are stored for your review history, but raw source code is not retained beyond the review session. All data is isolated per tenant.

Question 5

Which source control providers are supported?

Accepted Answer

VERDiiiCT currently supports GitHub and Azure DevOps. You can connect multiple providers within the same organization, and each repository is managed independently.

Question 6

How do I connect my repository?

Accepted Answer

From the dashboard, navigate to SCM Connections and add a new connection using a personal access token (PAT) for your GitHub or Azure DevOps account. Once connected, your repositories will appear and you can enable webhooks for automated reviews.

Question 7

What is a "verdict" and what do the different verdicts mean?

Accepted Answer

A verdict is the AI's overall assessment of your pull request. "Approved" means the code meets quality standards. "Needs Work" means there are issues that should be addressed before merging. "Rejected" means significant problems were found that require major changes.

Question 8

Can I configure how strict the reviews are?

Accepted Answer

Yes. VERDiiiCT offers three tolerance levels: Low (flags everything including minor suggestions), Medium (balanced feedback for most teams), and High (only flags critical bugs and security issues). You can change this at any time in your organization settings.

Question 9

How long does a review take?

Accepted Answer

Most reviews complete in under 2 minutes. The exact duration depends on the size and complexity of the pull request, but the process is fully automated and starts within seconds of the PR being opened.

Question 10

Is VERDiiiCT really free? What's the catch?

Accepted Answer

VERDiiiCT is completely free — no hidden fees, no credit card required, no usage caps on repositories or team members. We believe every engineering team should have access to AI-powered code reviews regardless of budget.

Question 11

Can I use this for private repositories?

Accepted Answer

Yes. VERDiiiCT works with both public and private repositories. Your code is accessed only through authenticated PAT connections, and all data is isolated per organization.

Question 12

How many team members can I invite?

Accepted Answer

There is no limit on team members. Invite as many people as you need — your entire engineering team can use VERDiiiCT at no cost.

Question 13

What roles are available (Owner, Admin, Member)?

Accepted Answer

Organizations have three roles. Owners have full control including billing and deletion. Admins can manage repositories, connections, and team members. Members can view reviews and analytics but cannot change organization settings.

Question 14

Can I use both GitHub and Azure DevOps in the same organization?

Accepted Answer

Yes. You can connect multiple SCM providers within a single organization. Each connection is managed independently, and reviews work the same way regardless of the provider.

Question 15

How do I set up webhooks?

Accepted Answer

Once you've connected a repository, you can register a webhook from the repository settings in the dashboard. VERDiiiCT will automatically create the webhook on your SCM provider. You can also manually configure webhooks if you prefer.

Question 16

What events trigger a code review?

Accepted Answer

Code reviews are triggered when a pull request is opened or updated (new commits pushed). The webhook listens for these specific events and starts the review pipeline automatically.

Question 17

Can I view past reviews and comments?

Accepted Answer

Yes. The dashboard provides a full review history for each repository. You can see every review's verdict, comments, and metadata. Comments are also posted directly on the PR in your SCM provider.

Question 18

What happens if the AI review fails?

Accepted Answer

If a review fails due to a transient error (e.g., API timeout), VERDiiiCT logs the failure in the dashboard. You can view the error details and manually re-trigger the review. Failed reviews do not block your PR from being merged.

Question 19

Is there an API I can use directly?

Accepted Answer

The VERDiiiCT backend exposes a REST API used by the dashboard application. While we don't currently offer a public API for third-party integrations, this is on our roadmap. Contact us if you have specific integration needs.

Question 20

How do I get support?

Accepted Answer

You can reach us at support@verdiiict.com for any questions or issues. We also have a GitHub repository where you can report bugs and request features. We aim to respond to all inquiries within 24 hours.

Frequently Asked Questions

Still have questions?