
# Datadog BYOC Logs

Datadog log processing, indexing and storage in the customer's cloud, with search through Datadog Log Explorer.

Canonical page: https://launchinyourcloud.com/directory/datadog-byoc-logs/
Catalog revision: 170de95bb7d832897d269051ad4500713acf96a62f3d01bc1d4e649679a56fde




Named clouds have provider-specific evidence. Missing clouds do not establish incompatibility. Preserve edition, account boundary, operating responsibilities and publisher disclosures. Source review dates record human checks, not rebuilds.


1 listing.


## Datadog BYOC Logs

Datadog log processing, indexing and storage in the customer's cloud, with search through Datadog Log Explorer.

- Listing: https://launchinyourcloud.com/directory/datadog-byoc-logs/
- Publisher listing: No
- Entry kind: product
- Documented cloud IDs: aws, azure, gcp
- Operating model: Customer-operated · vendor control plane
- Infrastructure IDs: servers
- License: Commercial Datadog software and service. Confirm BYOC Logs activation and commercial terms with the account team.
- Licensing model: commercial-only
- Installation: Install the BYOC Logs engine and Observability Pipelines Worker with Helm. An operator-managed installation is documented on Amazon EKS.
- Architecture: Customer-operated Kubernetes engine and pipeline workers use object storage for log data and PostgreSQL for index metadata. Datadog hosts the UI and routes queries.
- Operations: The customer provisions and sizes the cluster, manages storage, database, IAM and network connectivity, and applies validated engine and Worker version pairs. Datadog maintains the hosted UI.
- Product website: https://docs.datadoghq.com/byoc-logs/
- Source review: 2026-11-20; cloud review: 2026-11-20; licensing review: 2026-11-20; infrastructure review: 2026-11-20

### Scope and qualifications

Log ingestion, indexing and storage run in the customer's account. Matching query results travel to Datadog for display. The default connection is outbound from searcher pods to Datadog. Confirm service-site availability and account activation. A Docker path is documented for local evaluation. Docker is evaluation-only, and the Operator path is EKS-only. Engine v0.1.36/chart 0.6.0 needs the documented StatefulSet policy migration on existing clusters. Hosted Datadog SSO/SCIM and compliance boundaries remain distinct from the customer engine.

The offering requires a Datadog account and the vendor's terms. Account activation and the customer's applicable pricing and entitlement should be confirmed with Datadog.

Production workload uses Kubernetes, object storage and PostgreSQL. The listing's runtime describes the customer-operated engine and workers.


### Category fit

- observability: The customer-cloud Logs engine ingests, indexes, stores and queries operational logs. Datadog hosts the Log Explorer and pipeline configuration UI.

### Deployment boundaries


- aws: Customer cloud account; Customer-operated; control plane: vendor-hosted. Source: https://docs.datadoghq.com/byoc-logs/install/aws_eks/ (checked 2026-11-20). 

- azure: Customer cloud account; Customer-operated; control plane: vendor-hosted. Source: https://docs.datadoghq.com/byoc-logs/install/azure_aks/ (checked 2026-11-20). 

- gcp: Customer cloud account; Customer-operated; control plane: vendor-hosted. Source: https://docs.datadoghq.com/byoc-logs/install/gcp_gke/ (checked 2026-11-20). 

Operating responsibility: The customer installs and operates log processing, indexing and storage in its infrastructure. The Datadog-hosted UI submits queries and receives results; storing logs locally does not establish a disconnected or wholly customer-operated management plane. Source: https://docs.datadoghq.com/byoc-logs/introduction.md (checked 2026-11-20). Supporting source: Customer deployment and cluster configuration — https://docs.datadoghq.com/byoc-logs/install.md.


### Cloud deployment evidence

- Datadog BYOC Logs on Amazon EKS (aws): https://docs.datadoghq.com/byoc-logs/install/aws_eks/
  Vendor guide installs the engine in the customer's EKS cluster using S3 and PostgreSQL. Helm and the EKS-specific Datadog Operator are documented.
  Source type: vendor-documentation; reviewed: 2026-11-20; vendor support: not-assessed.

- Datadog BYOC Logs on Azure AKS (azure): https://docs.datadoghq.com/byoc-logs/install/azure_aks/
  Vendor guide installs the engine into the customer's AKS cluster with Azure Blob Storage and PostgreSQL Flexible Server.
  Source type: vendor-documentation; reviewed: 2026-11-20; vendor support: not-assessed.

- Datadog BYOC Logs on Google GKE (gcp): https://docs.datadoghq.com/byoc-logs/install/gcp_gke/
  Vendor guide installs the engine in the customer's Google Cloud project with GKE, Cloud Storage, PostgreSQL and Workload Identity.
  Source type: vendor-documentation; reviewed: 2026-11-20; vendor support: not-assessed.


### Sources

