Datadog CloudPrem

Name: Datadog CloudPrem
Brand: Datadog

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

MarketsObservability Platform

Published May 16, 2026

01Common complaints

1) An organization cannot operate production-grade Kubernetes and supporting data services CloudPrem requires Kubernetes 1.25+, object storage, and PostgreSQL. If an organization cannot reliably operate these components, a managed logs backend (Datadog SaaS logs, Elastic serverless, Grafana Cloud) may be a lower-risk option. 2) Immediate feature parity with Datadog SaaS Logs is required CloudPrem lists several missing capabilities (for example: Notebooks, LiveTail, Watchdogs, federated search, and certain AI features). Organizations that require full Datadog Logs parity immediately should consider the documented limitations. 3) The primary problem is Datadog commercial complexity across the entire stack CloudPrem may reduce SaaS log storage costs, but it does not automatically simplify overall Datadog pricing complexity (hosts, containers, APM, metrics cardinality, or security products). Organizations seeking simpler ingest/retention pricing models may prefer alternatives with explicit unit pricing. 4) A fully open, vendor-neutral stack is required for portability If an organization prefers a purely OpenTelemetry-centric approach and maximum backend portability (ClickHouse, Elastic, Loki), CloudPrem’s operational and commercial model may feel more tightly coupled to Datadog.

Deal disqualifiers (poor fit)

Lack of Kubernetes operational maturity
Requirement for a fully managed SaaS logging solution with minimal operations
Need for immediate feature parity with Datadog Logs; CloudPrem documents multiple unsupported features at the time of writing

CloudPrem is in Preview

Datadog documentation labels CloudPrem as a Preview release and indicates access is provided via request. https://docs.datadoghq.com/cloudprem/

Feature gaps (explicitly documented)

CloudPrem documentation lists features that are not supported in the Preview release, including some AI features and user-facing capabilities such as Notebooks, LiveTail, Watchdogs, federated search, and multi-retention index management.

Operational requirements

CloudPrem requires:

Kubernetes 1.25+ as a runtime
PostgreSQL as a metadata store
Compatible object storage (S3, GCS, Azure Blob, MinIO, Ceph, or S3-compatible stores)

Workload-dependent sizing

Vendor documentation indicates that resource requirements (for example, searcher nodes) depend on workload characteristics and should be validated empirically.

02Why they buy

Key product capabilities supported by vendor documentation and market context

- Datadog integration with BYOC log storage: CloudPrem enables logs to remain in the customer environment while allowing use of Datadog Log Explorer workflows. - Architecture intended for large-scale workloads: vendor documentation describes an object storage-centric architecture with stateless search nodes and indexing based on Quickwit. - Regulated-data positioning: product messaging emphasizes data residency and sensitive-data handling features (detection rules and related capabilities).

Where competitors have clear advantages

Pricing transparency: some competitors publish unit pricing and clearer billing components, while CloudPrem pricing is not publicly posted.
Maturity and ecosystem openness: long-standing open-source ecosystems (Grafana, Elastic) provide a range of self-managed and managed options.

03Field reports

Review-platform reality check: CloudPrem-specific reviews are limited

CloudPrem is in Preview, and review platforms contain few CloudPrem-specific reviews. Organizations should infer CloudPrem experience from general Datadog reviews on G2, TrustRadius, Capterra, community discussions, and analyst commentary about Datadog’s hybrid strategy and the Quickwit integration.

G2 (general Datadog) — positive and negative themes

G2’s Datadog review summaries identify recurring themes: - Pros: unified observability, correlation across logs, metrics, and traces, and real-time insights - Cons: costs can increase rapidly with greater usage Example positive reviewer quote (G2): - "Datadog provides an excellent all-in-one monitoring solution that gives complete visibility into infrastructure, applications, and logs." (review excerpt visible on G2 page) Example negative theme seen on G2: - "Expensive" and "Pricing Issues" appear prominently in cons and tags.

TrustRadius (general Datadog) — adoption and pricing context

TrustRadius lists numerous Datadog reviews and provides reference pricing for some Datadog tiers in its summaries.

Capterra (general Datadog) — balanced snippets

Capterra review snippets reference both positive and negative experiences:

