Datadog Pricing in Korea: AP1 Costs, Hosting, and Korean Support

For a Korean team, I would settle the hosting requirement before comparing Datadog pricing. Datadog’s public site list has AP1 in Japan and AP2 in Australia, with no Korea site listed. If the service must run in Korea, an AP1 cost estimate does not solve that requirement. If overseas SaaS is acceptable, AP1 provides a documented USD benchmark, followed by the terms of the actual Korean customer contract.

The next distinction is operational. Korean-language support has published hours; it is not the same as round-the-clock Korean incident response. These two decisions—where the service runs and when the team can get help—can matter more than a small difference in host prices.

Guance Editorial Team · 27 October 2026. Guance publishes this article and is included in the log-cost example. The analysis uses official documents and reproducible arithmetic, without customer contracts or production benchmark results.

Hosting and Korean support come before the rate card

A Korean-language pricing page selects the language, not the hosting region. The AP1-specific URL fixes the reference to Japan; the Sites list identifies each site’s location. Datadog sites are independent and can differ in products and endpoints. AP1 is not Korean data residency, and its list price is not an AP2 or negotiated Korean quote.

Datadog documents Korean support on weekdays from 09:00–17:00 KST, excluding local holidays. Korean chat is available on business days from 10:00–11:30 and 13:00–16:00 KST; English support remains available when the preferred language is not. An on-call rota that depends on Korean help overnight needs its escalation arrangements agreed separately. Korean support

Guance’s commercial site list includes AP1 on AWS Singapore and AP2 on Alibaba Cloud Singapore, but no Korea or Seoul SaaS site. Its public ticket service describes 5×8 support, not a guaranteed Korean-language response. Where hosting in Korea is mandatory, Guance’s Deployment Plan is a separate option on customer infrastructure or private cloud. That changes both the quote and who operates the system; the SaaS rates below do not price that deployment.

AP1 rates and the APM purchase model

The table uses Datadog’s AP1 Japan public list, checked on 27 October 2026, in USD. Annual rates depend on the relevant commitment; monthly and on-demand columns describe different purchasing terms. Included quantities, negotiated rates, unused commitments and overage belong in the account’s calculation. Keep the published precision until rounding the final subtotal.

The APM rates in this table are for purchasing APM with Infrastructure Monitoring. That model requires Pro or Enterprise Infrastructure on the APM hosts. Standalone APM is also available: the AP1 FAQ lists APM at US$45, APM Pro at US$51.25 and APM Enterprise at US$58.75 per host/month, with annual billing and on-demand availability. Comparing the attached APM rate with a standalone quote leaves out a material part of the purchase.

Apply the contract to the quantities the account actually bills

A Korean invoice needs its billing currency, exchange-rate date, VAT, reseller terms and support scope. Converting a USD list price at an arbitrary exchange rate would obscure those terms, so the example stays in USD. Annual commitment, unused spend, included quantities and overage remain separate parts of the calculation. Datadog billing

Start the product calculation with hourly billed hosts and excess containers. Pro’s published host allowances include 100 Custom Metrics, 100 Ingested Custom Metrics, five containers and 500 Custom Events, with meter-specific aggregation. Base APM adds 150 GB ingested spans and one million indexed spans per host/month with 15-day default retention; above allowance, AP1 ingestion is US$0.125/GB and annual indexed spans cost US$1.5875, US$2.125 or US$3.125 per million at 7, 15 or 30 days. Allotments, APM billing

Tag-value combinations determine series under cardinality-based custom-metric pricing. Metrics without Limits™ configuration makes ingestion and indexed quantities relevant; unconfigured metrics incur indexed charges only. A Metric Name Pricing contract uses names and data points instead. Those are different calculations, even if the same engineering team calls all of them “custom metrics.” Custom Metrics, Metric Name Pricing

RUM and replay use sessions, while API and browser tests use their own execution meters. Profiling, database, network, security and support costs also remain outside the log example. OpenTelemetry changes collection options, not these backend meters.

Log cost follows the events you keep searchable

Datadog charges for uncompressed log ingestion and for events retained in the selected index. An exclusion filter reduces indexed events; it does not undo ingestion already performed. That makes the indexing ratio a useful cost lever when only a fraction of records needs Standard indexed search. Flex Logs, archives and rehydration provide other arrangements with their own charges. Log indexes

Guance’s Commercial Plan uses a different unit. Its Hong Kong & Global public rate for 30-day retention is US$0.60 per million new billed log entries per day under default data-count billing. Billing logic includes large-entry splitting: the documented thresholds are 10 KB for ES storage and 2 KB for SLS. Custom indexes are counted separately; events and self-built synthetic data can also enter this billing item. The source event count is therefore only a starting point.

Consider a deliberately narrow, steady 30-day example: 1 decimal GB and one million events each day, all indexed in Datadog Standard for 30 days, with every event below both Guance splitting thresholds. Use AP1 annual list rates and Guance’s Hong Kong & Global default data-count rate. Exclude discounts, commitments, support, tax, reseller and currency effects, other products, archives, rehydration, forwarding, pipelines, scans, export, migration and parallel running. This is a rate calculation, not a production test or a feature-equivalence result.

The inputs can be changed independently:

D = daily uncompressed GB × 30 × 0.125
  + daily indexed events in millions × 30 × 3.125
G = daily billed entries in millions × 30 × 0.60
Difference (%) = (D - G) / D × 100

D = 3.75 + 93.75 = US$97.50
G = US$18.00
Difference ≈ 81.5%

The 81.5% difference belongs to this log-only scenario. An average event size of 1 decimal KB does not guarantee that every event is below a splitting threshold; the individual size distribution still matters.

A lower indexing ratio can reverse the result

Keep the same source volume and let Guance count all one million daily entries. Only change the share retained in Datadog’s Standard index:

Percentages use the unrounded amounts. At 34.4% indexing, Datadog’s US$36 subtotal is twice Guance’s US$18. At 10%, Datadog is lower. The latter retains only a tenth of the source events in the modeled Standard index, so the searchable scope differs. A useful decision starts with the records the team needs to retrieve, then prices that scope.

Guance also publishes US$0.17 per GB of daily original write traffic at 30-day retention for Hong Kong & Global. This alternative requires account-manager activation. It replaces default entry billing for standard log storage rather than being added to it. Its availability, GB definition and applicable site rate need to be confirmed in the order before using it in a budget.

A lower SaaS subtotal is useful only for a deployment you can use

I would keep Datadog where the existing investigation workflow, support arrangement and committed spend already serve the team well, and first reduce unnecessary indexing or metric cardinality. Replacing a platform to save a small recurring amount can cost more once dashboards, alerts, historical access and parallel running are included.

Guance becomes a useful alternative when its log billing matches the required searchable scope and its proposed hosting and service terms fit the Korean operation. For SaaS, confirm whether the Hong Kong & Global rate applies to the selected site. For a Korean deployment, obtain a deployment quote that includes infrastructure and operating responsibility. Neither route should inherit the other’s price.

Production data location also leaves backup, disaster recovery, support access, subprocessors, export and deletion to be addressed. Keep those obligations alongside the price in the order. Broader product trade-offs are covered in the Korea Datadog alternatives guide; a rate-card difference alone is not a reason to replace a working system.