- BYOC Logs install options and account activation: https://docs.datadoghq.com/byoc-logs/install/

- Architecture and query-result boundary: https://docs.datadoghq.com/byoc-logs/introduction/architecture/

- Connections and network data flow: https://docs.datadoghq.com/byoc-logs/introduction/network/

- Validated engine and worker updates: https://docs.datadoghq.com/byoc-logs/operate/updates/

- Datadog End-User License Agreement: https://www.datadoghq.com/legal/eula/

- BYOC Logs account configuration and activation: https://docs.datadoghq.com/byoc-logs/configure/

- Datadog BYOC Logs on Amazon EKS: https://docs.datadoghq.com/byoc-logs/install/aws_eks/

- Datadog BYOC Logs on Azure AKS: https://docs.datadoghq.com/byoc-logs/install/azure_aks/

- Datadog BYOC Logs on Google GKE: https://docs.datadoghq.com/byoc-logs/install/gcp_gke/

- Buyer evidence: scim: https://docs.datadoghq.com/account_management/scim/

- Separate Worker artifact; not asserted to be a validated pair: https://github.com/DataDog/helm-charts/releases/download/observability-pipelines-worker-2.26.0/observability-pipelines-worker-2.26.0.tgz

- Engine release and StatefulSet migration: https://docs.datadoghq.com/byoc-logs/release_notes/

- Buyer evidence: sso: https://docs.datadoghq.com/account_management/saml/

- Buyer evidence: footprint: https://docs.datadoghq.com/byoc-logs/operate/sizing/

### Licensing sources

- https://www.datadoghq.com/legal/eula/

- https://docs.datadoghq.com/byoc-logs/configure/

### Infrastructure sources

- https://docs.datadoghq.com/byoc-logs/install/

- https://docs.datadoghq.com/byoc-logs/introduction/architecture/


### Buyer diligence


Research coverage: 12/12 fields (100%); 8 documented, 4 unresolved. Coverage is not a feature score.

Unrecorded fields are not researched, not a statement that the feature is unavailable. Sources checked — unresolved means the cited material did not establish an answer. Hosted-service certifications do not automatically cover customer installations.


- Marketplace delivery: Sources checked — unresolved. The reviewed edition and deployment sources do not establish an exact marketplace offer, seller and delivery artifact that entitle this edition. A vendor SaaS subscription or another edition is insufficient. Scope: Datadog BYOC Logs: reviewed customer-cloud deployment. Source: https://docs.datadoghq.com/byoc-logs/install/ (reviewed 2026-11-20).

- Cloud commitment eligibility: Sources checked — unresolved. No exact offer and buyer-agreement combination establishes cloud-commitment credit. Customer infrastructure charges, software procurement and private-offer eligibility must be assessed separately. Scope: Datadog BYOC Logs: reviewed customer-cloud deployment. Source: https://docs.datadoghq.com/byoc-logs/install/ (reviewed 2026-11-20).

- Single sign-on: Documented. The hosted Datadog organization used for Log Explorer supports SAML SSO with a configured identity provider. This authenticates users to Datadog’s hosted UI; the customer-side engine connection instead uses Datadog API credentials and the selected network configuration. Scope: Datadog hosted account/control-plane identity; not an independent engine login. Source: https://docs.datadoghq.com/account_management/saml/ (reviewed 2026-11-20). Supporting source: BYOC query and control-plane boundary — https://docs.datadoghq.com/byoc-logs/introduction/architecture/.

- SCIM provisioning: Edition-dependent. Datadog documents SCIM user/team/role provisioning for Infrastructure Pro, Infrastructure Enterprise and Startup plans. Confirm the organization’s plan entitlement; BYOC Logs activation alone does not establish it. The endpoint manages hosted Datadog organization identities, not local engine users. Scope: Plan-dependent hosted Datadog organization provisioning. Source: https://docs.datadoghq.com/account_management/scim/ (reviewed 2026-11-20).

- Compliance attestations: Sources checked — unresolved. No reviewed independent report establishes certification of this customer-operated deployment and its infrastructure. Publisher or SaaS attestations do not automatically cover the customer installation; obtain scope, validity and shared responsibilities. Scope: Datadog BYOC Logs: reviewed customer-cloud deployment. Source: https://docs.datadoghq.com/byoc-logs/install/ (reviewed 2026-11-20).

- Security controls: Documented. The default searcher-initiated reverse connection uses outbound HTTPS/WebSocket access to Datadog and carries queries, results and index-management messages without a public query ingress. The optional public ingress uses mTLS. Review API credentials, storage IAM, network restrictions and the resulting query-result egress. Scope: BYOC query/control-plane connectivity and configurable customer-side controls. Source: https://docs.datadoghq.com/byoc-logs/introduction/network/ (reviewed 2026-11-20).

