惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

酷 壳 – CoolShell
酷 壳 – CoolShell
H
Hacker News: Front Page
P
Palo Alto Networks Blog
T
ThreatConnect
Apple Machine Learning Research
Apple Machine Learning Research
博客园_首页
T
True Tiger Recordings
P
Privacy & Cybersecurity Law Blog
B
Blog
IT之家
IT之家
Last Week in AI
Last Week in AI
F
Full Disclosure
Hacker News: Ask HN
Hacker News: Ask HN
C
Comments on: Blog
Microsoft Azure Blog
Microsoft Azure Blog
C
Cybersecurity and Infrastructure Security Agency CISA
Microsoft Security Blog
Microsoft Security Blog
博客园 - 【当耐特】
N
News and Events Feed by Topic
NISL@THU
NISL@THU
腾讯CDC
雷峰网
雷峰网
Security Latest
Security Latest
李成银的技术随笔
M
Microsoft Research Blog - Microsoft Research
L
LangChain Blog
L
Lohrmann on Cybersecurity
cs.CL updates on arXiv.org
cs.CL updates on arXiv.org
C
Check Point Blog
Y
Y Combinator Blog
Recent Announcements
Recent Announcements
博客园 - Franky
N
News | PayPal Newsroom
V
V2EX
A
About on SuperTechFans
The Register - Security
The Register - Security
月光博客
月光博客
奇客Solidot–传递最新科技情报
奇客Solidot–传递最新科技情报
Google Online Security Blog
Google Online Security Blog
MyScale Blog
MyScale Blog
Cisco Talos Blog
Cisco Talos Blog
Vercel News
Vercel News
WordPress大学
WordPress大学
C
Cyber Attacks, Cyber Crime and Cyber Security
The Hacker News
The Hacker News
IntelliJ IDEA : IntelliJ IDEA – the Leading IDE for Professional Development in Java and Kotlin | The JetBrains Blog
IntelliJ IDEA : IntelliJ IDEA – the Leading IDE for Professional Development in Java and Kotlin | The JetBrains Blog
爱范儿
爱范儿
A
Arctic Wolf
L
LINUX DO - 最新话题
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More

Datadog | The Monitor blog

