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

Kiuwan Code Security by Optimyth Software, S.L. (Kiuwan) holds a panel rating of 2.5/5 from 6 AI judges (category median 3/5), as of 2026-11-19. Provenance: provenance unknown; sovereignty: 1 of 6 dimensions proven.

- Vendor: Optimyth Software, S.L. (Kiuwan) (https://www.kiuwan.com)
- Category: [Code Security & Quality (SAST/SCA)](https://whats-best.ai/software/code-security.md)
- Provenance (editorial classification): provenance unknown
- Canonical page: https://whats-best.ai/software/code-security/kiuwan-code-security
- Alternatives: https://whats-best.ai/software/code-security/kiuwan-code-security/alternatives ([markdown](https://whats-best.ai/software/code-security/kiuwan-code-security/alternatives.md))
- Data as of: 2026-11-21 · evaluated 2026-11-19 · oldest source captured 2026-11-17

**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: Optimyth Software, S.L. (Kiuwan)
- Headquarters: Not stated on the vendor’s pages as of 17 Nov 2026
- Data hosting: Not stated on the vendor’s pages as of 17 Nov 2026
- Free plan: Not stated on the vendor’s pages as of 17 Nov 2026

## The panel's verdict

Kiuwan Code Security (Optimyth Software, S.L.) is a SAST/SCA product strongest at static analysis: code analysis scores a uniform 6, crediting data-flow analysis, more than 4,300 rules mapped to OWASP, CWE/SANS-25 and PCI-DSS, customisable rules and a code-quality module — though the "almost 100% of true positives" OWASP claim is self-reported and the pages give different figures for supported languages (30+ versus 10+). Dependencies and secrets score 4-5: transitive dependency management, licence policy enforcement, NIST NVD scanning and SBOM generation are documented, with no public information on secret detection, SBOM format or reachability. Weakest are sovereignty — the only captured address is Houston, Texas, cloud and local analysis report to a unified cloud dashboard, and we found no public information on hosting locations, subprocessors or a data processing agreement — and trust and compliance, with no public information on retention, encryption or certifications. Developer workflow and integration and admin range 4-6: the lead developer scored 4 on each, citing dashboard-centric findings and missing gate, triage and integration detail. Pricing states no figures; entry is a free trial or live demo.

**Speaks for it:**
- Static analysis with data-flow analysis and more than 4,300 rules mapped to OWASP Top 10, CWE/SANS-25 and PCI-DSS, plus customisable rules and a code-quality module
- Local pre-commit analysis, real-time IDE feedback with fix guidance, pull-request and merge-pipeline integration, and CI/CD automation for Git, Jenkins and Azure DevOps are documented
- Composition analysis documents transitive dependency management, licence identification with policy enforcement, obsolescence notifications, continuous scanning against the NIST National Vulnerability Database and SBOM generation
- Audit-ready reports are generated continuously and mapped to ISO 25000, OWASP, CWE, PCI DSS and HIPAA
- SARIF 2.1 export through a REST API and a Governance module with portfolio analytics, trends and grouping by business value, provider and technology

**Held against it:**
- Sovereignty scored 1-2: the only captured address is in Houston, Texas, cloud and local analysis report to a unified cloud dashboard, and we found no public information on hosting locations, subprocessors or a data processing agreement
- We found no public information on code retention, encryption, ISO 27001 or SOC 2 certifications, an SLA, a status page, or whether customer code trains the Sembi IQ AI engine
- We found no public information on secret detection in code or git history, the SBOM export format, reachability analysis, malicious-package detection or upgrade pull requests
- We found no public information on single sign-on, SCIM provisioning, roles and permissions, audit logs, Jira integration or webhooks, and GitHub and GitLab appear only as platforms consuming SARIF output
- The captured pages give different figures for supported languages (30+ versus 10+), and the "almost 100% of true positives" OWASP benchmark claim is self-reported with no stated methodology

**Best for:**
- You need a SAST core for a polyglot estate, with data-flow analysis and rules mapped to OWASP, CWE and PCI-DSS for audit evidence
- Your developers work in the IDE and at pre-commit, with CI/CD on Git, Jenkins or Azure DevOps and quality gates driven by SARIF 2.1
- You need open-source inventory, transitive dependency management, licence policy enforcement and SBOM generation against the NIST National Vulnerability Database
- You manage a portfolio of applications and want governance-level analytics, trends and grouping by business value, provider and technology

**Avoid if:**
- You must keep source code and findings entirely inside your own network — the captured pages state that cloud and local analysis report to a unified cloud dashboard, and we found no public information on hosting locations, subprocessors or a data processing agreement
- You need secret detection, reachability analysis or malicious-package detection — the documented dependency features are open-source inventory, transitive dependencies, licences, obsolescence notifications and NIST NVD scanning, and we found no public information on the rest
- Your developers need findings surfaced as merge-request comments under strict new-code gates — the documented workflow is IDE feedback, pre-commit analysis and a dashboard with remediation tips, and we found no public information on comment decoration or a new-code baseline

## 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 | 3/5 | 3/5 |
| Dependencies (SCA), licences & secrets | 2/5 | 2/5 | 2.5/5 | 2/5 | 2.5/5 | 2.5/5 |
| Developer workflow, quality gates & fixes | 2/5 | 3/5 | 2.5/5 | 3/5 | 3/5 | 3/5 |
| Platforms, deployment & administration | 2/5 | 2.5/5 | 2.5/5 | 2.5/5 | 2.5/5 | 3/5 |
| Source-code handling, security & compliance | 2/5 | 2/5 | 2/5 | 1.5/5 | 2/5 | 2/5 |
| European sovereignty | 1/5 | 1/5 | 1/5 | 1/5 | 1/5 | 0.5/5 |
| Pricing transparency | n/r | n/r | n/r | n/r | n/r | n/r |
| **Weighted verdict** | **2/5** | **2.5/5** | **2.5/5** | **2/5** | **2/5** | **2/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: 1 of 6 dimensions proven.

| Dimension | Finding | Points | Source |
|---|---|---|---|
| Legal entity | Not determined | — | — |
| Hosting location | Not determined | — | — |
| Hosting options | Self-hostable | 1/1 | [S5] |
| 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**
- Alignment standards: OWASP · CWE · CVE · CPE · NIST [S1]
- Sast standards: CWE · OWASP · PCI · CERT · SANS [S1]
- Standards supported: ISO 25000 · OWASP · CWE · PCI DSS · HIPAA · yes [S2]

**Hosting**
- Deployment options: yes [S1]

**Integrations**
- Sarif accepted by: GitHub Advanced Security, Azure DevOps, GitLab, Jenkins, security orchestration platforms [S6]
- Sarif API: yes [S6]
- Sarif compatible tools: GitHub Advanced Security, Azure DevOps, and 100+ tools [S6]

**Legal**
- Address: 2950 N Loop Freeway W, Ste 700, 77092 Houston, US [S1]
- Address: 2950 N Loop Freeway W, Ste 700, 77092 Houston, US [S2]
- Address: 2950 N Loop Freeway W, Ste 700, 77092 Houston, US [S3]
- Address: 2950 N Loop Freeway W, Ste 700, 77092 Houston, US [S4]
- Address: 2950 N Loop Freeway W, Ste 700, 77092 Houston, US [S5]
- Address: 2950 N Loop Freeway W, Ste 700, 77092 Houston, US [S6]
- Address: 2950 N Loop Freeway W, Ste 700, 77092 Houston, US [S7]

**Pricing**
- Free trial: yes [S7]
- Pricing section: Pricing section present; no specific prices stated [S3]

**Product**
- Activity tracking: dev team and vendor activity tracking [S5]
- Add ons: yes [S1]
- AI engine: Sembi IQ · AI engine [S1]
- Cicd and local: yes [S3]
- Code quality module: Code Quality module for quality metrics and remediation plans [S4]
- Continuous monitoring: yes [S4]
- Data flow analysis: yes [S2]
- Decision quadrants: decision quadrants for risky apps [S5]
- Demo: yes [S1]
- Dependency management: yes [S4]
- Deployment environments: cloud native · local [S4]
- Deployment options: yes [S3]
- Deployment options: yes [S5]
- Free trial: yes [S1]
- Free trial: yes [S3]
- Governance module: Governance: Portfolio Intelligence Centre for portfolio analytics [S4]
- Ide integration: yes [S1]
- Ide integration: yes [S7]
- Ide realtime: yes [S3]
- Insights identify vulnerabilities: known vulnerability and license issue identification [S5]
- Insights inventory: yes [S7]
- Insights nist: NIST [S7]
- Insights sbom features: component inventories · vulnerability and licensing issues · component names, versions, dependencies · risk mitigation and compliance [S5]
- Language support: 10+ · Git · Jenkins · Microsoft Azure DevOps [S4]
- Languages: 30 [S1]
- License compliance: yes [S7]
- License identification: yes [S4]
- Live demo: yes [S3]
- Obsolescence alerts: yes [S7]
- Owasp benchmark: almost 100% [S7]
- Owasp scan: Scans applications for OWASP Top 10 critical application security risks [S7]
- Platforms: Web-based [S2]
- Platforms: Web-based [S3]
- Platforms: Web-based [S4]
- Platforms: Web-based · On-premise [S5]
- Platforms: Web-based · On-premise [S6]
- Platforms: Web-based [S7]
- Portfolio grouping: Business Value · Provider · Technology · Quality Model [S5]
- Predictive analytics: portfolio evolution forecasting [S5]
- Premerge qc: yes [S2]
- Real time alerts: yes [S4]
- Realtime alerts: yes [S2]
- Remediation and compliance: yes [S3]
- Reporting severity: yes [S2]
- Reports: yes [S1]
- Rules count: 4300 · 30+ [S7]
- Sarif code analysis: Kiuwan Code Analysis (Quality) SARIF exports contain vulnerability findings plus quality and defect-related data [S6]
- Sarif code security: Kiuwan Code Security SARIF exports contain complete vulnerability data and related security details [S6]
- Sarif export: yes [S6]
- Sarif sbom complementary: SBOM and SARIF are complementary; both formats can be exported from Kiuwan [S6]
- Sarif use cases: CI/CD integration, security dashboards, compliance reporting, developer tools (VS Code, IntelliJ) [S6]
- Sarif version: 2.1 [S6]
- Sast: yes [S1]
- Sast foundation: Kiuwan offers static application security testing (SAST) analyzing code for vulnerabilities, coding standards violations and quality concerns [S2]
- Sast standards: CWE · OWASP · PCI · CERT · SANS [S4]
- Sast tool: SAST tool that finds and prioritizes vulnerabilities with remediation guidance [S3]
- Sbom generation: yes [S5]
- Sbom generation: yes [S4]
- Sca: yes [S1]
- Sca: yes [S7]
- Sca capabilities: yes [S1]
- Sca scanning modes: on-demand · continuous [S4]
- Sdlc tracking: yes [S4]
- Sembi iq: Sembi IQ is described as an AI engine powering intelligent quality [S7]
- Trial available: yes [S6]
- Vulnerability source: Scans against NIST NVD to detect known CVEs [S4]
- Zap testing: Page describes OWASP ZAP penetration testing and its limitations [S7]

## Questions

### Is Kiuwan Code Security European?

Not determined: the vendor’s pages as captured do not say where Kiuwan Code Security is based.

### Where does Kiuwan Code Security store data?

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

### Does Kiuwan Code Security have a free plan?

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

### What are the best alternatives to Kiuwan Code Security?

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: [Kiuwan Code Security alternatives](https://whats-best.ai/software/code-security/kiuwan-code-security/alternatives).

## Sources

- [S1] Vendor page: https://www.kiuwan.com (checked 2026-11-17)
- [S2] Code analysis (SAST & code quality) — found from sitemap: https://www.kiuwan.com/static-code-analysis/ (checked 2026-11-17)
- [S3] Code analysis (SAST & code quality) — found from sitemap: https://www.kiuwan.com/code-security-sast/ (checked 2026-11-17)
- [S4] Dependencies (SCA), licences & secrets — found from sitemap: https://www.kiuwan.com/insights-open-source/ (checked 2026-11-17)
- [S5] Dependencies (SCA), licences & secrets — found from sitemap: https://www.kiuwan.com/secure-sbom-compliance/ (checked 2026-11-17)
- [S6] Platforms, deployment & administration — found from sitemap: https://www.kiuwan.com/sarif/ (checked 2026-11-17)
- [S7] Source-code handling, security & compliance — found from sitemap: https://www.kiuwan.com/owasp-accredited/ (checked 2026-11-17)

---

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

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