Positive: customizable dashboards and automated alerting providing full-stack visibility (example: a financial services reviewer)
Negative: some reviewers cite slow response to issues and compatibility gaps with OpenTelemetry in certain use cases
Cost: multiple reviewers cite Datadog’s pricing as relatively high

Gartner Peer Insights — general sentiment

Gartner Peer Insights pages accessible during this research reflect buyer sentiment on themes such as usage-based pricing, cost estimation challenges, and a learning curve for some advanced features.

Community (Reddit) — cost, billing surprises, and value debates

Reddit threads commonly highlight Datadog’s usability and reliability alongside cost and billing critiques.

Representative community statements include strong negative experiences about cost increases and counterpoints from users who find Datadog effective when used selectively.

Why customers choose Datadog (inferred from reviews)

Common reasons stated by reviewers and users include:

A single interface for correlated telemetry (logs, metrics, traces)
Broad integration support
Faster troubleshooting and reduced mean time to repair (MTTR) due to correlated telemetry

Why some customers leave or consider alternatives

Common churn drivers include:

Costs that scale poorly with increased telemetry volume and high-cardinality metrics
Billing surprises and contract friction
Preference for open tooling (OpenTelemetry) with lower-cost backends

Vendor-published architecture and claimed outcomes (not independently validated)

Datadog’s CloudPrem announcement and related posts describe an architecture using object storage, stateless query nodes, and an indexing model. The vendor claims cost and performance advantages versus legacy self-hosted systems but does not publish third-party benchmarks or a transparent benchmark methodology in the announcement. Critical evaluation: - The vendor’s architectural description provides a plausible rationale for decoupling compute and storage, but organizations should request empirical benchmarks (indexing throughput, query latency at scale, and storage compression ratios) using representative workloads. - Claims of very large scale should be treated as vendor descriptions unless accompanied by reproducible sizing guidance and service-level objectives.

Implementation detail availability

CloudPrem installation documentation provides prerequisites such as supported Kubernetes versions, a PostgreSQL metadata store, and compatible object storage backends (S3, GCS, Azure Blob, MinIO, Ceph, and other S3-compatible stores). Time-to-value considerations: - Quickstart examples are available in documentation, but production readiness depends on cluster provisioning, IAM, networking, storage performance, disaster recovery, and observability for the CloudPrem components themselves.

04Best fit

Company sizes

Most suitable fit:

Mid-market to enterprise organizations with substantial log volumes and compliance obligations.
Smaller organizations can benefit, but CloudPrem’s operational requirements (Kubernetes, storage, Postgres) may make it less practical without managed operations.

Industries

Strong alignment:

Financial services, insurance, healthcare, government, and other regulated sectors with residency or retention requirements
Security-focused environments generating large volumes of firewall, WAF, CDN, and VPC flow logs

Roles and personas

Platform engineering and SRE leadership
Security engineering and SOC teams (for security data lake patterns)
Cloud infrastructure and operations leadership
Compliance and risk stakeholders (for data residency requirements)

Qualification criteria (good fit)

Broad existing use of Datadog and a desire to avoid splitting incident workflows across tools
Needs for extended log retention at scale with residency constraints
Capability to operate Kubernetes clusters or a managed Kubernetes strategy

05The pitch

What the product does (core value proposition)

Datadog CloudPrem is a bring-your-own-cloud / self-hosted log storage and search offering that runs inside a customer-controlled environment (Kubernetes + object storage), while remaining integrated with the Datadog SaaS experience (for example, Log Explorer UI and cross-telemetry correlation). The offering is intended to let organizations retain and query very large log volumes (Datadog describes the capability as very large scale) with data residency control and the possibility of lower storage costs when using existing cloud commitments or discounts. Key vendor-positioned capabilities include: - Store, search, and analyze logs inside the customer environment while using Datadog UI and workflows for investigation. - Correlate self-hosted logs with Datadog SaaS metrics, traces, and RUM for incident investigation. - Use Datadog "Bits AI" and AI-assisted workflows (not all AI features are supported in CloudPrem at the time of writing — see limitations). - Use CloudPrem as a security log lake (OCSF support and long-retention positioning). Important framing: CloudPrem is positioned as a hybrid model: the log data plane runs in the customer environment, while much of the user interface and broader Datadog platform context remain in Datadog’s SaaS. Official product page: Product overview and feature pages from the vendor. Official docs landing page (Preview): Official product documentation (Preview).