- Air-gapped operation: Explicitly unsupported. The documented BYOC workflow depends on a connection to the hosted Datadog UI/control plane. Searchers maintain outbound connections by default, or Datadog connects through an optional ingress. This connected offering does not provide a documented fully disconnected mode. Scope: Complete documented Datadog BYOC Logs workflow, including hosted UI. Source: https://docs.datadoghq.com/byoc-logs/introduction/network/ (reviewed 2026-11-20).

- Deployment artifact / IaC: Documented. The inspected cloudprem chart 0.6.0 packages engine v0.1.36. The separately indexed Worker chart is 2.26.0; observing both artifacts does not establish a validated engine/Worker pair. Select the vendor-approved combination. Chart 0.6.0 changes the indexer StatefulSet pod-management default; existing installations need the documented migration or an OrderedReady override. Scope: BYOC engine artifact plus separate Worker and cloud dependencies. Source: https://docs.datadoghq.com/byoc-logs/install/ (reviewed 2026-11-20). Deployment artifact: https://github.com/DataDog/helm-charts/releases/download/cloudprem-0.6.0/cloudprem-0.6.0.tgz. Artifact reference: cloudprem 0.6.0 / engine v0.1.36; sha256:7cf894e6c9fd3dc4e28f120fd354847151ea414e7885b7724d73fe2f1babae73. Supporting source: Separate Worker artifact; not asserted to be a validated pair — https://github.com/DataDog/helm-charts/releases/download/observability-pipelines-worker-2.26.0/observability-pipelines-worker-2.26.0.tgz. Supporting source: Vendor update/compatibility policy — https://docs.datadoghq.com/byoc-logs/operate/updates/. Supporting source: Engine release and StatefulSet migration — https://docs.datadoghq.com/byoc-logs/release_notes/.

- Minimum footprint / sizing: Documented. The sizing guide starts indexers at 2 vCPUs per TB/day, compactors at 1 vCPU per 2 TB/day and searchers near twice the indexer CPU, with query-driven adjustment. It separately sizes control services, Workers and PostgreSQL and recommends Multi-AZ database availability. Its 1 TB/day example assumes 30-day retention and roughly 6x compression; 1 TB stored is a different input. Scope: Vendor sizing model and assumptions; not a universal minimum or measured workload/cost estimate. Source: https://docs.datadoghq.com/byoc-logs/operate/sizing/ (reviewed 2026-11-20).

- License pricing: Documented. BYOC Logs is commercial Datadog software/service and requires activation through the account team. The reviewed materials do not establish an all-in public BYOC unit price or a customer quote; organization plan entitlements, engine/Worker billing and customer cloud charges must be confirmed separately. Scope: Commercial activation/licensing boundary, not an operating-cost estimate. Source: https://docs.datadoghq.com/byoc-logs/install/ (reviewed 2026-11-20). Supporting source: Datadog EULA — https://www.datadoghq.com/legal/eula/.

- Operating cost estimate: Sources checked — unresolved. No complete dated operating-cost estimate is established. The AWS us-east-1 baseline of 100 internal users, 1 TB stored data and HA still needs daily telemetry ingestion, retention, monitored infrastructure, query concurrency and commercial entitlements. Human user count does not size the telemetry backend. Scope: Datadog BYOC Logs: reviewed customer-cloud deployment. Source: https://docs.datadoghq.com/byoc-logs/install/ (reviewed 2026-11-20).

- Release snapshot / cadence: Documented. The reviewed BYOC engine snapshot is v0.1.36, dated November 3, 2026 and bundled in cloudprem chart 0.6.0. Engine, Worker and charts have separate versions; use the vendor-validated combination. Datadog states an engine release cadence of at least monthly, which is a vendor policy rather than a support guarantee from this directory. Scope: BYOC engine snapshot and separately documented update policy. Source: https://docs.datadoghq.com/byoc-logs/release_notes/ (reviewed 2026-11-20). Supporting source: Vendor version-pair and update policy — https://docs.datadoghq.com/byoc-logs/operate/updates/.




### Security and lifecycle reviews

Selected editorial reviews only; no flag does not mean safe or supported.

- Datadog BYOC chart 0.6.0 indexer policy transition (lifecycle): Chart 0.6.0 defaults indexer podManagementPolicy to Parallel, an immutable StatefulSet field. Existing deployments need an override or the documented migration. Scope: BYOC engine v0.1.36 packaged in cloudprem chart 0.6.0; chart and application versions are separate. Conditions: Clusters running nodes older than engine v0.1.33 also need the documented gossip protocol compatibility setting during the transition. Action: Retain OrderedReady explicitly or follow the indexer StatefulSet migration. Keep gossip protocol 0 while older nodes remain, then apply the vendor-approved engine/Worker versions. Source: https://docs.datadoghq.com/byoc-logs/release_notes/; reviewed 2026-11-20.



