Datadog Code Security

Name: Datadog Code Security
Brand: Datadog
Rating: 4.5 (18 reviews)

Leader

Datadog provides cloud-scale monitoring and security for metrics, traces and logs in one unified platform.

Est 2010|Valuation $91.4B|Raised $795.9M

LinkedIn 546K|Website|Web traffic 4.6M|FTEs 8,100|HQ New York, New York, US

MarketsApplication Security Testing (AST)Cloud-Native Application Protection Platform (CNAPP)Code Security

Published Sep 26, 2026

01Common complaints

- If an organization only needs SAST/SCA scanning and does not intend to adopt the Datadog platform, a dedicated scanner (Semgrep, Snyk, GitHub Advanced Security) may deliver better value. - If predictable, tightly controlled cost is the primary constraint: community feedback highlights pricing unpredictability for the Datadog suite, which may be material for budget-sensitive buyers. - If the procurement requirement is for GA-only features with strict SLAs: preview features increase adoption risk and may not meet strict enterprise availability or support requirements. - If independent, third-party validation of effectiveness is required as a procurement condition: much of the publicly available evidence is vendor-published or platform-level rather than product-specific third-party validation.

Deal disqualifiers

Highly cost-sensitive organizations.
Requirements for on-premises or self-hosted scanning only; Datadog is a SaaS-first vendor.
Requirements for immediate availability of specific Code Security features in a particular Datadog regional site where support may lag.

Current limitations acknowledged or implied

Preview features (for example, Secret Scanning and some advanced capabilities) imply potential limitations in support and availability.
Regional/site support constraints: some documentation indicates the product may not be supported on all Datadog sites, which can be a blocker for data residency or regional operations.

Integration and compatibility constraints

Runtime Code Analysis (IAST) depends on tracer and library version support; buyers must validate language/framework coverage and performance overhead for their stack.

Scale limitations

No explicit published hard limits on the number of repositories, committers, or services were identified. Practically, scaling stresses often include:

triage workflow management (muting/assignment automation),
PR comment noise if rules are not tuned,
CI time and developer experience impacts.

02Why they buy

Differentiators

Integration of runtime telemetry into vulnerability prioritization tied to running services and ownership within the Datadog platform.
Developer workflow integrations spanning IDE, PR comments, CI, and runtime telemetry in a unified product suite.

Claims requiring cautious interpretation

Vendor-reported benchmark outcomes for IAST should be validated for relevance to an organization’s language/framework mix and real-world application topology.
Vendor-described use of machine learning/LLMs to reduce false positives is a plausible technical approach but should be validated with before-and-after metrics during evaluation.

Areas where competitors may have the advantage

Broader recognition and maturity as dedicated AppSec platforms.
More extensive community rule ecosystems and custom policy languages.
Different bundled economics for organizations already licensed for a competitor’s platform.

03Field reports

Important limitation: scarce Code Security-specific third-party reviews

Major review platforms typically assess Datadog at the observability/platform level rather than as a standalone Code Security product. Consequently, third-party, product-specific reviews for Code Security are limited in the sources reviewed here.

This analysis relies more on community discussions (primarily around Datadog pricing and the security suite) and vendor-published narratives for Code Security.

Positive feedback themes (from accessible sources)

1. Runtime context and prioritization: the vendor emphasizes correlating findings with runtime/service impact to help teams focus on findings that are active in production. 2. Developer workflow integration: IDE support and inline PR comments with suggested fixes are positioned as core workflow capabilities. 3. Secret scanning with validation: the vendor describes the ability to validate secrets with external providers to reduce false positives. 4. Use of LLMs to reduce false positives: the vendor has described LLM-based filtering for static analysis false positives; this is a vendor claim that was not independently verified in the sources accessed.

Negative feedback themes (from community/reviews about Datadog broadly)

Because Code Security is priced and sold as part of a broader platform, many objections are suite-level but affect buying decisions for Code Security: - Pricing frustration and unpredictability: community discussions describe Datadog pricing as difficult to forecast, with bills that can rise due to autoscaling and ingestion growth. - Perception of being expensive for smaller organizations: several community comments suggest Datadog may be less suitable for startups or highly cost-sensitive teams. - Mixed impressions of some security modules: some community evaluations described security components as underwhelming in certain proofs-of-concept; these comments are not specific to Code Security and may refer to other security products in the suite.

Why customers choose Datadog (inferred)

Inferred drivers include:

Teams already standardized on Datadog for observability may prefer a single vendor to consolidate runtime telemetry, security findings, ownership, and ticketing.
Organizations with complex microservices and significant operational overhead may accept premium pricing for consolidation and operational efficiencies.

Why some customers leave or avoid Datadog

Commonly stated reasons (largely suite-level):

Difficulty predicting bills and perceived price increases
Cost scaling with infrastructure autoscaling
Preference for lower-cost, specialized scanners if organizations do not require an observability/security consolidation

