Datadog Pricing in Singapore (2026): AP1 Rates and Cost Examples

Datadog pricing for a Singapore team is a stack of product meters rather than one platform fee. A typical bill can combine Infrastructure hosts, APM hosts, ingested and indexed logs, indexed spans, containers, custom metrics, RUM, synthetics, support, and contract commitments. This guide uses the public AP1 Japan rate card as an APAC benchmark; it is not a Singapore or AP2 Australia quote.

This guide is published by Guance, which offers an observability platform discussed in the cost comparison. Prices and billing documentation were reviewed on 31 July 2026. We did not inspect customer contracts or run a production benchmark. Every percentage below is limited to the disclosed workload and public list rates.

Datadog pricing: the short answer

Datadog publishes separate annual, monthly, and on-demand rates. On the public AP1 list, Infrastructure Pro starts at US$18.75 per host per month with annual billing, APM at US$38.75 per APM host per month, log ingestion at US$0.13 per GB, and 30-day indexed logs at US$3.13 per million events. These are component rates, not an all-in platform price.

For a useful estimate, collect at least:

• hourly infrastructure and APM host usage;
• containers above included allotments;
• ingested and indexed custom metrics;
• uncompressed log GB and indexed log events by retention tier;
• ingested and indexed spans;
• RUM, Session Replay, synthetic, profiling, network, security, and support usage;
• annual commitment, negotiated discount, overage, tax, and migration cost.

The authoritative starting points are the Datadog AP1 price list, Datadog product allotments, and the account’s actual usage and contract.

Why this guide uses AP1 instead of the default US price list

Datadog’s Sites documentation lists AP1 in Japan and AP2 in Australia. It does not list a Singapore Datadog site. Datadog sites are independent, and product availability and endpoints can differ by site.

Related guideHow to Migrate from Datadog in 6 Weeks: Dual-Write, Field Mapping, Rollback (2026)→

The public Japanese rate card identifies AP1 and publishes AP1-specific USD prices. The default US Datadog detailed price list is lower for several headline products, so applying the US page to a Singapore evaluation can materially understate an AP1 benchmark. We did not find a similarly reproducible public AP2 rate card in the official material reviewed.

This does not prove that every Singapore customer must buy AP1, that AP1 prices apply to AP2, or that a negotiated Singapore contract will equal public list rates. Ask Datadog to identify the proposed site and contracted rate schedule in writing.

Annual, monthly, and on-demand are different buying modes

The AP1 page shows three columns:

Do not mix an annual Infrastructure price with an on-demand log price and describe the result as one standard package. Datadog’s billing documentation and the signed order form should determine how committed, included, and on-demand usage interact.

AP1 public rate card at a glance

The following rates were transcribed from the official AP1 list on 31 July 2026. Currency is USD.

Source: Datadog AP1 pricing. The table is not exhaustive. Database Monitoring, RUM, Session Replay, Synthetics, network products, security products, support, and other capabilities have additional meters.

Infrastructure hosts, containers, and high-water usage

Infrastructure Monitoring is not simply “average hosts × headline price.” Datadog documents usage aggregation and allotments in its account billing guide and product allotments page.

For Infrastructure Pro, the public allotment page currently lists, per host:

• 100 Custom Metrics;
• 100 Ingested Custom Metrics;
• 5 Containers;
• 500 Custom Events.

Containers above the included quantity can produce separate charges. Ephemeral clusters, autoscaling, short-lived build nodes, and duplicate Agent deployment can therefore change the bill even when average fleet size looks stable. Use Datadog’s billed-usage exports rather than a CMDB monthly average.

Datadog custom metrics pricing needs two counts

The exact supporting query datadog custom metrics pricing deserves its own worksheet because Datadog documents both Custom Metrics and Ingested Custom Metrics.

Custom Metrics generally depend on a metric name plus unique tag-value combinations. High-cardinality dimensions such as container IDs, request IDs, customer IDs, or rapidly changing deployment labels can create many billable series. The official Custom Metrics billing guide explains the counting model and included allotments.