Reduce CVE noise with OpenVEX assessments in Datadog How we made a SQL query optimization agent 59% more accurate using autoresearch and LLM Observability How to audit and clean up monitors effectively Diagnose slow PostgreSQL queries faster with explain plan correlation Explore Datadog metrics with Natural Language Queries Toto 2.0: Time series forecasting enters the scaling era Simplify micro-frontend observability with Datadog RUM Attribute AI costs across providers with Datadog Cloud Cost Management Diagnose and resolve database performance issues faster with Database Investigator Datadog for Government achieves FedRAMP® High certification Analyze cloud costs with flexible spreadsheets in Datadog Sheets Inside Datadog’s AI Research Lab: Meet two PhD candidates behind Toto Connect triage and investigation in a single workflow with Datadog Cloud SIEM This Month in Datadog - April 2026 Monitor and optimize Supabase query performance with Datadog Database Monitoring Add dynamically updating context to logs with Reference Tables and Observability Pipelines Introducing ARFBench: A time series question-answering benchmark based on real incidents The product signal latency gap slowing your growth Test network paths with TCP, UDP, and ICMP in Datadog Turn developer feedback into operational insight with Datadog Forms and Sheets How to investigate cloud credential compromise with Bits AI Security Analyst Evaluate, optimize, and secure your Google Cloud AI stack with Datadog Bringing observability data hosting to the UK on AWS Identify and fix code issues faster with Datadog’s Azure DevOps Source Code integration Steganography at scale: Embedding share URLs in Datadog widget screenshots Every team should be A/B testing Centralize observability management with Datadog Governance Console Spotting CI/CD misconfigurations before the bots do: Securing GitHub Actions with Datadog IaC Security Route OTel data from AI apps to ClickHouse and Datadog using Observability Pipelines Manage service tracing across hosts with Single Step Instrumentation rules Offline evaluation for AI agents: Best practices Detect runtime threats in Python Lambda functions with Datadog AAP Introducing our open source AI-native SAST Instrument and monitor Boomi integration flows with OpenTelemetry and Datadog Not all index scans are equal: How we cut query latency by over 99% Platform engineering metrics: What to measure and what to ignore Integrate Recorded Future threat intelligence with Datadog Cloud SIEM CI/CD security: threat modeling using a MITRE-style threat matrix CI/CD security: How to secure your GitHub ecosystem Ingress NGINX is EOL: A practical guide for migrating to Kubernetes Gateway API How we built a real-world evaluation platform for autonomous SRE agents at scale Operating agentic AI with Amazon Bedrock AgentCore and Datadog LLM Observability: Lessons from NTT DATA Introducing the Datadog Code Security MCP Capture and analyze custom heatmaps in Session Replay Understand session replays faster with AI summaries and smart chapters Monitor ClickHouse query performance with Datadog Database Monitoring How we designed empathetic alert sounds for on-call engineers Search and act across Datadog to resolve issues faster with Bits Assistant Measure the business impact of every product change with Datadog Experiments Analyzing round trip query latency Configuring JavaScript caches for better performance Introducing Bits AI Dev Agent for Code Security Datadog achieves ISO 42001 certification for responsible AI Monitor Nutanix clusters, hosts, and VMs with Datadog Monitor Juniper Mist in Datadog A new Host Map for modern infrastructure When upserts don't update but still write: Debugging Postgres performance at scale Annotate traces to improve LLM quality with Datadog LLM Observability What's new in Cloud SIEM: AI-powered investigations, enhanced threat intelligence, and scalable security operations Explore Kubernetes with native OpenTelemetry data Monitor Oracle Fusion Cloud Applications with Datadog Announcing the Datadog Terraform provider v4.0.0 Scaling Kubernetes workloads on custom metrics How to design cloud environments for AI-powered threat analysis Monitor Aruba Central in Datadog How we centralize and remediate risks with Datadog Case Management Accelerate incident response with Datadog and ServiceNow Monitor your application and network load balancer logs Understanding Karpenter architecture for Kubernetes autoscaling Tools for collecting metrics and logs from Karpenter Monitor Karpenter with Datadog What your product data is actually saying Key metrics for monitoring Karpenter Securing Datadog's platform in the AI age: The role of observability data Closing the verification loop: Observability-driven harnesses for building with agents When an AI agent came knocking: Catching malicious contributions in Datadog’s open source repos Closing the verification loop, Part 2: Fully autonomous optimization Four ways engineering teams use the Datadog MCP Server to power AI agents Approaching your observability migration with the right mindset Meet the new Bits AI SRE: Deeper reasoning, twice as fast Designing MCP tools for agents: Lessons from building Datadog's MCP server Key learnings from the 2026 State of DevSecOps study Use plain English to query your multi-cloud infrastructure in Resource Catalog Simplifying troubleshooting across the user journey with Datadog Synthetic Monitoring Protect your OCI resources with Datadog Cloud Security This Month in Datadog - February 2026 Fine-tune Toto for turbocharged forecasts Amazon EC2 security: How misconfigured and public AMIs expand your cloud attack surface Enable end-to-end visibility into your Java apps with a single command Measure and improve mobile app startup performance with Datadog RUM Evaluating our AI Guard application to improve quality and control cost Identify untested code across every level of your codebase Make use of guardrail metrics and stop babysitting your releases Monitor Versa Networks SD-WAN performance in Datadog How we reduced the size of our Agent Go binaries by up to 77% Improve performance and reliability with APM Recommendations Remediate transitive vulnerabilities faster with Datadog Software Composition Analysis Generate audit-ready vulnerability and compliance reports with Datadog Sheets Monitor Fortinet FortiManager performance in Datadog Improve test coverage across codebases with Datadog Code Coverage
A guide to cloud unit economics
2025-08-06 · via Datadog | The Monitor blog

As you analyze your organization’s cloud spending, you’ll often find that stakeholders have different perceptions of what that spending brings you. This is especially true when overall costs are rising and it’s hard to distinguish waste from valuable investments in growth. But when finance, engineering, and product teams can all connect cloud spending to specific business outcomes, you gain the ability to make data-driven decisions about how to maximize the value of that spending.

