FinOps Framework Applied to Atlas

Parent: Atlas Pricing Programs, Cost Governance and TCO · Published reference · snapshot 2026-10-19 · skill mongodb-operations-expert/references/atlas-pricing-programs-cost-governance-and-tco.md · viability 3.80 / 5 (research)

↓ Facts as markdown all context files

The FinOps Foundation Framework 2025 adds Scopes (a segment of technology-related spending to which FinOps concepts are applied) and runs an iterative Inform, Optimize, Operate lifecycle over them; MongoDB publishes no official mapping of Atlas to that lifecycle, so any mapping is inference. Atlas supplies the Inform-phase data through Cost Explorer (grouping by organization, project, cluster and service), resource tags on invoice line items, cross-organization billing, and FOCUS 1.3 reports from the Invoices page or the FOCUS Data API, while third-party tools such as DoiT ingest the same data; a known gap is that tags are resolved at export time, so deleted clusters appear untagged. The pack draws on 6 sources (FinOps Foundation, Atlas billing docs, MongoDB blog, DoiT, MongoDB feedback portal) and covers definitions, structure, mechanism, how-to, parameters, measures, problems, comparisons and history, with 1 flagged disagreement about a workaround.

These notes link each claim to its source. Some citations identify archived research reports that are no longer hosted on this site. A published reference means the content is available; it does not certify independent review or accuracy.Read the editorial policy and follow the sources before relying on a claim.

Definitions

It’s important to note that Scopes are not simply a data source or type of infrastructure. They are a segment of technology-related spending to which the FinOps practitioners apply FinOps concepts. In one Scope, the business strategy may require extra focus on Workload Optimization or Rate Optimization, and in another Scope, the business may require extra priority on Allocation, or in another on Forecasting accuracy. [source]
FinOps Framework 2025 was approved in March 2025. It adds Scopes, defined as a segment of technology-related spending to which practitioners apply FinOps concepts. The initial Scopes are Public Cloud, SaaS and Data Center. Scopes are not mutually exclusive. [source]
A FinOps Scope is defined as a segment of technology-related spending to which FinOps Practitioners apply FinOps concepts. [source]
A FinOps Capability describes how to achieve a specific outcome (i.e., Domain), such as Understanding Costs, Optimizing Usage, or Quantifying Business Value. By comparison, a FinOps Scope represents a collection of Capabilities for a specific context – like public cloud, or AI, or licenses. A FinOps Scope for Licensing, for example, involves multiple Capabilities and may span across multiple types of infrastructure. [source]
The FinOps Open Cost and Usage Specification (FOCUS) establishes uniform requirements for technology billing datasets. MongoDB Atlas provides billing cost and usage data in the FOCUS 1.3 format. You can generate a FOCUS report from the Invoices page in the Atlas console or with the FOCUS Data API. [source]
The FinOps Framework offers building blocks for a successful FinOps practice. It encompasses principles, personas, measures of success, maturity characteristics, and functional activities in a common language that reflect how successful Practitioners drive value from technology spend. [source]
Through our work with the community, TAC, and Working Groups, the initial FinOps Scopes identified were Public Cloud, SaaS, and Data Center. Public Cloud remains the primary Scope, as the practice of FinOps was born to address the cost management challenges that arose with the introduction of cloud. [source]
FinOps Domains are the fundamental business outcomes organizations should achieve from a FinOps practice. [source]
FinOps Capabilities are the core practices, processes, and tools that organizations use to effectively manage and optimize their cloud and technology operations. [source]
The FOCUS Data API provides programmatic access to your FOCUS-formatted cost and usage data. [source]

Structure and components

