Datadog Kubernetes Autoscaling

Name: Datadog Kubernetes Autoscaling
Brand: Datadog
Rating: 4.4 (2770 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

MarketsContainer Management Cloud Cost Management

Datadog Kubernetes Autoscaling screenshot

01Competitive Landscape

Narrative competitive analysis

Datadog Kubernetes Autoscaling vs. HPA/VPA (native Kubernetes) - Datadog documents DKA as an alternative to HPA/VPA for a workload and recommends considering removal of existing HPA/VPA configurations for workloads enrolled in DKA. This shifts scaling policy control from native controllers to Datadog’s controller model, which may simplify certain workflows while creating different governance and dependency considerations. Datadog vs. KEDA - KEDA is commonly chosen for event-driven scaling and for portability across clusters; Datadog provides monitoring integrations for KEDA but KEDA remains a common first-choice when scaling is primarily based on external event sources. Datadog vs. CAST AI - CAST AI emphasizes automation for cluster efficiency (bin packing, node scaling automation, spot instance strategies), while Datadog emphasizes rightsizing recommendations and controlled autoscaling actions integrated into an observability platform. Buyers should evaluate governance models and whether autoscaling changes are applied from within an observability UI/remote config or via a dedicated cluster automation platform. Datadog vs. StormForge - StormForge focuses on optimization workflows and publishes pricing metrics tied to compute units. Datadog may be preferable for organizations that already standardize on Datadog for observability and seek to reduce vendor sprawl.

Adoption trends

Independent commentary indicates that cost pressure is motivating evaluations of alternatives (including open-source stacks and other cloud-native observability options), but platform replacement also incurs operational overhead.

	Datadog Kubernetes Autoscaling	CAST AI (Kubernetes cost optimization)	StormForge Optimize Live
Starting Price	Not publicly documented as a standalone SKU; likely bundle/contract dependent	Not transparently listed (sales-led pricing)	Vendor publishes pricing tied to compute/CPU units; see vendor pricing documentation
Suited For	Existing Datadog customers seeking workload rightsizing and integrated autoscaling actions	Teams prioritizing automated cluster cost optimization (bin packing, node scaling automation)	Teams focused on continuous rightsizing and optimization with model-driven recommendations
Key Strength	Integration with Datadog telemetry and workflows; UI and CRD-based control modalities	Focus on cluster automation, node optimization, and spot strategies	Pricing basis tied to compute optimization units and a focus on rightsizing workflows
Key Weakness	Community concerns about cost predictability in dynamic environments; requires Datadog agents and configuration	Some reviewers report dissatisfaction with automation behavior compared to incumbent solutions	Adds another vendor tool to procurement and operations; may overlap with native Kubernetes approaches

01Competitive Landscape

Narrative competitive analysis

Datadog Kubernetes Autoscaling vs. HPA/VPA (native Kubernetes)

Datadog documents DKA as an alternative to HPA/VPA for a workload and recommends considering removal of existing HPA/VPA configurations for workloads enrolled in DKA. This shifts scaling policy control from native controllers to Datadog’s controller model, which may simplify certain workflows while creating different governance and dependency considerations.

Datadog vs. KEDA

KEDA is commonly chosen for event-driven scaling and for portability across clusters; Datadog provides monitoring integrations for KEDA but KEDA remains a common first-choice when scaling is primarily based on external event sources.

Datadog vs. CAST AI

CAST AI emphasizes automation for cluster efficiency (bin packing, node scaling automation, spot instance strategies), while Datadog emphasizes rightsizing recommendations and controlled autoscaling actions integrated into an observability platform. Buyers should evaluate governance models and whether autoscaling changes are applied from within an observability UI/remote config or via a dedicated cluster automation platform.

Datadog vs. StormForge

StormForge focuses on optimization workflows and publishes pricing metrics tied to compute units. Datadog may be preferable for organizations that already standardize on Datadog for observability and seek to reduce vendor sprawl.

Adoption trends

	Datadog Kubernetes Autoscaling	CAST AI (Kubernetes cost optimization)	StormForge Optimize Live
Starting Price	Not publicly documented as a standalone SKU; likely bundle/contract dependent	Not transparently listed (sales-led pricing)	Vendor publishes pricing tied to compute/CPU units; see vendor pricing documentation
Suited For	Existing Datadog customers seeking workload rightsizing and integrated autoscaling actions	Teams prioritizing automated cluster cost optimization (bin packing, node scaling automation)	Teams focused on continuous rightsizing and optimization with model-driven recommendations
Key Strength	Integration with Datadog telemetry and workflows; UI and CRD-based control modalities	Focus on cluster automation, node optimization, and spot strategies	Pricing basis tied to compute optimization units and a focus on rightsizing workflows
Key Weakness	Community concerns about cost predictability in dynamic environments; requires Datadog agents and configuration	Some reviewers report dissatisfaction with automation behavior compared to incumbent solutions	Adds another vendor tool to procurement and operations; may overlap with native Kubernetes approaches