The AP1 list publishes:

• US$6.25 per 100 Custom Metrics per month;
• US$0.13 per 100 Ingested Custom Metrics per month.

Datadog also documents a separate Metric Name Pricing model. Its applicable commercial rate is not published on the reviewed page, so it is not publicly documented until the account’s contract and usage method are confirmed.

Before estimating, export both the billable custom-metric count and the ingested custom-metric count. Do not infer either from the number of metric names alone.

APM pricing combines hosts, ingestion, and indexed spans

The AP1 annual list price for base APM is US$38.75 per APM host per month. Datadog’s APM billing documentation and product allotments currently show an included allowance of 150 GB of ingested spans and one million indexed spans per APM host per month for base APM.

Above the applicable allowance, the AP1 list publishes:

• US$0.13 per ingested GB;
• US$1.59, US$2.13, or US$3.13 per million indexed spans for 7-, 15-, or 30-day retention under annual billing.

The cost can change with Kubernetes node counting, how the Agent is deployed, service sampling, span volume, retention, and the number of spans deliberately kept for search and analytics. “We send OpenTelemetry” does not remove these backend meters.

Log pricing has both ingestion and indexing

Datadog log cost commonly contains at least two separate components:

1. ingestion for the uncompressed data sent to Datadog; and
2. indexing for the events retained in an index for the selected period.

The AP1 annual public rates used in the model below are:

• US$0.13 per GB of ingested logs;
• US$3.13 per million indexed log events at 30-day retention.

Datadog’s Log Indexes documentation explains that exclusion filters can control which logs remain indexed. Excluding an event from an index can reduce indexing usage, but it does not retroactively remove the ingestion that already occurred. Archives, rehydration, Flex Logs, forwarding, sensitive-data scanning, and pipelines can add other meters.

This distinction is a major reason a “price per GB” comparison can be incomplete: one vendor may charge for bytes plus retained events, while another may use a mutually exclusive entry or traffic model.

RUM, Session Replay, Synthetics, and support must be added separately

An end-to-end Datadog estimate should also identify:

• Browser and Mobile RUM sessions;
• Session Replay sessions and retention;
• API and browser synthetic tests;
• profiling, network, database, security, and incident-management products;
• the selected support plan.

The AP1 list contains the applicable product meters, while Datadog support plans describe Free, Standard, and Premier support structures. Support percentage, response targets, and eligibility can change the commercial result and must come from the quote.

What public pricing cannot tell a Singapore buyer

The following values remain not publicly documented or quote-specific:

• whether the proposed Singapore account will use AP1 or AP2;
• the AP2 price schedule;
• negotiated annual and volume discounts;
• committed quantities, ramp, overage, and unused spend;
• support, onboarding, professional services, tax, and reseller terms;
• site-specific product availability and regional uplift;
• the actual count produced by host, container, metric, span, session, and event rules;
• data export, archive, rehydration, and migration charges;
• whether a different contract model replaces any public rate.

The public list is useful for a reproducible benchmark, not a substitute for a bill or binding quote.

Build the Datadog cost worksheet before comparing vendors

Use one row per product meter and keep committed, included, and on-demand quantities separate.

The comparison should then apply each platform’s units independently. Equal source data does not guarantee equal billed usage.

A reproducible 30-day log scenario

This narrow scenario is intentionally limited to logs because the public meters can be aligned more transparently than a mixed Infrastructure, APM, RUM, and Synthetic bundle.

Assumptions:

• 1 decimal GB of original, uncompressed logs per day;
• 1 million log events per day;
• every event is indexed and retained for 30 days in Datadog;
• every event is under both Guance large-entry splitting thresholds;
• a steady 30-day billing month;
• Datadog AP1 annual public rates;
• Guance Hong Kong & Global default data-count rate;
• no discount, support, tax, archive, rehydration, forwarding, pipeline, scanning, migration, or feature-equivalence claim.

Guance’s official price is US$0.60 per million billed log entries per day at 30-day retention. The Guance billing logic says data-entry billing is the default log model. It also documents that events and self-built synthetic data can enter the same billing item, custom indexes are counted separately, and large entries can be split. Those additions are excluded from this controlled example.