Vendor-published case-like outcomes (limited independent case studies found)

The accessible sources are primarily vendor blog posts and product narratives that describe workflows and capabilities. Independent, audited customer ROI case studies were not found in the materials reviewed. Examples of vendor claims include end-to-end scanning across IDE/CI/runtime and the ability to create remediation pull requests from findings. These are workflow descriptions supported by product screenshots and narrative rather than by independently validated customer metrics. Secret scanning is described as performing live validation with external providers to focus on active secrets and block commits/merges; supporting external validation data or independent false-positive reduction metrics were not found in the accessed sources.

Methodology gaps to note

Most vendor materials describe product capabilities rather than providing case studies with baseline → intervention → measured outcome.
Where benchmark metrics are published by the vendor, they are vendor-reported and benchmark-based rather than third-party audited in the sources accessed.

04Best fit

Company sizes

Most likely fit:

Mid-market to enterprise organizations where security governance and service sprawl make runtime-informed prioritization valuable.
Stronger fit when the organization already has a significant Datadog deployment.

Industries

SaaS, fintech, large-scale internet services, and regulated industries where consolidation and auditability are priorities.

Roles/personas

Decision makers: Head of AppSec, CISO (AppSec), VP Engineering/Platform, SRE leadership.
End users: developers (IDE/PR feedback), AppSec analysts (triage), SREs (runtime context).

Fit qualification criteria

Existing Datadog APM/service catalog adoption and the ability to correlate runtime telemetry with code findings.
Organizations with a backlog of findings that seek to reduce false positives and improve prioritization.
Willingness to support per-committer and per-host security spend.

05The pitch

What the product does (core value proposition)

Datadog Code Security is a DevSecOps-focused application security product suite that scans first-party code and open-source dependencies across the software development lifecycle (IDE → PR/CI → runtime). It includes: - SAST (Static Code Analysis) for code vulnerabilities and quality issues - SCA (Software Composition Analysis) for vulnerable dependencies (static + runtime context) - IAST (Runtime Code Analysis) for vulnerabilities detected in running services - Secret Scanning (noted as preview in vendor documentation) - IaC Security for Terraform misconfigurations - Supply Chain Security aimed at malicious package prevention Datadog positions Code Security to integrate runtime telemetry into vulnerability prioritization and to provide integrated workflows for triage and remediation within the Datadog platform.

Target market and market positioning

- Primary buyer personas: security engineering/AppSec, platform engineering, DevOps/SRE leadership that already use Datadog. - Positioning: a platform-oriented approach that combines shift-left scanning with shift-right runtime context to reduce noise and prioritize findings that are present in running services. In practice, Datadog Code Security is most relevant for organizations that already operate Datadog APM/infrastructure monitoring (to benefit from runtime context) and that accept per-committer and per-host security licensing.

Get a comprehensive analysis of Datadog Code Security including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →

Published Sep 26, 2026

01Common complaints

If an organization only needs SAST/SCA scanning and does not intend to adopt the Datadog platform, a dedicated scanner (Semgrep, Snyk, GitHub Advanced Security) may deliver better value.
If predictable, tightly controlled cost is the primary constraint: community feedback highlights pricing unpredictability for the Datadog suite, which may be material for budget-sensitive buyers.
If the procurement requirement is for GA-only features with strict SLAs: preview features increase adoption risk and may not meet strict enterprise availability or support requirements.
If independent, third-party validation of effectiveness is required as a procurement condition: much of the publicly available evidence is vendor-published or platform-level rather than product-specific third-party validation.

Deal disqualifiers

Highly cost-sensitive organizations.
Requirements for on-premises or self-hosted scanning only; Datadog is a SaaS-first vendor.
Requirements for immediate availability of specific Code Security features in a particular Datadog regional site where support may lag.

Current limitations acknowledged or implied

Preview features (for example, Secret Scanning and some advanced capabilities) imply potential limitations in support and availability.
Regional/site support constraints: some documentation indicates the product may not be supported on all Datadog sites, which can be a blocker for data residency or regional operations.

Integration and compatibility constraints

Runtime Code Analysis (IAST) depends on tracer and library version support; buyers must validate language/framework coverage and performance overhead for their stack.

Scale limitations

No explicit published hard limits on the number of repositories, committers, or services were identified. Practically, scaling stresses often include:

triage workflow management (muting/assignment automation),
PR comment noise if rules are not tuned,
CI time and developer experience impacts.

02Why they buy

Differentiators

Integration of runtime telemetry into vulnerability prioritization tied to running services and ownership within the Datadog platform.
Developer workflow integrations spanning IDE, PR comments, CI, and runtime telemetry in a unified product suite.

Claims requiring cautious interpretation