Atlas provides billing data in FOCUS 1.3 format. The FinOps Open Cost and Usage Specification gives a vendor-neutral schema. Reports come from the Invoices page (CSV FOCUS Cost & Usage Report) or from the FOCUS Data API's asynchronous request and retrieve endpoints. Columns include BilledCost, EffectiveCost in billing currency, and SubAccountName in place of groupName. [source]
Atlas Cost Explorer filters and groups usage by organization, project, cluster and service. It shows six months of usage and up to 18 months of billing data, and spans linked organizations under cross-organizational billing. This is the native Inform-phase visibility layer. [source]
Third-party FinOps platforms ingest Atlas billing directly. DoiT's MongoDB Intelligence module, announced 2025-11-07, breaks spend down by organization, project and SKU, with trend tracking and an AI assistant. [source]
On the right, you’ll find an Agentic FinOps AI assistant. Ava isn’t just a chatbot; it’s a reasoning layer that interprets the same data visible on the dashboard. Ask questions like “Which projects or SKUs changed the most this month?” or “Where am I overspending on backups?”, and Ava will analyze cost trends, isolate anomalies, and suggest next best actions. [source]
The Billing Cost Explorer filters and groups usage data by organization, project, cluster, and service. Each filter contains a Usage chart with stacked columns representing the total cost incurred each month. Underneath, there is a Usage By Month table that displays the billing data shown in the chart. To learn more, see Billing Cost Explorer. [source]

How it works

The Framework lifecycle is iterative: Operate outputs inform changes to the Scope, Inform updates the Scope, Optimize sets refinements as targets, then the cycle repeats. The 2025 update dropped 'cloud' from domain and capability names, for example 'Optimize Usage and Cost'. [source]
Atlas resource tags (for example department, project or cost center) appear on invoice line items. The Return All Pending Invoices endpoint exposes them in results.lineItems.tags. MongoDB recommends feeding that data into external FinOps tools for chargeback, by environment, team or tag value. [source]
Scopes provide an implementation roadmap or practice profile for how FinOps achieves the business and technology goals defined by Leadership. A Scope is constantly evolving based on results and outcomes as Practitioners move through the iterative lifecycle of the Framework. Outputs from the Operate Phase inform changes to the Scope (Inform Phase), then further refinements are set as targets in the Optimize Phase, and the cycle repeats. These changes are constantly influenced by changing business needs to drive desired business value outputs, in addition to providing inputs for further strategy [source]
Atlas Well-Architected cost guidance maps to the Optimize phase: enable auto-scaling on the cluster tier to cut over-provisioning, and use tags plus programmatic billing pulls for allocation. MongoDB does not publish an explicit Inform/Optimize/Operate mapping, so this mapping is the researcher's inference. [source] — mapping to Optimize phase is the researcher's inference
The Framework is flexible and non-prescriptive. With components that FinOps Practitioners can select from, it enables organizations to start where the greatest need is, and evolve their FinOps practice in scale, scope, and maturity as business value warrants. [source]
With FinOps Scopes, Practitioners create the context that drives how to apply the FinOps Framework. Each Scope encompasses a segment of technology usage and cost to which Practitioners can apply FinOps concepts; This could be in a single type of infrastructure like Cloud, or across multiple types like SaaS, PaaS, Data Centers, or Private Cloud. [source]
Practitioners are also enabled to apply the Framework beyond infrastructure to other groupings of spend, like AI and Licensing costs, for example. Your organization’s technology strategy and business priorities will influence the number of FinOps Scopes that will be part of your practice.The graphic below illustrates the concept of FinOps Scopes by highlighting Data Center, Containers, and Licenses as three examples of Scopes in the era of Cloud+. [source]
This construct helps frame conversations and expectations about which Personas, Domains, and Capabilities apply for the Scope, so the FinOps practice can deliver business value based on business strategy and adjust the Scope profile to react to changes in strategy. [source]
FinOps Practitioners do not need to apply all Capabilities, but should assess their organization’s needs and prioritize improving Capabilities that will drive the most value. This flexible approach also applies to Cloud+ other technology costs; Different Scopes will require different Capabilities, and maturing each one to a different level depending on your organization’s needs. [source]
A single company might have multiple Scopes. In one company with a hub-and-spoke FinOps practice, each spoke may be managing different Scopes with different priorities, driven by each respective business unit’s strategy. This strategy gets to another critical thing to recognize with Scopes: that they change how the practice of FinOps itself is applied. [source]
FOCUS provides a common vocabulary and billing structure, which helps you understand, reconcile, and integrate your Atlas billing data with FinOps and cross-vendor cost-management tools. [source]
The updated definition means that Practitioners can define their own Scopes, and that those Scopes may sit across multiple types of technology spending, or multiple Scopes may be defined within a single provider. Practitioners have begun defining their own Scopes to manage things like, Private Cloud, Licensing, and AI costs in addition to Public Cloud spend. [source]
A Scope may turn on or off certain Capabilities due to relevance or prioritization, it may include or exclude a specific Persona from involvement, or it may change the thresholds for metrics associated with a Capability depending on the business strategy passed down from Leadership. [source]
The PDF and CSV usage summaries present your invoice in MongoDB-specific formats. The FOCUS cost and usage report presents the same billing period in the standardized FOCUS format. You can download all three from the Invoices page in the Atlas console. [source]
Analytics for organization-level costs, project distribution, and SKU analytics reveal patterns previously hidden in CSVs, helping FinOps and engineering teams align on the same data when evaluating scaling, tiering, or retention decisions. [source]
Requests generation of a billing report in the FOCUS standard format. Atlas generates the report asynchronously and returns a report ID that you use to poll for the report status. [source]
Returns the status and details of a FOCUS report that you requested. Poll this endpoint until state is SUCCEEDED or FAILED. [source]
Single-organization scope: Each request returns data for one organization. If you use cross-org billing, request one report for each invoiceId returned by the list endpoint. [source]
Atlas allows you to share a billing subscription across many organizations and to pay a single invoice for them. Enable cross-organization billing for easy visibility into Atlas spending for all of your organizations. [source]
After you configure a paying organization, you pay invoices for the paying organization that include a list of charges incurred for all linked organizations. To learn more, see Cross-Organization Billing. [source]
Leveraging tags within billing invoices empowers customers to categorize spending based on custom dimensions (such as cost center) and streamline financial reporting. [source]

