Pricing
我们把 50 台数据库的 Datadog DBM 账单加了一遍,这就是结果。
2026 年 50 台 Postgres + 12 台 MySQL + 8 台 Mongo 在 Datadog DBM 实际花费的逐行明细,以及不换工具也能降本的方法。
Datadog DBM is genuinely a very good product. It’s also famous, in 2026, for the price tag at scale. We added it up for a hypothetical mid-market SaaS — 50 Postgres + 12 MySQL + 8 Mongo databases across 30 hosts — using public list pricing.
The line items
Hosts (30 × $23/host/mo · APM/Infra) = $690 / mo
DBM hosts (30 × $70/host/mo) = $2,100 / mo
DBM database instances (70 × $35/inst/mo) = $2,450 / mo
Log management (estimated, 50GB/mo) = $250 / mo
----------
$5,490 / mo ($65,880 / yr)That’s before custom metrics overage, before retention upgrades, and before any of the SaaS-only features your CISO doesn’t love. In practice the bill is 30–80% higher than the line items above.
What you can do without switching tools
- Drop DBM hosts that don’t actually run a DB process.
- Tag “dev” instances and exclude from DBM scope.
- Negotiate the per-instance fee at renewal — it’s the most negotiable line.
- Don’t pay for log retention longer than 7 days for DB logs.
- Move collection off Datadog APM to your own pipeline — DBM’s value is the agent + UI, not the storage.
What you can do by switching tools
Obsfly comes in at roughly 1/3 of that bill on the same fleet, with BYOC available for the regulated workloads, and AI features that aren’t generic-purpose Bits. Full comparison: /datadog-dbm-alternative.
For BYOC specifically — the unlock for regulated SaaS — read Why regulated SaaS can’t use Datadog DBM.
Do these numbers reflect real customer bills?+
What's the cheapest line to cut first?+
Keep reading
BYOC
Why regulated SaaS can't use Datadog DBM — and the BYOC fix
Walking through the architecture of a BYOC observability deployment: where data lives, what crosses the boundary, and how to satisfy SOC2 / HIPAA / GDPR without giving up the UX.
MySQL
MySQL Performance Schema vs sys schema: a 2026 monitoring guide
Performance Schema is unreadable. sys schema is friendly but lossy. Here's exactly which to use for which production question, with the eight queries every MySQL DBA should know by heart.