Vendor-reported benchmark outcomes for IAST should be validated for relevance to an organization’s language/framework mix and real-world application topology.
Vendor-described use of machine learning/LLMs to reduce false positives is a plausible technical approach but should be validated with before-and-after metrics during evaluation.

Areas where competitors may have the advantage

Broader recognition and maturity as dedicated AppSec platforms.
More extensive community rule ecosystems and custom policy languages.
Different bundled economics for organizations already licensed for a competitor’s platform.

03Field reports

Important limitation: scarce Code Security-specific third-party reviews

This analysis relies more on community discussions (primarily around Datadog pricing and the security suite) and vendor-published narratives for Code Security.

Positive feedback themes (from accessible sources)

Runtime context and prioritization: the vendor emphasizes correlating findings with runtime/service impact to help teams focus on findings that are active in production.
Developer workflow integration: IDE support and inline PR comments with suggested fixes are positioned as core workflow capabilities.
Secret scanning with validation: the vendor describes the ability to validate secrets with external providers to reduce false positives.
Use of LLMs to reduce false positives: the vendor has described LLM-based filtering for static analysis false positives; this is a vendor claim that was not independently verified in the sources accessed.

Negative feedback themes (from community/reviews about Datadog broadly)

Because Code Security is priced and sold as part of a broader platform, many objections are suite-level but affect buying decisions for Code Security:

Pricing frustration and unpredictability: community discussions describe Datadog pricing as difficult to forecast, with bills that can rise due to autoscaling and ingestion growth.
Perception of being expensive for smaller organizations: several community comments suggest Datadog may be less suitable for startups or highly cost-sensitive teams.
Mixed impressions of some security modules: some community evaluations described security components as underwhelming in certain proofs-of-concept; these comments are not specific to Code Security and may refer to other security products in the suite.

Why customers choose Datadog (inferred)

Inferred drivers include:

Teams already standardized on Datadog for observability may prefer a single vendor to consolidate runtime telemetry, security findings, ownership, and ticketing.
Organizations with complex microservices and significant operational overhead may accept premium pricing for consolidation and operational efficiencies.

Why some customers leave or avoid Datadog

Commonly stated reasons (largely suite-level):

Difficulty predicting bills and perceived price increases
Cost scaling with infrastructure autoscaling
Preference for lower-cost, specialized scanners if organizations do not require an observability/security consolidation

Vendor-published case-like outcomes (limited independent case studies found)

Examples of vendor claims include end-to-end scanning across IDE/CI/runtime and the ability to create remediation pull requests from findings. These are workflow descriptions supported by product screenshots and narrative rather than by independently validated customer metrics.

Secret scanning is described as performing live validation with external providers to focus on active secrets and block commits/merges; supporting external validation data or independent false-positive reduction metrics were not found in the accessed sources.

Methodology gaps to note

Most vendor materials describe product capabilities rather than providing case studies with baseline → intervention → measured outcome.
Where benchmark metrics are published by the vendor, they are vendor-reported and benchmark-based rather than third-party audited in the sources accessed.

04Best fit

Company sizes

Most likely fit:

Mid-market to enterprise organizations where security governance and service sprawl make runtime-informed prioritization valuable.
Stronger fit when the organization already has a significant Datadog deployment.

Industries

SaaS, fintech, large-scale internet services, and regulated industries where consolidation and auditability are priorities.

Roles/personas

Decision makers: Head of AppSec, CISO (AppSec), VP Engineering/Platform, SRE leadership.
End users: developers (IDE/PR feedback), AppSec analysts (triage), SREs (runtime context).

Fit qualification criteria

Existing Datadog APM/service catalog adoption and the ability to correlate runtime telemetry with code findings.
Organizations with a backlog of findings that seek to reduce false positives and improve prioritization.
Willingness to support per-committer and per-host security spend.

05The pitch

What the product does (core value proposition)

SAST (Static Code Analysis) for code vulnerabilities and quality issues
SCA (Software Composition Analysis) for vulnerable dependencies (static + runtime context)
IAST (Runtime Code Analysis) for vulnerabilities detected in running services
Secret Scanning (noted as preview in vendor documentation)
IaC Security for Terraform misconfigurations
Supply Chain Security aimed at malicious package prevention

Datadog positions Code Security to integrate runtime telemetry into vulnerability prioritization and to provide integrated workflows for triage and remediation within the Datadog platform.

Target market and market positioning

Primary buyer personas: security engineering/AppSec, platform engineering, DevOps/SRE leadership that already use Datadog.
Positioning: a platform-oriented approach that combines shift-left scanning with shift-right runtime context to reduce noise and prioritize findings that are present in running services.

In practice, Datadog Code Security is most relevant for organizations that already operate Datadog APM/infrastructure monitoring (to benefit from runtime context) and that accept per-committer and per-host security licensing.

Get a comprehensive analysis of Datadog Code Security including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →