> For the complete documentation index, see [llms.txt](https://docs.sonarsource.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sonarsource.com/get-to-know-sonar/sonarqube-products.md).

# SonarQube products

The products that extend the SonarQube platform across the agentic, CI verification, and code maintenance loops, and where to find their documentation.

The SonarQube platform's capabilities, integrations, and specialized products help you improve agent effectiveness, reduce avoidable defects and rework, strengthen security, lower technical debt, and provide evidence for governance and compliance as your agentic software factory scales.

Availability varies by product, plan, edition, and version. Check each product's documentation for details.

## Sonar Vortex

Sonar Vortex is Sonar's agent effectiveness solution. It gives AI coding agents the project-specific context and constraints they need before they write code, then verifies each change in real time against the same SonarQube quality and security standards used in your CI/CD pipeline. Agents use this feedback to fix issues before they open a pull request, which helps reduce rework and manual verification.

Sonar Vortex complements your quality gates and code review. It does not replace them.

* Semantic code navigation from a live code graph built on Sonar analysis
* Coding guidelines chosen for each task from your SonarQube rules and your project's issue history
* Architecture context, including the constraints your teams defined

See [What is Sonar Vortex?](https://docs.sonarsource.com/agent-centric-development-cycle/inside-your-agent-the-agentic-loop/sonar-vortex.md)

## SonarQube MCP Server

The SonarQube MCP Server is the integration layer that connects AI coding agents to SonarQube code quality and security data through the Model Context Protocol (MCP). MCP-compatible agents and tools can call it to analyze code, retrieve issues, check quality gates, review security hotspots, and inspect coverage without leaving the coding environment. SonarQube remains the source of analysis and standards.

See the [SonarQube MCP Server](https://docs.sonarsource.com/sonarqube-mcp-server/) documentation.

## SonarQube CLI

The SonarQube CLI brings SonarQube code quality and security verification into the terminal, pipelines, and AI coding tools like Claude Code.

* Secrets scanning as a pre-commit hook, so leaked credentials are blocked before they're committed
* On-demand code quality and security analysis for supported languages, and secrets detection on any file
* Issue queries and triage from the command line, with output an LLM can read

See the [SonarQube CLI](https://docs.sonarsource.com/sonarqube-cli/) documentation.

## SonarQube Advanced Security

SonarQube Advanced Security extends SonarQube security verification to third-party and open source dependencies. Core SonarQube security covers your first-party code. SonarQube Advanced Security adds:

* Software composition analysis (SCA): vulnerability detection, malicious package detection, license policy management, and software bill of materials (SBOM) export
* Advanced SAST: dependency-aware taint analysis that traces data flows into open source libraries

Risky dependencies can fail the quality gate before they merge, whoever or whatever added them. This helps you identify and manage supply chain risk.

See SonarQube Advanced Security for [SonarQube Cloud](https://docs.sonarsource.com/sonarqube-cloud/advanced-security.md) or [SonarQube Server](https://docs.sonarsource.com/sonarqube-server/advanced-security.md).

## Gitar

Gitar is Sonar's AI code verification agent for pull requests and CI workflows. It reviews code changes with awareness of repository context, team conventions, and the intent behind a change, diagnoses CI failures, and generates fixes. Automated actions, such as committing fixes, are configurable and stay under your team's review controls.

Gitar works alongside SonarQube. SonarQube sets the standard; Gitar enforces it at merge speed.

See the [Gitar documentation](https://docs.gitar.ai).

## SonarQube Hunter Agent

SonarQube Hunter Agent is an AI-powered security agent that hunts complex, intent-based vulnerabilities in your source code: broken access control and insecure direct object references (IDOR), business logic flaws, and authentication and session gaps. In these flaws, the code is valid but the intent is not, so a pattern-based scanner sees nothing wrong.

SonarQube Hunter Agent works through playbooks, structured multi-step sequences that investigate candidate issues and rule out false positives the way a security researcher audits code. Confirmed findings become regular SonarQube issues, each with a severity, an explanation, and the exact location. It complements SonarQube deterministic analysis. To fix the issues it finds, use SonarQube Remediation Agent.

See [SonarQube Hunter Agent](https://docs.sonarsource.com/agent-centric-development-cycle/in-your-long-living-branches-the-code-maintenance-loop/hunter-agent.md).

## SonarQube Remediation Agent

SonarQube Remediation Agent fixes issues that SonarQube and SonarQube Hunter Agent have already found, then verifies each fix before it reaches you. Every fix goes through closed-loop verification: SonarQube Remediation Agent generates a patch, applies it in a sandbox, and reruns Sonar analysis. It discards any fix that does not resolve the issue or that introduces a new one.

SonarQube Remediation Agent opens pull requests that contain only verified fixes. Your developers review each pull request and decide whether to merge.

* Clear technical debt backlogs on a schedule, or on demand for issues you assign
* Resolve quality gate failures in pull requests

See [SonarQube Remediation Agent](https://docs.sonarsource.com/agent-centric-development-cycle/in-your-long-living-branches-the-code-maintenance-loop/remediation-agent.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sonarsource.com/get-to-know-sonar/sonarqube-products.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