Target market and market positioning

CloudPrem appears aimed at: - Large-scale, log-heavy organizations (security, networking, high-volume application logs) where Datadog SaaS log costs or retention requirements are material. - Regulated industries (financial services, healthcare, insurance, public sector) with data residency constraints or policies requiring logs to remain in-region or under customer control. - Teams that already standardize on Datadog for metrics and APM but want to avoid maintaining a separate logging platform for long-retention or high-volume streams. Datadog’s messaging highlights vendor claims such as large-scale capacity, reduced operational burden, and compliance. CloudPrem is released in Preview, so some organizations may treat it as early-stage or limited-access rather than a fully mature GA component.

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

Download full report →

Published May 16, 2026

01Common complaints

An organization cannot operate production-grade Kubernetes and supporting data services

CloudPrem requires Kubernetes 1.25+, object storage, and PostgreSQL. If an organization cannot reliably operate these components, a managed logs backend (Datadog SaaS logs, Elastic serverless, Grafana Cloud) may be a lower-risk option.

Immediate feature parity with Datadog SaaS Logs is required

CloudPrem lists several missing capabilities (for example: Notebooks, LiveTail, Watchdogs, federated search, and certain AI features). Organizations that require full Datadog Logs parity immediately should consider the documented limitations.

The primary problem is Datadog commercial complexity across the entire stack

CloudPrem may reduce SaaS log storage costs, but it does not automatically simplify overall Datadog pricing complexity (hosts, containers, APM, metrics cardinality, or security products). Organizations seeking simpler ingest/retention pricing models may prefer alternatives with explicit unit pricing.

A fully open, vendor-neutral stack is required for portability

If an organization prefers a purely OpenTelemetry-centric approach and maximum backend portability (ClickHouse, Elastic, Loki), CloudPrem’s operational and commercial model may feel more tightly coupled to Datadog.

Deal disqualifiers (poor fit)

Lack of Kubernetes operational maturity
Requirement for a fully managed SaaS logging solution with minimal operations
Need for immediate feature parity with Datadog Logs; CloudPrem documents multiple unsupported features at the time of writing

CloudPrem is in Preview

Datadog documentation labels CloudPrem as a Preview release and indicates access is provided via request. https://docs.datadoghq.com/cloudprem/

Feature gaps (explicitly documented)

Operational requirements

CloudPrem requires:

Kubernetes 1.25+ as a runtime
PostgreSQL as a metadata store
Compatible object storage (S3, GCS, Azure Blob, MinIO, Ceph, or S3-compatible stores)

Workload-dependent sizing

Vendor documentation indicates that resource requirements (for example, searcher nodes) depend on workload characteristics and should be validated empirically.

02Why they buy

Key product capabilities supported by vendor documentation and market context

Datadog integration with BYOC log storage: CloudPrem enables logs to remain in the customer environment while allowing use of Datadog Log Explorer workflows.
Architecture intended for large-scale workloads: vendor documentation describes an object storage-centric architecture with stateless search nodes and indexing based on Quickwit.
Regulated-data positioning: product messaging emphasizes data residency and sensitive-data handling features (detection rules and related capabilities).

Where competitors have clear advantages

Pricing transparency: some competitors publish unit pricing and clearer billing components, while CloudPrem pricing is not publicly posted.
Maturity and ecosystem openness: long-standing open-source ecosystems (Grafana, Elastic) provide a range of self-managed and managed options.

03Field reports

Review-platform reality check: CloudPrem-specific reviews are limited

G2 (general Datadog) — positive and negative themes

G2’s Datadog review summaries identify recurring themes:

Pros: unified observability, correlation across logs, metrics, and traces, and real-time insights
Cons: costs can increase rapidly with greater usage

Example positive reviewer quote (G2):

"Datadog provides an excellent all-in-one monitoring solution that gives complete visibility into infrastructure, applications, and logs." (review excerpt visible on G2 page)

Example negative theme seen on G2:

"Expensive" and "Pricing Issues" appear prominently in cons and tags.

TrustRadius (general Datadog) — adoption and pricing context

TrustRadius lists numerous Datadog reviews and provides reference pricing for some Datadog tiers in its summaries.