Parameters and configuration

View costs in billing currency: Access BilledCost and EffectiveCost directly in billing currency, without manual conversion. [source]
Request a FOCUS Report requests generation of a FOCUS-formatted billing report. [source]
Retrieve a FOCUS Report returns the status of that report and, when the report is ready, the URL to download it. [source]
Tags will typically appear on Invoice line items within 48 hours of being added to the deployment. Also, tags will not appear on cluster related line items that are not associated with a tag and line items not billed at the cluster level are not eligible for tagging at this time. The example below shows an example CSV export for the fictitious project, Leafy. This organization has two tag keys (Environment and Cost-Center) associated with different clusters. Notice that the cluster named “Blue” does not have the Cost-Center tag applied, so those cells are blank. [source]
To view and download billing data, you must have the Organization Billing Admin, Organization Owner, or Organization Billing Viewer role. [source]
List Invoices for an Organization lists the available invoices for an organization. [source]
Retrieves a list of available invoice IDs. For Cross-Org Billing, this endpoint identifies invoices for all linked organizations. [source]
After you enable cross-organization billing, you can view linked invoices if you have the Organization Billing Admin role or the Organization Owner role for the paying organization. [source]

How-to and procedures

You can retrieve all your pending invoices with the Return All Pending Invoices for One Organization API endpoint. The endpoints response body contains the results.lineItems.tags field, which reflect the tags you applied to your resources (such as organizations and clusters). You can then feed this line-item-level billing data into external FinOps tools and reports track your Atlas spending by environment, team, or other tag values. [source]
You can download the FOCUS cost and usage report for an invoice from the Invoices page in the Atlas console. Select CSV FOCUS Cost & Usage Report when you choose the invoice format. [source]
You can apply resource tags in Atlas for precise cost allocation by categorizing resources according to departments, projects, or cost centers. You can also group and analyze tagged resources in financial reports, providing a clear and organized view of how various teams or projects contribute to overall cloud spending. To learn more, see Resource Tags. [source]
To view your billing data monthly, navigate to the Cost Explorer page. The Cost Explorer provides a granular view of cloud spending in chart and table form, allowing users to analyze costs by clusters, projects, or teams. Historical spending data and customizable filters help identify trends and inefficiencies, enabling better financial decision-making and resource optimization. You can view your usage over the past six months, and access your billing data up to the past 18 months. If your organization uses cross-organizational billing, you can view billing data across all linked organizations [source]
Customers can get started today by adding tags to new or existing deployments using the Atlas UI, Admin API, or CLI. Once added, the tag keys will appear as column headings in the billing invoice CSV export and as a field in the Invoices payload for the Admin API calls. [source]
Do not include any sensitive information such as Personally Identifiable Information (PII) or Protected Health Information (PHI) in resource tag keys or values. [source]
Implement a tag governance routine that regularly checks for untagged or improperly tagged deployments. [source]
Pull billing data programmatically to integrate with your FinOps tools for charge-back and accounting purposes within each department and application. [source]
The Atlas Administration API provides a RESTful interface that allows you to programmatically access your billing data for use with external tools and reports. Combine this feature with resource tags to easily categorize your Atlas spending. [source]
To view your billing data annually, navigate to the Billing Overview page. This page helps you to understand the costs incurred by your organization's Atlas usage by service, deployment, and project. Each category contains a Usage chart with stacked columns representing the total cost incurred each month. To learm more, see Year-to-Date Usage Chart. [source]
You can visualize your billing data in a MongoDB Charts billing dashboard to help you optimize your Atlas spending. Billing dashboards contain prebuilt charts that help you monitor your Atlas usage in an organization across different categories and periods of time, and MongoDB Charts integrates with Atlas to seamlessly ingest billing data. [source]
Define and communicate a strategy that enforces mandatory tags on all database deployments. We recommend you start with identifying the environment and the application/service/workload. [source]
Setting up MongoDB Intelligence takes only a few minutes — connect your Atlas organization, and Cloud Intelligence™ will automatically ingest cost and usage data. Follow the step-by-step guide in our Help Center article to enable the integration securely and start visualizing your MongoDB Atlas spend with zero manual exports. [source]
Use a standard naming convention - including spelling, case, and punctuation for all tags. [source]
Use namespaces or prefixes to easily identify tags owned by different business units. [source]