Unit economics connects each dollar you spend to the value it brings to your business. By connecting cloud spending to customer activity such as signups, checkouts, and requests, unit economics shows you how efficiently your organization uses cloud resources, from core infrastructure to related software and SaaS subscriptions.

In this post, we’ll explain how to identify useful unit economic metrics and how to apply them to:

But first, we’ll take a closer look at what cloud unit economics is and how it can help you.

What is unit economics?

Effective cloud spending enables your organization to attain specific objectives that bring you value, such as creating a user account or completing an ecommerce checkout. You can understand the value you get for your cloud spending by analyzing costs through the lens of unit economics. Unlike measuring your overall cloud spending, measuring unit costs—how much you spend to attain a discrete business outcome—can help you understand the actual cost of delivering on your core objectives. Unit costs illustrate the value you get from the cloud.

Understanding your unit costs is critical in effectively optimizing your spending. Your optimization efforts should aim not just to decrease your cloud spending, but instead to increase the value of what you get. To do this, you need to minimize your unit costs by making strategic changes in how you use your cloud services. Driving down unit costs increases the value you get from each dollar you spend in the cloud.

For example, if your revenue comes from memberships, your unit cost might be dollars per member—the sum of the cloud costs associated with creating and maintaining each membership. A lower unit cost brings you more members—and more revenue—per dollar of cloud spending. You can decrease your unit cost by moving stale member data to cheaper storage, shifting batch processing jobs to spot compute instances, or taking advantage of rate optimizations.

In addition to informing your cost-optimization efforts, tracking unit costs can provide important context that gives you a more complete understanding of your cloud spending. For example, if your overall cloud costs increase, unit costs can show you whether it’s due to a higher cost per membership or simply due to more members.

If you’re able to decrease your unit costs even while your overall spending rises, you know that you’re gaining cost efficiency and generating more value for each dollar you spend in the cloud. In this case, the rise in cloud costs is caused by greater volume, and that additional spending is a way of accelerating your organization’s growth and capturing more revenue. Rising cloud costs might look bad, but by tracking unit costs, you can expose the value of that spending.

In the next section, we’ll look at how to identify unit metrics that are meaningful for your organization. Later in this post, we’ll show you how you can apply unit economics to improve visibility and collaboration, guide cost optimization efforts, and maximize revenue.

Define unit metrics that capture value

Unit economics helps you measure the cost of a specific outcome, but it doesn’t provide any standard metrics. This means that you need to decide what’s useful for your organization to measure. First, you need to recognize the business outcomes that bring you value. For example, a team that operates an internal developer portal attains value each time a product team deploys a change, but a non-profit organization gains value from each donation.

After you’ve identified your organization’s valuable activities (your unit metrics), you need to calculate the cloud spending that corresponds with each one (your unit costs). For example, to calculate the unit cost of a donation, you might include the cloud costs of the CDN that hosts the form, the serverless functions that process the submission, the data storage associated with creating the donor record, and the payment processing fees.

The following screenshot shows a service’s daily AWS costs per checkout. The stacked bar chart uses different colors to show the cost attributable to each of the AWS products that power the service, such as Amazon EC2, Amazon S3, and Amazon EKS.

Screenshot of daily cost data visualized as a bar graph, highlighting cloud service expenses per checkout from July to August.

Which cloud costs you factor into your unit costs should be defined by your FinOps team along with your internal users—the engineering teams whose work produces these metrics. Engineering teams can draw on their knowledge of the meaning and context of their services’ metrics to guide their cost-optimization efforts.

As your capability for unit economics matures, you might aim to understand your unit costs at an even more granular level. To do this, you can expand your definition of cost to include spending from across various FinOps scopes. Including related costs—such as the CRM software and email services you use to communicate with donors—can give you more accurate unit costs, but comes with additional complexity.

You can even calculate unit costs that differentiate between various levels of service to understand the amount of revenue generated by each of your activities. For example, if you offer multiple tiers of service, you should try to identify your per-user cost in each tier. This can inform your product pricing decisions and help you maximize your revenue.

Putting unit economics into practice

In this section, we’ll look at some practical examples of applied unit economics. We’ll show you how you can use unit economics to foster shared understanding of your cloud costs, create KPIs, more accurately forecast your cloud costs, and determine optimal pricing of your organization’s offerings.

