Datadog BYOC Logs
Datadog log processing, indexing and storage in the customer's cloud, with search through Datadog Log Explorer.
14 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
Datadog BYOC chart 0.6.0 indexer policy transition
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.
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.
Primary source · Reviewed 2026-11-20
What lands where
Supplied by
Vendor or project
Install the BYOC Logs engine and Observability Pipelines Worker with Helm. An operator-managed installation is documented on Amazon EKS.
External vendor control plane
Runs in
Documented customer environment
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.
- AWS: Customer cloud account
- Azure: Customer cloud account
- Google Cloud: Customer cloud account
- AWS
- Azure
- Google Cloud
Servers / containers
Operated by
Your team
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.
Deployment boundaries by provider
- AWS: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Datadog BYOC Logs on Amazon EKS ↗ · Source checked 2026-11-20
- Azure: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Datadog BYOC Logs on Azure AKS ↗ · Source checked 2026-11-20
- Google Cloud: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
Datadog BYOC Logs on Google GKE ↗ · Source checked 2026-11-20
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.
Operating responsibility source ↗ · Checked 2026-11-20
Customer deployment and cluster configuration ↗
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Install the BYOC Logs engine and Observability Pipelines Worker with Helm. An operator-managed installation is documented on Amazon EKS. |
|---|---|
| Infrastructure | Servers / containers Production workload uses Kubernetes, object storage and PostgreSQL. The listing's runtime describes the customer-operated engine and workers. |
| Licensing model | Commercial Only 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. |
| License | Commercial Datadog software and service. Confirm BYOC Logs activation and commercial terms with the account team. |
Buyer diligence
Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.
How to read these facts
Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.
12 of 12 fields researched (100%) · 8 documented · 4 unresolved. Evidence coverage is not a feature score.
- Marketplace delivery
Not confirmedEvidence and scope for Marketplace delivery
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.
Datadog BYOC Logs: reviewed customer-cloud deployment · Source ↗ · Reviewed 2026-11-20
Sources checked — unresolved · Editor reviewed.
- Cloud commitment eligibility
Not confirmedEvidence and scope for Cloud commitment eligibility
No exact offer and buyer-agreement combination establishes cloud-commitment credit. Customer infrastructure charges, software procurement and private-offer eligibility must be assessed separately.
Datadog BYOC Logs: reviewed customer-cloud deployment · Source ↗ · Reviewed 2026-11-20
Sources checked — unresolved · Editor reviewed.
- Single sign-on
AvailableEvidence and scope for Single sign-on
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.
Datadog hosted account/control-plane identity; not an independent engine login · Source ↗ · BYOC query and control-plane boundary ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- SCIM provisioning
Edition-dependentEvidence and scope for SCIM provisioning
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.
Plan-dependent hosted Datadog organization provisioning · Source ↗ · Reviewed 2026-11-20
Edition-dependent · Editor reviewed.
- Compliance attestations
Not confirmedEvidence and scope for Compliance attestations
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.
Datadog BYOC Logs: reviewed customer-cloud deployment · Source ↗ · Reviewed 2026-11-20
Sources checked — unresolved · Editor reviewed.
- Security controls
DocumentedEvidence and scope for Security controls
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.
BYOC query/control-plane connectivity and configurable customer-side controls · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- Air-gapped operation
Not availableEvidence and scope for Air-gapped operation
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.
Complete documented Datadog BYOC Logs workflow, including hosted UI · Source ↗ · Reviewed 2026-11-20
Explicitly unsupported · Editor reviewed.
- Deployment artifact / IaC
AvailableEvidence and scope for Deployment artifact / IaC
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.
BYOC engine artifact plus separate Worker and cloud dependencies · Source ↗ · Deployment artifact ↗ (cloudprem 0.6.0 / engine v0.1.36; sha256:7cf894e6c9fd3dc4e28f120fd354847151ea414e7885b7724d73fe2f1babae73) · Separate Worker artifact; not asserted to be a validated pair ↗ · Vendor update/compatibility policy ↗ · Engine release and StatefulSet migration ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing
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.
Vendor sizing model and assumptions; not a universal minimum or measured workload/cost estimate · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
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.
Commercial activation/licensing boundary, not an operating-cost estimate · Source ↗ · Datadog EULA ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- Operating cost estimate
Not confirmedEvidence and scope for Operating cost estimate
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.
Datadog BYOC Logs: reviewed customer-cloud deployment · Source ↗ · Reviewed 2026-11-20
Sources checked — unresolved · Editor reviewed.
- Release snapshot / cadence
DocumentedEvidence and scope for Release snapshot / cadence
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.
BYOC engine snapshot and separately documented update policy · Source ↗ · Vendor version-pair and update policy ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
Scope & considerations
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.
Category fit
- Observability
- The customer-cloud Logs engine ingests, indexes, stores and queries operational logs. Datadog hosts the Log Explorer and pipeline configuration UI.
Compare within Observability
- AVEVA PI System (BYOL)Commercial industrial data collection, historian and visualization system with an AWS architecture.
- AWS
- Cloud Carbon FootprintOpen-source cloud-usage, energy and carbon-estimation application.
- Google Cloud
- Coroot Community EditionSelf-hosted application observability with service maps, logs, metrics, traces and continuous profiling.
- AWS
- Azure
- Google Cloud
- Oracle Cloud
- Elastic Cloud EnterpriseCommercial self-managed orchestration platform for Elastic Stack deployments across customer cloud hosts.
- AWS
- Azure
- Google Cloud
- Elastic Cloud on KubernetesElastic's Kubernetes operator for deploying and operating Elasticsearch, Kibana and related Elastic Stack resources in customer clusters.
- AWS
- Azure
- Google Cloud
- Grafana OSS Self-HostedSelf-hosted dashboards, visualization and alerting for operational data.
- AWS
- Langfuse Self-HostedSelf-hosted LLM observability, evaluations and prompt-management platform.
- AWS
- Azure
- Google Cloud
- Railway
- Render
- MLflow Tracking Server Self-HostedSelf-hosted experiment tracking and LLM/agent observability with customer-controlled metadata and artifacts.
- AWS
- Azure
- Google Cloud
Showing 8 of 20 other listings in Observability. These products address related workflows; read their category-fit notes before comparing scope. See all of Observability →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- BYOC Logs install options and account activation ↗docs.datadoghq.com
- Architecture and query-result boundary ↗docs.datadoghq.com
- Connections and network data flow ↗docs.datadoghq.com
- Validated engine and worker updates ↗docs.datadoghq.com
- Datadog End-User License Agreement ↗www.datadoghq.com
- BYOC Logs account configuration and activation ↗docs.datadoghq.com
- Datadog BYOC Logs on Amazon EKS ↗docs.datadoghq.com
- Datadog BYOC Logs on Azure AKS ↗docs.datadoghq.com
- Datadog BYOC Logs on Google GKE ↗docs.datadoghq.com
- Buyer evidence: scim ↗docs.datadoghq.com
- Separate Worker artifact; not asserted to be a validated pair ↗github.com
- Engine release and StatefulSet migration ↗docs.datadoghq.com
- Buyer evidence: sso ↗docs.datadoghq.com
- Buyer evidence: footprint ↗docs.datadoghq.com
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- Datadog BYOC Logs on Amazon EKS ↗ · AWS
Vendor / upstream documentation · Reviewed 2026-11-20. Vendor support commitment: not assessed; confirm the selected release and contract.
Vendor guide installs the engine in the customer's EKS cluster using S3 and PostgreSQL. Helm and the EKS-specific Datadog Operator are documented.
- Datadog BYOC Logs on Azure AKS ↗ · Azure
Vendor / upstream documentation · Reviewed 2026-11-20. Vendor support commitment: not assessed; confirm the selected release and contract.
Vendor guide installs the engine into the customer's AKS cluster with Azure Blob Storage and PostgreSQL Flexible Server.
- Datadog BYOC Logs on Google GKE ↗ · Google Cloud
Vendor / upstream documentation · Reviewed 2026-11-20. Vendor support commitment: not assessed; confirm the selected release and contract.
Vendor guide installs the engine in the customer's Google Cloud project with GKE, Cloud Storage, PostgreSQL and Workload Identity.
- Datadog BYOC Logs on Amazon EKS ↗ · AWS
- Infrastructure evidenceChecked
- Licensing evidenceChecked