# Qlty — Code Security & Quality (SAST/SCA)

Qlty by Qlty Software Inc. holds a panel rating of 2.5/5 from 6 AI judges (category median 3/5), as of 2026-11-06. Provenance: Rest of world; sovereignty: 2 of 6 dimensions proven.

- Vendor: Qlty Software Inc. (https://qlty.sh)
- Category: [Code Security & Quality (SAST/SCA)](https://whats-best.ai/software/code-security.md)
- Provenance (editorial classification): Rest of world
- Canonical page: https://whats-best.ai/software/code-security/qlty
- Alternatives: https://whats-best.ai/software/code-security/qlty/alternatives ([markdown](https://whats-best.ai/software/code-security/qlty/alternatives.md))
- Data as of: 2026-11-21 · evaluated 2026-11-06 · oldest source captured 2026-11-06

**AI-generated.** Every score, rationale and verdict here is written by a panel of AI judges from public evidence — an analysis, not a hands-on test. Every fact quotes the vendor page it was read from. No score can be bought. How scores are made: https://whats-best.ai/methodology

## At a glance

- Vendor: Qlty Software Inc.
- Headquarters: Incorporated in the United States [S7]
- Data hosting: Not stated on the vendor’s pages as of 6 Nov 2026
- Free plan: Yes, per the vendor’s own page [S4]

## The panel's verdict

Qlty, a cloud code health platform from Qlty Software Inc., is strongest on pricing transparency at 8-9: Free at $0, Pro at $20 per contributor per month and Enterprise at $30, a rolling 30-day seat rule that counts bots, $0.01 overage per analysis minute, volume discounts and two months free on annual plans. Developer workflow and code analysis follow at 5-6, on fourteen fully supported languages, go/no-go quality gates, self-updating pull-request comments, a new-code baseline and AI suggestions for 90% of issues. Sovereignty is the floor at a flat 2 — New York governing law, US headquarters, AWS hosting with no region stated, and we found no public information on EU hosting, a data processing agreement or a self-hosted edition — with dependencies and secrets close behind at 3-4, where we found no public information on licence detection, SBOM export or reachability analysis. Judges split by a single point on several criteria — most consequentially trust and compliance at 4-5, a concrete security page weighed against retention stated only as long as necessary and no OWASP/CWE mapping — and the flagged splits list came back empty.

**Speaks for it:**
- Pricing transparency scores 8-9: three public tiers — Free at $0, Pro at $20 and Enterprise at $30 per contributor per month — with $0.01-per-analysis-minute overage, published volume discounts and two months free on annual plans.
- Code analysis scores 5-6 on fourteen fully supported languages, a documented cognitive complexity metric and coverage import across 14+ formats.
- Developer workflow scores 5-6: pass-fail statuses and self-updating comments on every pull request, configurable go/no-go quality gates, a new-code baseline and AI suggestions for 90% of issues.
- The security page is concrete: SOC 2 Type II, annual third-party penetration testing, analysis in sandboxed Fargate containers destroyed after each run, and no stored clones of analyzed repositories.
- Secrets scanning through Gitleaks and Trufflehog includes a block mode that stops a merge when a new secret is detected.

**Held against it:**
- Sovereignty scores a flat 2: a US entity under New York law, AWS hosting with no region stated, and we found no public information on EU hosting, a data processing agreement or a self-hosted edition of the cloud product.
- Dependencies and secrets scores 3-4, and we found no public information on licence detection, SBOM export, reachability analysis or malicious-package detection.
- Integration and admin scores a flat 4: the documented code host is GitHub, the REST API is early access without versioning, and we found no public information on GitLab, Bitbucket, Azure DevOps, SAML single sign-on, SCIM or audit logs.
- Security scanning rides bundled engines such as Semgrep and OSV Scanner, with no public information on cross-file taint analysis or rules mapped to OWASP and CWE, and the sub-5% false-positive figure is a stated goal, not a published rate.
- Retention is stated only as keeping personal information as long as necessary with anonymized data kept indefinitely, and we found no public information on whether source code trains the AI models.

**Best for:**
- Your repositories live on GitHub and you want linting, duplication, complexity, coverage and secrets feedback delivered on every pull request from one cloud service.
- You need a publicly computable bill before signing — three priced tiers, a stated rolling 30-day seat definition, and published overage, discount and annual terms.
- You want a zero-cost start: the Free plan carries 1,000 analysis minutes and 100 AI autofixes per month with unlimited private and public contributors.

**Avoid if:**
- Your contracts require EU data residency or self-hosting — ask the vendor: the public pages we read do not show it
- You must produce SBOMs or licence policies for a supply-chain review — the bench's dependencies and secrets scoring of 3-4 comes from exactly these findings.
- Your teams work in GitLab, Bitbucket or Azure DevOps — the documented code host is GitHub alone, connected through a GitHub App, with permissions mirroring GitHub repository roles.
- Your audit needs findings mapped to OWASP or CWE — we found no public information on any such rule mapping, and SAST arrives through a bundled Semgrep plugin.

## Scores by judge and criterion

Scores out of 5, each judge scoring independently against the published rubric (v1). "n/r" = not rated: the vendor publishes no price, or the judge found no public information on that criterion.

| Criterion | The Lead Developer | The Application Security Engineer | The Engineering Manager | The Platform Engineer | The Product Security Officer | The Skeptic |
| --- | --- | --- | --- | --- | --- | --- |
| Code analysis (SAST & code quality) | 3/5 | 3/5 | 3/5 | 3/5 | 2.5/5 | 2.5/5 |
| Dependencies (SCA), licences & secrets | 2/5 | 2/5 | 2/5 | 2/5 | 1.5/5 | 2/5 |
| Developer workflow, quality gates & fixes | 3/5 | 3/5 | 3/5 | 2.5/5 | 2.5/5 | 3/5 |
| Platforms, deployment & administration | 2/5 | 2/5 | 2/5 | 2/5 | 2/5 | 2/5 |
| Source-code handling, security & compliance | 2.5/5 | 2/5 | 2.5/5 | 2/5 | 2.5/5 | 2/5 |
| European sovereignty | 1/5 | 1/5 | 1/5 | 1/5 | 1/5 | 1/5 |
| Pricing transparency | 4.5/5 | 4/5 | 4/5 | 4/5 | 4/5 | 4.5/5 |
| **Weighted verdict** | **3/5** | **2.5/5** | **2.5/5** | **2/5** | **2/5** | **2.5/5** |

### The judges

- **The Lead Developer** (v1.0): Lead developer at a web agency in Cologne with fourteen developers building Laravel, TypeScript and React Native projects for clients on GitHub and GitLab. Wants every merge request checked for bugs, injection flaws and vulnerable packages before review, comments in the merge request rather than a separate dashboard, the same rules in VS Code and PhpStorm, few false positives, and a bill that does not jump each time a freelancer pushes a commit.
- **The Application Security Engineer** (v1.0): Application security engineer at a payments company in Frankfurt with 120 developers, two of them security champions per team, under PCI DSS and DORA. Wants taint analysis that follows user input across files, reachability so the backlog holds only vulnerable code that is actually called, secrets checked for validity across the whole git history, push protection, custom rules for in-house frameworks, and reports an auditor accepts.
- **The Engineering Manager** (v1.0): Head of engineering at a B2B SaaS company in Munich with six teams and a ten-year-old Java and Kotlin codebase. Wants technical debt and code health shown per team and hotspot, a quality gate on new code that every team keeps, trends to show the board that the rewrite budget worked, findings routed to Jira, single sign-on and roles per team, and to know what the AI-written code the teams now merge does to the numbers.
- **The Platform Engineer** (v1.0): Platform engineer at an insurer in Hanover who runs a self-managed GitLab and Jenkins for 300 developers inside the company network; source code may not leave it. Wants a self-hosted edition or a scanner that runs in the pipeline and sends only results, SAML and SCIM from Entra ID, an API to roll scan settings out to 900 repositories, SARIF output, audit logs, and upgrades that do not break the pipelines.
- **The Product Security Officer** (v1.0): Product security officer at a machine builder in Baden-Württemberg whose controllers and service apps fall under the EU Cyber Resilience Act. Needs an SBOM per release in a standard format, every component's vulnerabilities and licences tracked after shipping, evidence of secure development an auditor can file, and to know where the firmware source code is stored, for how long, and whether any AI model is trained on it.
- **The Skeptic** (v1.0): Has seen "zero false positives" bury a team under four thousand findings on day one, a "free for open source" plan that counted every bot as a contributor, and an "AI autofix" that shipped the repository to a model in the US. Asks how contributors are counted, which languages get real data-flow analysis rather than regular expressions, what happens to the code after a scan, whether the findings export when the contract ends — and what the second year costs.

## European sovereignty — proven facts

Built only from facts on the vendor's own pages; a dimension we could not prove is left open, never scored as zero. Headline: 2 of 6 dimensions proven.

| Dimension | Finding | Points | Source |
|---|---|---|---|
| Legal entity | Incorporated in US | 0/2 | [S7] |
| Hosting location | Not determined | — | — |
| Hosting options | Self-hostable | 1/1 | [S1] |
| Open source | Not determined | — | — |
| Data processing agreement | Not determined | — | — |
| Transfer impact assessment | Not determined | — | — |

## Key facts

Each fact is the vendor's own statement, cited to the source page it was read from ([S*n*] → Sources).

**Compliance**
- CCPA no sale: no [S7]
- CCPA notice: yes [S7]
- Corporate security program: yes [S5]
- Cross border safeguards: no · yes [S7]
- Encryption at rest: yes · AWS KMS · yes [S5]
- Encryption in transit: yes · A+ [S5]
- Iac: Terraform · yes [S5]
- Mdm: yes [S5]
- No security guarantee: no [S7]
- PCI: Service Provider Level 1 · Stripe [S5]
- Security policy: commercially reasonable efforts to secure the Cloud Service [S6]
- SOC 2: yes · SOC 2 Type II [S5]
- SOC 2: yes [S4]
- Vanta: Vanta [S5]

**Data**
- Children age: 16 [S7]
- Retention after revoking scr: email address · SCR username · organization name [S7]
- Retention policy: no · yes [S7]
- Source code repository access: GitHub · yes [S7]

**Hosting**
- Aws access: no · yes [S5]
- Docs platform: Mintlify [S5]
- Hq location: United States · yes [S7]
- Provider: AWS [S5]
- Vpc: yes [S5]

**Integrations**
- Analytics: Google Analytics [S7]
- API auth token: bearer token · https://qlty.sh/user/settings/tokens [S3]
- API auth token: bearer_token · https://qlty.sh/user/settings/tokens [S12]
- API base URL: https://api.qlty.sh/ [S12]
- API error format: errors [S12]
- API https required: yes [S12]
- API no versioning: no [S12]
- API pagination: offset-based · 100 · 20 [S12]
- API rate limit: units · fixed window · hour · 5000 [S12]
- API rate limit headers: x-ratelimit-limit · x-ratelimit-remaining · x-ratelimit-used · x-ratelimit-reset [S12]
- API rate limit increase contact: yes [S12]
- API rate limit scope: per-user · per-workspace [S12]
- API rate limit status endpoint: GET /rate_limit · no [S12]
- Component API operations: list · create · update · delete [S3]
- Components response formats: json · ndjson · csv [S3]
- Github app: yes [S10]
- Github status posting: GitHub · yes [S11]
- Rest API: Pro · Enterprise [S4]
- Vcs identity: yes [S6]

**Legal**
- Chosen courts: state or federal courts located in New York [S6]
- Controller individual: Qlty Software Inc. [S7]
- Effective date: 2024-11-08 [S7]
- Entity: Qlty Software Inc. [S1]
- Entity: Qlty Software Inc. [S4]
- Entity name: Qlty Software Inc. [S7]
- Governing law: State of New York [S6]
- Liability cap: fees paid or payable in the 12 month period before the claim [S6]
- Notice address: hello@qlty.sh [S6]
- Postal address: 169 Madison Avenue STE 11723, New York, NY, 10016 USA [S7]
- Processor enterprise: processor · employer [S7]
- Product description: engineering insights and automated code review for enterprise customers and individual consumers [S7]
- Provider: Qlty Software Inc. [S6]
- Terms last updated: 2025-07-07 [S6]

**Pricing**
- Annual discount: yes [S4]
- Automatic billing: yes [S6]
- Bots count: yes [S4]
- Cli free tier: yes · no · yes [S1]
- Contributor definition: 30 [S4]
- Custom terms: Enterprise · 40000 [S4]
- Enterprise inclusions: 5000 · 75000 [S4]
- Enterprise price: Enterprise · 30 [S4]
- Free inclusions: community · 100 · 1000 [S4]
- Free price: Free · 0 [S4]
- Free private contributors: yes [S4]
- Invoiced billing: Enterprise · 10000 [S4]
- Invoiced billing detail: Stripe · 10000 [S4]
- Non renewal notice: before end of monthly period, or 30 days before end of annual period [S6]
- Nonprofit discounts: yes · 10 [S4]
- Opensource free: yes [S4]
- Overage analysis minutes: 0.01 [S6]
- Overage rate: 0.01 [S4]
- Page exists: yes [S1]
- Payment methods: yes [S4]
- Plan scope terms: free tier and Essentials plan · Business Terms [S6]
- Price change notice: 30 [S6]
- Pro inclusions: web-based · 5000 · 20000 [S4]
- Pro price: Pro · 20 [S4]
- Refund policy: no [S4]
- Seat definition: rolling 30-day period · yes [S6]
- Subscription period: monthly · annual [S6]
- Tax: no [S4]
- Volume discounts: 5 · 10 · 300 [S4]

**Product**
- Accelerated analysis: Pro · Enterprise [S4]
- Add project constraint: Add Repository as Project only for repos authorized to the GitHub App [S13]
- Additional languages lint format: GraphQL · HTML · JSON · Prisma · SASS · SCSS · SQL · YAML · CSS · Markdown [S8]
- AI autofix: 90 [S1]
- Analysis isolation: AWS Fargate · yes [S5]
- Analysis minutes definition: up to next whole minute · 2-core Linux runner · 1 [S6]
- Analysis types: Linting · Defects · Formatting · Duplication · Security · Complexity [S1]
- API early access: yes [S12]
- API resource groups: Applications · Builds · Coverage · Issues · Projects · Service · User · Workspaces [S12]
- API rest json: REST · JSON [S12]
- Approvals override: yes [S1]
- Auth: GitHub SSO · no [S5]
- Authorization: yes [S5]
- Automated code review: Automated code review with pass-fail statuses on every pull request [S1]
- Baseline analysis: yes [S1]
- Capabilities: Linting · Auto-formatting · Security scanning · Code coverage · Duplication detection · Complexity · Code smells · Metrics [S2]
- Cicd scanning tool: ActionLint · CI/CD [S14]
- Cli capabilities: yes · Rust · yes [S1]
- Cli custom extensions: yes [S1]
- Cli monorepos: yes [S1]
- Cli performance: 3X faster than running linters directly [S1]
- Cli platforms: Mac · Linux · Windows · no [S1]
- Cloud service description: code quality tool for codebase health and issue detection [S6]
- Code climate migration: uses legacy Code Climate GitHub OAuth App for previously authorized repositories [S13]
- Commit statuses: enforce coverage requirements before merging [S10]
- Complexity code smells: high function complexity · high file complexity [S9]
- Complexity definition: Cognitive complexity metric measuring how difficult code is to read and understand, distinct from cyclomatic complexity (testability) [S9]
- Complexity flow breaks: loops · conditionals · catching/rescuing exceptions · switch or case statements · sequences of logical operators · recursion · jumps to labels [S9]
- Complexity nesting structures: conditionals · loops · try/catch blocks [S9]
- Complexity principles: shorthand collapsing multiple statements · breaks in linear flow · nested flow-breaking structures [S9]
- Complexity providers: Qlty CLI · Qlty Cloud [S9]
- Complexity reference: Metric based on the Cognitive Complexity white paper by G. Ann Campbell of SonarSource [S9]
- Components: Qlty CLI · Qlty Cloud [S2]
- Coverage capability: yes [S6]
- Coverage carry forward: yes [S1]
- Coverage chrome extension: yes [S1]
- Coverage ci integrations: GitHub Action · CircleCI Orb [S1]
- Coverage comment reporting: yes [S1]
- Coverage formats: 14 [S1]
- Coverage gates: yes [S1]
- Coverage server side merging: yes [S1]
- Coverage tags: yes [S1]
- Custom permissions: Enterprise [S4]
- Diff coverage: yes [S1]
- Do not track: no [S7]
- Error monitoring: Sentry [S5]
- False positive target: <5% false positive rate [S15]
- Focus new issues: focuses on newly introduced issues; pre-existing issues browsable [S2]
- Full support languages: C / C++ · C# · Go · Java · JavaScript · Kotlin · PHP · Python · Ruby · Rust · Scala · Swift · TypeScript · VB.NET [S8]
- Git connect: GitHub [S1]
- Github app integration: GitHub integration for Qlty Cloud · GitHub App [S13]
- Github oauth auth: GitHub identity of the user · GitHub OAuth [S13]
- Hotspots: Enterprise [S4]
- Iac languages: Terraform · CloudFormation · Kubernetes · Docker · Shell (Bash) · GitHub Actions workflows [S8]
- Iac scanning tools: Trivy · Checkov · Hadolint · ShellCheck · IaC [S14]
- Ignore issues: project configuration file · Qlty web application · yes [S15]
- License model: Fair Source [S1]
- Limits: unlimited [S4]
- Linter count: 70 [S1]
- List components: Retrieve all Components defined for a Project [S3]
- Maker: from the makers of Code Climate [S2]
- Monorepo support: Pro · Enterprise [S4]
- No ci setup: yes [S1]
- No repo clones stored: no [S5]
- Osv monitor mode: monitor · osv-scanner · vulnerable dependencies [S15]
- Owner path parameter: ownerKeyOrId · Repository owner name (login) or workspace ID · 3 [S3]
- Pen testing: at least annually · yes [S5]
- Planned languages: Elixir · Groovy [S8]
- Plugins documentation: Plugin list, security framework, security scanning implementation, plugin development, and monorepo documentation pages are referenced. [S8]
- Pr analysis scope: static-analysis issues introduced by the PR · PR coverage impact [S11]
- Pr comment custom templates: enterprise · support team · yes [S10]
- Pr comment updates: new coverage upload · new commits · coverage metric changes [S10]
- Pr comments enable steps: Project Settings > Comments, toggle Summary Comments on [S10]
- Pr comments github: yes · automatic code coverage comments on GitHub pull requests [S10]
- Pr coverage components: Components sub-view shows per-component coverage comparing base and head [S11]
- Pr coverage direct changes: Direct changes sub-view shows coverage delta per directly modified file [S11]
- Pr coverage indirect changes: Indirect changes sub-view shows coverage changes in files not touched by the PR [S11]
- Pr coverage tab: Coverage tab shows PR coverage impact relative to base with per-file breakdowns [S11]
- Pr default tab: Issues [S11]
- Pr issues tab: Issues tab shows every issue detected in PR analysis with filtering, sorting, triage actions [S11]
- Pr workflow: automated code review comments on newly introduced issues in PRs within minutes [S2]
- Project definition: GitHub repositories · GitHub repository role [S13]

**Support**
- Account manager: Enterprise [S4]
- Channels detail: Discord · GitHub · email · Slack [S4]
- Pr comment requirements: Qlty GitHub App installed on repo · coverage report uploaded for PR · summary comments enabled in project settings [S10]
- Priority: Enterprise [S4]
- Privacy contact email: hello@qlty.sh [S7]
- Security updates trust center: Trust Center · yes [S5]
- Slack: Enterprise [S4]
- Vulnerability disclosure: security@qlty.sh · yes [S5]

24 more facts on the canonical page: https://whats-best.ai/software/code-security/qlty

## Questions

### Is Qlty European?

No. whats-best.ai classifies Qlty as Rest of world. Its vendor, Qlty Software Inc., is incorporated in the United States, per [the vendor’s page captured 6 Nov 2026](https://whats-best.ai/evidence/20337).

### Where does Qlty store data?

Not stated on the vendor’s pages as of 6 Nov 2026.

### Does Qlty have a free plan?

Yes. Qlty has a free plan, per [the vendor’s page captured 6 Nov 2026](https://whats-best.ai/evidence/20324).

### What are the best alternatives to Qlty?

As of 19 Nov 2026, the panel rates [SonarQube (3.5/5)](https://whats-best.ai/software/code-security/sonarqube), [Aikido Security (3.5/5)](https://whats-best.ai/software/code-security/aikido) and [Endor Labs (3.5/5)](https://whats-best.ai/software/code-security/endor-labs) highest among the other 18 Code Security & Quality (SAST/SCA) products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is [SonarQube](https://whats-best.ai/software/code-security/sonarqube) (EU origin, foreign-owned, Switzerland). Ratings are the AI panel’s opinion, formed from public evidence: [how scores are made](https://whats-best.ai/methodology#ordering). The full list, with European products first: [Qlty alternatives](https://whats-best.ai/software/code-security/qlty/alternatives).

## What this page leaves out

- 4 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material.
- 2 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material.
- 2 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material.
- 2 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material.
- 1 legal fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material.
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement.

## Sources

- [S1] Vendor homepage: https://qlty.sh/ (checked 2026-11-06)
- [S2] Features page: https://docs.qlty.sh/what-is-qlty (checked 2026-11-06)
- [S3] API documentation: https://docs.qlty.sh/api-reference/components/list-components (checked 2026-11-06)
- [S4] Pricing page: https://qlty.sh/pricing (checked 2026-11-06)
- [S5] Security / trust page: https://docs.qlty.sh/cloud/security (checked 2026-11-06)
- [S6] Terms of service: https://qlty.sh/legal/terms-of-use (checked 2026-11-06)
- [S7] Privacy policy: https://qlty.sh/legal/privacy-policy (checked 2026-11-06)
- [S8] Code analysis (SAST & code quality) — found from sitemap: https://docs.qlty.sh/languages (checked 2026-11-06)
- [S9] Code analysis (SAST & code quality) — found from sitemap: https://docs.qlty.sh/complexity (checked 2026-11-06)
- [S10] Developer workflow, quality gates & fixes — found from sitemap: https://docs.qlty.sh/coverage/pull-request-comments (checked 2026-11-06)
- [S11] Developer workflow, quality gates & fixes — found from sitemap: https://docs.qlty.sh/cloud/projects/pull-requests (checked 2026-11-06)
- [S12] Platforms, deployment & administration — found from sitemap: https://docs.qlty.sh/api/introduction (checked 2026-11-06)
- [S13] Platforms, deployment & administration — found from sitemap: https://docs.qlty.sh/cloud/permissions (checked 2026-11-06)
- [S14] Source-code handling, security & compliance — found from sitemap: https://docs.qlty.sh/cloud/security/framework (checked 2026-11-06)
- [S15] Source-code handling, security & compliance — found from sitemap: https://docs.qlty.sh/cloud/security/implementing (checked 2026-11-06)

---

Cite as: whats-best.ai, "Qlty — Code Security & Quality (SAST/SCA)", AI panel analysis, as of 2026-11-21. https://whats-best.ai/software/code-security/qlty

Corrections: https://whats-best.ai/correct/1658?target=page
