The FinOps Foundation, a part of the Linux Foundation's nonprofit technology consortium focused on advancing the people and practice of FinOps, announced the launch of FOCUS 1.3 (FinOps Open Cost and Usage Specification) adding solutions to three persistent problems: splitting shared resource costs, tracking contract commitments accurately, and verifying data freshness.
With FOCUS 1.3 – the fifth major release since the FOCUS specification launched in 2023 – the specification includes transparency for provider-defined services that allocate shared costs for containers and databases, introduces a new external dataset for contract or negotiated agreements, and includes metadata signals for dataset completeness and recency – all of which allow practitioners to more accurately and securely manage their multi-provider reporting workflows.
All major clouds have been contributors to the ongoing FOCUS 1.3 specification development. Further, FOCUS is already supported by cloud and technology providers worldwide including Alibaba, AWS, Databricks, Google Cloud, Grafana, Huawei, Microsoft, Oracle Cloud Infrastructure, OVH Cloud, and Tencent. In addition, many enterprises are using FOCUS language in their internal reporting systems, and generating FOCUS datasets for their data center and private cloud spending.
The overarching aim of FOCUS is to reduce complexity across cloud, SaaS, data center, and other technology vendors to reduce complexity for FinOps practitioners who are managing the value of these technologies. The list of FOCUS dataset generators originally included major cloud providers, and now has grown to encompass SaaS, software, data and platform providers.
"With over a dozen providers already supporting FOCUS and AWS announcing generally available FOCUS 1.2 support, FOCUS is hitting yet another big milestone in terms of a rapidly maturing data structure with the new 1.3 release. The common definitions that FOCUS provides for billing data generators enable FinOps practitioners to spend less time on data normalization and more time finding valuable business insights," said J.R. Storment, Executive Director of the FinOps Foundation. "FOCUS 1.3 goes deeper to unpack shared cost allocations, enables a broader swath of providers to support the specification, adds a new contract dataset that can be permissioned separately from cost and usage data, and helps shine light on the freshness of data."
New enhancements include:
- Split Shared Costs and Understanding of Data Generators' Allocation Method. Today, shared resources, such as Kubernetes pods and database instances, force practitioners to build custom allocation logic or accept non-granular cost allocations. That changes with FOCUS 1.3. New allocation-specific columns let data generators expose how they split costs across workloads. Practitioners see the methodology—not just the result. This will especially benefit platform engineering teams, FinOps analysts allocating shared infrastructure, and DevOps leaders managing multi-tenant clusters.
- Track Contract Commitments in a Dedicated Dataset. Practitioners can make more informed decisions if they understand how much their existing cost and usage is applicable to terms spelled out in service provider contracts. But those details are difficult to tie back to data presented in cost and usage datasets. In FOCUS 1.3, a new, "Contract Commitment" dataset isolates contract terms, including such things as start/end dates, remaining units, and descriptions, from cost/usage rows. One query shows all active commitments. This enhancement marks the first instance of extending FOCUS language to an adjacent dataset, giving practitioners a structured method to understand contract commitments.
- Verify Data Recency and Completeness. Processing stale or incomplete cost and usage data can break automated reconciliation workflows. Practitioners might only discover missing rows after month-end close. With FOCUS 1.3, providers must timestamp datasets and flag completeness status so users know if data is subject to revision. This will result in less processing of incomplete data and more confidence in making decisions knowing that data is complete and relevant.
- Service Provider and Host Provider Columns. Definitions will be more delineated between service and host providers so that practitioners will more easily see who they should engage for support and billing inquiries.
In addition to the launch of the FOCUS 1.3 specification, the FinOps Foundation is announcing a forthcoming update to the FinOps Certified FOCUS Analyst course to include features from FOCUS 1.2. The updated course will allow for more detailed, unified reporting across cloud, SaaS, and PaaS services.
The FOCUS project always welcomes feature requests for future releases and contributors The FOCUS 1.4 specification is already under development, given a backlog of member feedback and requests. Future FOCUS versions will deepen support for cloud and SaaS billing while expanding to additional spending scopes, including data center and AI - join the FOCUS Project to help develop the next release.
The Latest
I've spent a lot of time in the channel, and one thing I keep coming back to is this: a partner program is only as good as what it looks like in the field. Many programs look great on paper, but when a partner is in front of a customer navigating a complex hybrid environment or trying to make the case for AI-powered observability, the gap between what a vendor promises and what it actually delivers becomes very clear, very fast ...
Enterprises today operate in a real-time environment where uninterrupted access to trusted data has become a baseline expectation for users, applications and automated systems. Traditional DataOps models, built on manual effort and human triage, cannot keep pace with this always active demand. AI agents are emerging as the operational backbone, ensuring consistent data availability, reinforcing trustworthiness and enabling a level of scale that manual processes cannot achieve ...
For decades, trust in the digital workplace rested on familiar signals. We trusted faces on video calls, voices on the phone, and emails that appeared to come from people we knew. These cues felt human and intuitive. They anchored how decisions were made, approvals were granted, and access was authorized. AI-powered deepfakes have quietly broken that model ...
Cloud migration was supposed to be a one-way door. For most enterprises, it turns out it isn't. Cloud data repatriation is a real and growing trend. A new survey ... finds that 89% of organizations plan to expand their on-premises infrastructure footprint over the next two years — and 75% have already moved at least some workloads back from public cloud in the past 24 months. The findings point to a broad rethinking of where data belongs ...
Over the past few years, large language models (LLMs) have revolutionized the software industry. Given their ability to excel at multi-step reasoning, LLMs have helped enterprises streamline workflows and adapt to the unknown. However, employing such models comes with sky-high costs, latency issues, and limited flexibility. In the realm of IT operations, it is generally wiser to employ smaller, domain-specific models instead ...
For years, DevOps teams operated under a simple assumption: collect enough telemetry, and you can find and fix any problem. That assumption is breaking down. Modern enterprises now operate across microservices, hybrid cloud environments, APIs, Kubernetes, and highly automated delivery pipelines. Releases happen continuously, dependencies shift constantly, and failures spread faster than teams can diagnose them ...
New Relic surveyed IT and engineering leaders from the media and entertainment (M&E) sector to understand what's working — and where challenges persist with their observability practices. The findings reveal how M&E organizations are navigating rising platform complexity, audience expectations, and AI-driven change. Below are five takeaways that stand out ...
Let me start with something I've seen play out more times than I can count. A team hits a wall with the cloud. Costs creep up, then spike. Performance starts to feel inconsistent. Someone in finance asks a simple question like "why did this double?" and nobody has a clean answer ... Maybe this isn't the right place for everything. That realization feels like a breakthrough, like you've identified the problem. In reality, you've just identified the starting line ...
In MEAN TIME TO INSIGHT Episode 24, Shamus McGillicuddy, VP of Research, Network Infrastructure and Operations, at EMA discusses network observability tool sprawl ...
In cloud-native systems, scaling is often as simple as moving a slider. For on-premise databases, the stakes are different. Over-provisioning hardware is expensive. Under-provisioning leads to performance bottlenecks that are difficult to fix once the equipment is in the rack ...