Use a common language to gain a shared understanding

Without unit economics, finance, engineering, and product tend to focus on cloud costs from different angles and using different terminology. Finance teams might talk about costs in terms of variance against budget. Engineering teams might talk about technical drivers of cost, such as CPU utilization. Product teams might discuss the bottom-line cost of adding a new feature. When these stakeholders communicate about costs, these different languages can lead to inefficiency and misunderstandings.

But all of these stakeholders are committed to the outcomes that are valuable to your business. When you adopt unit economics, they can communicate and collaborate more effectively by focusing on metrics that matter to everyone. With this shared understanding, stakeholders can work together to analyze business performance and make data-driven decisions that ensure the effectiveness of your cloud investments.

Define KPIs to guide optimization and enable cost ownership

Selecting the right unit metrics and defining their costs helps you understand your cloud spending as a function of your business activity and an opportunity for growth. To guide you in maximizing that growth, you can create KPIs that give engineering teams the necessary visibility to own and continually optimize costs.

Screenshot of FinOps KPIs dashboard showing cost per core per hour, storage cost per byte, cost per checkout. Also shows graphs depicting trends for storage cost per byte, checkout costs, and number of checkouts over the past week.

To create an effective KPI, use your unit cost’s recent history as a baseline, then set a cost-optimization target. For example, the team that owns a service might determine that they can optimize its use of cloud services to lower the unit cost by 20% without compromising its performance. This KPI is critical because it enables the team to measure the value of their work. Even if the service’s total cost increases due to higher traffic, a decreasing unit cost demonstrates that the team is operating an efficient service and that the increased spending is generating value, not waste. They can track the status of the KPI by using monitors and dashboards to stay informed about their progress and find out quickly about any regressions.

Forecast cloud costs more accurately

Your total spending is a function of your unit cost and the number of units you produce, whether that’s responding to an API request, processing a query, or storing a byte of data. By shifting your focus from your overall cloud spending to your cost per unit of value, unit economics enables you to project future costs based on your expectations of growth. Unit economics allows you to create more accurate forecasts by projecting costs based on expected business volume, while also factoring in planned efficiency improvements.

Screenshot of a line graph titled 'Cost per checkout' showing historical data from June through July, followed by a forecast beginning in August, predicting checkout costs for the next 12 weeks.

Strategic decisions that are informed by unit costs—rather than bluntly derived from aggregated cloud cost data—can help your organization identify and lean in to opportunities to maximize revenue. Unit costs show you the margins of each of your offerings so you can plan to grow your strongest products to realize the greatest gains. At the same time, this information guides you to hold back on those offerings with small or negative margins until you can cost-optimize them enough to generate meaningful value.

Determine product pricing with unit economics

Effectively pricing a digital product balances capturing the greatest gains with staying competitive in the market. Your unit cost sets a minimum price for your offerings, which enables you to use a data-driven pricing strategy to ensure that you’re not losing money on each transaction, signup, or other activity that is meant to generate value. It can also show you whether you can effectively contend with competitors offering similar services.

If your pricing strategy includes multiple tiers of service, your unit costs can give you an empirical understanding of your per-tier revenue. Your unit costs will show if your premium tier is actually your most profitable, or if you need to optimize its costs to build a bigger margin. If you’re also operating a free tier, you’re foregoing gains on each customer in order to demonstrate the value of your product. You can multiply your unit cost by your free-tier offering—e.g., 100 queries per day—to understand how much it costs you to serve those users and then closely track the impact of that investment.

Measure and maximize the business value of your cloud spending

By gaining visibility into your unit costs, you can better understand your current and future cloud spending and make data-driven decisions to guide your cost optimization and product pricing. Unit economics fosters collaboration among stakeholders and provides an organization-wide shared understanding of the value you get from each dollar you spend in the cloud. Most importantly, it gives you the confidence to invest in growth by proving that rising overall costs are not necessarily a sign of waste. Instead, they can be a direct reflection of increasing business value.

If you’re interested in learning more, see our blog posts about Datadog’s FinOps practice and how we’ve made some major cost optimizations. If you haven’t yet started using Datadog, you can sign up for a 14-day free trial.