Measurements and reference values

The State of FinOps 2025 revealed that Scopes are not just affecting the type of spending being managed, but the profile of the FinOps practice itself. While Optimization was the top priority for Cloud, Optimization was not in the top 5 priorities for SaaS, AI, Licensing, or Data Centers. [source]
FOCUS 1.3 cost columns in the Atlas FOCUS Data API: BilledCost: The cost, in billing currency, charged during the current invoicing period. EffectiveCost: Represents the amortized cost of a charge after applying all reduced rates and discounts. This field is denominated in billing currency. ListCost: Represents the cost calculated by multiplying the list unit price and the corresponding pricing quantity. This field is denominated in billing currency. [source]
Atlas-specific FOCUS columns: x_AtlasSku: The Atlas SKU that is being billed. x_PricingCurrencyRate: The "price" of an Atlas Credit. Apply this rate to find the cost of an Atlas Credit in billing currency. x_SkuCategory: Highest-level classification for the associated Atlas SKU. For example, Clusters, or Backup. PricingCurrency: The metering currency for this charge, for example, Atlas Credits. ServiceCategory: Highest-level classification as defined by FOCUS. This is "Databases" for MongoDB Atlas. [source]
FOCUS 1.3 grouping columns for Atlas: BillingAccountId: The Atlas organization ID for this invoice. SubAccountId: An identifier assigned to a sub account, which is a grouping based on organizational constructs. This equates to a Project in MongoDB Atlas (CSV: Project ID, JSON: groupId). SubAccountName: The display name of sub account. This equates to a Project in MongoDB Atlas (CSV: Project, JSON: groupName). ResourceName: For Atlas, this is the cluster name (CSV: Cluster, JSON: clusterName). Tags: Tags assigned to the associated resources. [source]