Capterra (general Datadog) — balanced snippets

Capterra review snippets reference both positive and negative experiences:

Positive: customizable dashboards and automated alerting providing full-stack visibility (example: a financial services reviewer)
Negative: some reviewers cite slow response to issues and compatibility gaps with OpenTelemetry in certain use cases
Cost: multiple reviewers cite Datadog’s pricing as relatively high

Gartner Peer Insights — general sentiment

Gartner Peer Insights pages accessible during this research reflect buyer sentiment on themes such as usage-based pricing, cost estimation challenges, and a learning curve for some advanced features.

Community (Reddit) — cost, billing surprises, and value debates

Reddit threads commonly highlight Datadog’s usability and reliability alongside cost and billing critiques.

Representative community statements include strong negative experiences about cost increases and counterpoints from users who find Datadog effective when used selectively.

Why customers choose Datadog (inferred from reviews)

Common reasons stated by reviewers and users include:

A single interface for correlated telemetry (logs, metrics, traces)
Broad integration support
Faster troubleshooting and reduced mean time to repair (MTTR) due to correlated telemetry

Why some customers leave or consider alternatives

Common churn drivers include:

Costs that scale poorly with increased telemetry volume and high-cardinality metrics
Billing surprises and contract friction
Preference for open tooling (OpenTelemetry) with lower-cost backends

Vendor-published architecture and claimed outcomes (not independently validated)

Critical evaluation:

The vendor’s architectural description provides a plausible rationale for decoupling compute and storage, but organizations should request empirical benchmarks (indexing throughput, query latency at scale, and storage compression ratios) using representative workloads.
Claims of very large scale should be treated as vendor descriptions unless accompanied by reproducible sizing guidance and service-level objectives.

Implementation detail availability

Time-to-value considerations:

Quickstart examples are available in documentation, but production readiness depends on cluster provisioning, IAM, networking, storage performance, disaster recovery, and observability for the CloudPrem components themselves.

04Best fit

Company sizes

Most suitable fit:

Mid-market to enterprise organizations with substantial log volumes and compliance obligations.
Smaller organizations can benefit, but CloudPrem’s operational requirements (Kubernetes, storage, Postgres) may make it less practical without managed operations.

Industries

Strong alignment:

Financial services, insurance, healthcare, government, and other regulated sectors with residency or retention requirements
Security-focused environments generating large volumes of firewall, WAF, CDN, and VPC flow logs

Roles and personas

Platform engineering and SRE leadership
Security engineering and SOC teams (for security data lake patterns)
Cloud infrastructure and operations leadership
Compliance and risk stakeholders (for data residency requirements)

Qualification criteria (good fit)

Broad existing use of Datadog and a desire to avoid splitting incident workflows across tools
Needs for extended log retention at scale with residency constraints
Capability to operate Kubernetes clusters or a managed Kubernetes strategy

05The pitch

What the product does (core value proposition)

Key vendor-positioned capabilities include:

Store, search, and analyze logs inside the customer environment while using Datadog UI and workflows for investigation.
Correlate self-hosted logs with Datadog SaaS metrics, traces, and RUM for incident investigation.
Use Datadog "Bits AI" and AI-assisted workflows (not all AI features are supported in CloudPrem at the time of writing — see limitations).
Use CloudPrem as a security log lake (OCSF support and long-retention positioning).

Important framing: CloudPrem is positioned as a hybrid model: the log data plane runs in the customer environment, while much of the user interface and broader Datadog platform context remain in Datadog’s SaaS.

Official product page: Product overview and feature pages from the vendor. Official docs landing page (Preview): Official product documentation (Preview).

Target market and market positioning

CloudPrem appears aimed at:

Large-scale, log-heavy organizations (security, networking, high-volume application logs) where Datadog SaaS log costs or retention requirements are material.
Regulated industries (financial services, healthcare, insurance, public sector) with data residency constraints or policies requiring logs to remain in-region or under customer control.
Teams that already standardize on Datadog for metrics and APM but want to avoid maintaining a separate logging platform for long-retention or high-volume streams.

Datadog’s messaging highlights vendor claims such as large-scale capacity, reduced operational burden, and compliance. CloudPrem is released in Preview, so some organizations may treat it as early-stage or limited-access rather than a fully mature GA component.

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

Download full report →