In this disclosed log-only public-rate scenario, Guance is 81.6% lower than the Datadog AP1 annual-list result. That is not a universal Datadog-to-Guance saving and does not establish equal features, search performance, support, or contract scope.

Formula and calculation method

For this scenario:

Datadog monthly logs
= (daily uncompressed GB × 30 × US$0.13)
+ (daily indexed events in millions × 30 × US$3.13)

Guance monthly logs
= daily billed entries in millions × 30 × US$0.60

Scenario-specific saving %
= (Datadog modeled cost - Guance modeled cost)
  / Datadog modeled cost × 100

At 1 GB and 1 million events per day:

Datadog = (1 × 30 × 0.13) + (1 × 30 × 3.13)
        = US$97.80

Guance  = 1 × 30 × 0.60
        = US$18.00

Difference = (97.80 - 18.00) / 97.80
           = 81.6%

This model assumes an average of one decimal kilobyte per event and, more importantly, that no individual Guance event crosses the documented splitting threshold. Use actual event-size distribution in a customer calculation.

Indexing-ratio sensitivity and the 50% threshold

Scaling the same 100% indexing assumption across five traffic volumes would keep the percentage artificially constant. The more useful sensitivity variable is the share of one million daily events kept in Datadog Standard Indexed Logs for 30 days. This table fixes source volume at 1 GB and one million events per day; Guance bills all one million entries under the default data-count model.

Related guideDatadog to OpenTelemetry: The 2026 Migration Playbook (Without Losing Visibility)→

This is not a feature-equivalent comparison: at 10% indexing, Datadog retains only one tenth of the events in the modelled Standard index while the Guance subtotal still counts all entries. The reversal is nevertheless important. It proves that indexing ratio, Standard versus Flex Logs, event-size distribution, Guance entry splitting, and required search scope must be explicit calculator inputs. Discounts, commitments, archives, rehydration, add-ons, and contract terms can move every result again.

What about Guance traffic billing?

Guance also publishes a Hong Kong & Global 30-day rate of US$0.17 per GB of original log write traffic per day. Its official Commercial Plan pricing details and billing logic state that traffic billing is not the default and requires an account manager to enable it.

We exclude that conditional mode from the worked model and headline. Eligibility, contract activation, the definition of GB, entry-size distribution, and the selected Singapore commercial terms remain not publicly documented. A buyer can add it only after the account manager confirms the mode in the proposed order.

Guance’s data-count and traffic models are alternatives for standard log storage; they are not added together in this example.

Can Guance be about 50% cheaper than Datadog?

The public evidence does not establish an approximately 50% difference for a mixed observability workload, so the blanket statement “Guance is 50% cheaper than Datadog” should not be used. In this narrow log model, the arithmetic crosses 50.0% when 34.2% of one million daily events are kept in the Datadog Standard 30-day index. It reaches 81.6% at 100% indexing and reverses when only 10% is indexed. None of those points establishes full-platform total cost or feature parity.

The defensible claim is:

As of 31 July 2026, under the disclosed AP1 annual public-rate log scenario with 1 GB and one million events per day, 100% Standard indexing, and 30-day retention, the modeled Guance known subtotal is US$18.00 versus US$97.80 for Datadog, or 81.6% lower. This result applies only to this scenario and is not a customer quote, full TCO, feature-parity claim, or universal saving.

Use the customer’s billed usage and current quotes to determine the direction and magnitude of the full scoped result without presupposing a 50% outcome.

A sales or landing-page headline should never detach the percentage from the scenario, rate date, region, retention, and exclusions.

When Datadog may cost less or fit better

Datadog may cost less or fit better when:

• a negotiated commitment or volume discount materially reduces the public AP1 rates;
• the organization already has unused Datadog committed spend;
• exclusion filters keep only a small fraction of ingested logs indexed;
• Datadog-specific workflows, integrations, security, support, or team expertise replace other tools or operating labour;
• the Guance account cannot use the intended billing mode;
• Guance billed entries increase because of large-log splitting, multiple indexes, events, or self-built synthetic data;
• Guance add-ons such as forwarding, sensitive-data scanning, security scanning, or Central Pipeline materially increase cost;
• migration, retraining, historical access, and dual-running cost exceed the rate-card difference;
• AP1 or AP2 operational coverage is a better fit than the proposed Guance architecture.

Conversely, Guance may have a stronger cost case when the workload maps cleanly to its published billing unit, the necessary product workflows pass a controlled evaluation, and the Singapore commercial and data terms are confirmed.

Singapore architecture and commercial questions

Guance’s commercial registration documentation lists AP1 on AWS Singapore. A site label does not by itself prove end-to-end residency, backup location, support-data handling, or a specific price schedule.

Ask both vendors to confirm:

• the tenant site and ingestion endpoints;
• production, backup, DR, account, billing, and support-data locations;
• cross-border support access and subprocessors;
• product availability in the proposed site;
• currency, tax, reseller, and regional uplift;
• SLA, support tier, escalation hours, and implementation ownership;
• exit, export, archive, and deletion terms.

For Guance, also confirm whether the Hong Kong & Global rates apply to the AP1 Singapore order and whether default entry billing or account-enabled traffic billing will be used.

Measure both platforms before making a savings claim

OpenTelemetry can support a controlled dual-write for standard signals. Datadog publishes a path-specific OpenTelemetry compatibility matrix, Guance documents OpenTelemetry ingestion through DataKit, and the upstream OpenTelemetry Collector can export to more than one backend.

Run a 7–14 day production-shaped measurement:

1. Export 30 days of Datadog billed usage and the contracted rate schedule.
2. Choose representative services with normal and peak telemetry patterns.
3. Dual-write only the signals whose semantics and privacy controls are understood.
4. Record accepted, rejected, sampled, dropped, ingested, indexed, retained, and queried data.
5. Rebuild only the dashboards and alerts needed to test real incident tasks.
6. Compare investigation coverage, latency, access control, support, and operating labour.
7. Recalculate both invoices with the observed meters and binding quotes.
8. Keep the current alert path and rollback until acceptance criteria are met.

OpenTelemetry compatibility does not migrate Datadog dashboards, monitors, SLOs, roles, workflows, history, or proprietary behavior automatically.

Procurement checklist

Before accepting a Datadog quote, ask:

1. Which site and rate card apply to the Singapore account?
2. What are the annual commitment, monthly, on-demand, and overage rates for every used product?
3. Which host, container, custom-metric, log, and span allotments apply?
4. How are high-water, hourly, and monthly quantities calculated for this contract?
5. What were the measured ingested GB and indexed events or spans during the POC?
6. Which retention tiers and archives are included?
7. What support, tax, reseller, implementation, and regional charges are excluded?
8. What happens to unused commitment and usage above commitment?
9. Which products or features differ between AP1 and AP2?
10. What export, rehydration, and termination charges apply?

Before accepting a Guance quote, ask:

1. Does the Hong Kong & Global public rate apply to AP1 Singapore in the order form?
2. Is log billing based on default billed entries or enabled ingest traffic?
3. How are large events, multiple indexes, events, and synthetic data counted?
4. Does “GB” mean decimal GB or GiB in the contract?
5. Which forwarding, scanning, pipeline, trigger, replay, network, and support charges apply?
6. Which Datadog assets require manual recreation?
7. What billable quantities did the dual-write POC produce?
8. Which data, backup, support, DPA, SLA, and exit terms are binding?

Official sources

• Datadog: AP1 detailed pricing, default detailed pricing, Sites, billing, product allotments, container billing, APM billing, custom metrics, Metric Name Pricing, log indexes, OpenTelemetry compatibility, and support plans.
• Guance: Commercial Plan pricing details, billing logic, commercial sites, and OpenTelemetry integration.
• OpenTelemetry: Collector documentation.

For product-selection context rather than pricing formulas, see what to compare when choosing a Datadog alternative in Singapore.