Problems, failure modes and limitations

Atlas resolves tags at invoice export time, not when the cost occurs. A cluster deleted before export shows as untagged, which breaks tag-based allocation for ephemeral clusters. A customer request filed 2026-06-24 (status Started) got a MongoDB reply on 2026-07-15 saying it is being evaluated for prioritization. Workaround: export invoices before deleting short-lived clusters, or keep an external tag-to-cluster mapping. [source] — workaround is the researcher's; request says none reliable
Accurate tag-based cost attribution is a core part of our FinOps practice. We use resource tags to allocate cloud spend across teams, track budgets, and produce monthly cost reports. When ephemeral clusters - which are a normal and frequent part of our infrastructure - show up as untagged, entire categories of spend become invisible to our reporting. This directly undermines our ability to manage and understand our cloud costs. [source]
Resource tags in invoices should reflect the state at the time of use, not export time. Atlas should record and persist resource tags at the time each cost event occurs, so that invoice exports always reflect the tag state that was true during the billing period - regardless of whether the cluster still exists at the time of download. This is consistent with how cost allocation tagging works in AWS and GCP. [source]
Resource tags assigned to Atlas clusters are not preserved in invoices if the cluster is deleted before the invoice is exported. Atlas fetches tags live at export time rather than recording them when the cost is incurred. This means that any ephemeral cluster - correctly tagged throughout its entire lifetime - will appear as untagged in the invoice, making it impossible to attribute its costs to the right team, project, or cost center. [source]
Currently, there is no reliable workaround. We have to manually cross-reference cluster creation and deletion logs with invoice line items to reconstruct cost attribution - a time-consuming and error-prone process. For short-lived clusters, this is often not feasible at all. [source] — customer request, Jun 2026: no reliable workaround
Thank you for your feedback. We are aware of this requirement. Since this will involve coordination with some of our other teams, we are currently evaluating it to see how we can prioritize it internally. We'll keep you updated on our progress. [source] — MongoDB reply 2026-07-15: evaluating prioritization

Comparisons and alternatives

Work with standard industry terms: Use SubAccountName and other intuitive FOCUS terms instead of internal API terms such as groupName. [source]

Changes and history

Key Insight: The FinOps Framework has been updated to reflect the present-day practice of FinOps as it evolves to a Cloud+ approach to managing technology spend. The 2025 revisions include the addition of Scopes as a core element of the Framework, and incremental updates to the definition of FinOps and the language used to describe the Principles, Domains, and Capabilities to align with the addition of Scopes. [source]
In October 2024, the Foundation’s Technical Advisory Council (TAC) approved Scopes as a new element in the FinOps Framework to capture the different types of technology cost and usage data that FinOps Practitioners are managing. As part of the Framework 2025 revision approved in March 2025, the definition of a Scope has been further clarified and expanded: [source]
The definition of FinOps has been updated to reflect this era of Cloud+ other technology cost data that FinOps Practitioners are managing. [source]
FinOps Principles act as a north star, guiding the activities of a FinOps practice. Four Principles have been updated to balance the primary scope of cloud with language that acknowledges the other types of cost data that FinOps Practitioners are managing. This is the first time the FinOps Principles have changed since they were originally crafted in 2019. [source]
The 2025 revisions include the addition of Scopes as a core element of the Framework, and incremental updates to the definition of FinOps and the language used to describe the Principles, Domains, and Capabilities to align with the addition of Scopes. [source]
In June, we announced MongoDB’s Atlas new resource tagging capability - built to provide a simple and easy way to organize and manage database deployments at scale. Today, we are pleased to announce the availability of these tags in billing invoice CSVs and Admin API operations. [source]
Other customers were naming their deployments after internal billing references instead of meaningful names for their development teams. Addressing this leads to an enhanced user experience, streamlined reporting processes, and ensures invoices can meet the unique cost allocation needs of our customers. [source]
FinOps data should be accessible and timely has become FinOps data should be accessible, timely, and accurate. [source]
A centralized team drives FinOps has become FinOps should be enabled centrally. [source]
Understand Cloud Usage and Cost has become Understand Usage and Cost. [source]
Optimize Cloud Usage and Cost has become Optimize Usage and Cost. [source]
Historically, Atlas billing data has been provided in MongoDB-specific formats. Atlas customers, particularly large enterprises and partners, need to expend manual effort to convert Atlas Credit Units (ACUs) into billing currency. [source]

Facts and statements

No, Public Cloud will always be the primary Scope of FinOps, as FinOps was born to address the challenges that arose with the variable cost model of the Cloud. FinOps aims to help all practitioners, and many practitioners are being asked to take on responsibilities in addition to public cloud – including for SaaS, licensing, private cloud, and data center. Framework 2025 reflects this reality. [source]
No, FinOps practitioners define Scopes based on their business’s priorities and unique technology strategy. The FinOps Foundation does not prescribe or limit the possible Scopes. It aims to help all FinOps practitioners, and many practitioners are being asked to take on responsibilities in addition to cloud – such as SaaS, licensing, private cloud, and data center. Framework 2025 reflects this reality. [source]
No, FinOps Scopes are not intended to be mutually exclusive. A Scope may include overlapping types of infrastructure and/or technology. For example, your FinOps practice will focus on the public cloud, and you may also choose to create a Scope to focus on container costs. In this example, you would apply Framework concepts to public cloud costs, and also to container costs, which are not mutually exclusive. [source]
Gain full FinOps visibility into MongoDB Atlas costs across organizations, projects, and SKUs with built-in analytics and AI-powered optimization insights. [source]

Disagreements

Atlas resolves tags at invoice export time, not when the cost occurs. A cluster deleted before export shows as untagged, which breaks tag-based allocation for ephemeral clusters. A customer request filed 2026-06-24 (status Started) got a MongoDB reply on 2026-07-15 saying it is being evaluated for prioritization. Workaround: export invoices before deleting short-lived clusters, or keep an external tag-to-cluster mapping. [source] — workaround is the researcher's; request says none reliable
Currently, there is no reliable workaround. We have to manually cross-reference cluster creation and deletion logs with invoice line items to reconstruct cost attribution - a time-consuming and error-prone process. For short-lived clusters, this is often not feasible at all. [source] — customer request, Jun 2026: no reliable workaround

Related concepts

FinOps Principles Domains and Capabilities — is a part of FinOps Framework Applied to Atlas
FinOps Scopes — is a part of FinOps Framework Applied to Atlas
FOCUS — is a part of FinOps Framework Applied to Atlas
resource tags — is a part of FinOps Framework Applied to Atlas
billing data API — is a part of FinOps Framework Applied to Atlas
cross-organization billing — is a part of FinOps Framework Applied to Atlas
tags lost on deleted clusters — is a problem of FinOps Framework Applied to Atlas
Atlas Credit Units — is a part of FinOps Framework Applied to Atlas
Inform Optimize Operate lifecycle — is a part of FinOps Framework Applied to Atlas
Cost Explorer — is a part of FinOps Framework Applied to Atlas
tagging best practices — is a measure of FinOps Framework Applied to Atlas
DoiT MongoDB Intelligence — is a instance of FinOps Framework Applied to Atlas
Atlas Well-Architected cost guidance — is a related of FinOps Framework Applied to Atlas
billing dashboard — is a part of FinOps Framework Applied to Atlas
tag lag — is a measure of FinOps Framework Applied to Atlas

Children

Atlas tag taxonomy for showback and chargeback

← the whole tree · 3D view· how to read this page