The FinOps community trusts the FinOps Foundation as a neutral party with no stake in positioning one tool or service provider over another.
This certification signals to the community that…
The FinOps Certified Platform certification badge will be displayed on your FinOps Foundation Member Page, the FinOps Landscape, and on booths at the FinOps X conference.
Being a FinOps Foundation Member and Linux Foundation Member in good standing are prerequisites to becoming a FinOps Certified Platform.
Demonstrate your team’s knowledge and FinOps expertise through FinOps training and certifications.
The FinOps Certified Platform certification requires individuals in your organization to have achieved FinOps Certified Practitioner and FinOps Certified Professional certifications based on your organization’s size.
The following table outlines the types and number of certifications that individuals in your organization require. Note the different types of individual certifications outlined in the table are mutually exclusive. For example, one FinOps Certified Professional certification does not substitute for FinOps Certified Practitioner certifications. One individual can hold multiple certifications and each certification that one individual holds counts toward the total required.
| FinOps Platform | |||
|---|---|---|---|
| Company Size | FinOps Certified Practitioner | FinOps Certified Professional | FinOps Certified FOCUS Analyst |
| 5,000 + | 100 | 5 | 30 |
| 500 – 4,999 | 50 | 3 | 15 |
| 100 – 499 | 10 | 2 | 3 |
| Less than 100 | 5 | 1 | 2 |
| The “Company Size” column in this table refers to the parent organization size that was used for defining your fee structure when you joined the Linux Foundation and counts are not based on the individual business unit. For example, a 100 person product team that is part of a 1,500 person organization would fall into the “500-4,999” individual certification requirement tier, and not the “100-499” individual certification requirement tier. | |||
The FinOps Framework provides the operating model for how to establish and excel in the practice of FinOps.
The FinOps Certified Platform certification requires publicly referenceable information about your product that highlights feature/functionality alignment to the Framework Capabilities and Supplemental Criteria outlined in the tables below, accompanied by a recorded demonstration of your product showcasing those FinOps capabilities.
Each Framework Capability is assigned a FinOps tool criteria value that is weighted in the context for how software functionality enables that FinOps Capability for FinOps Core Personas. The criteria value is not a reflection of the FinOps Framework Capability’s value in the practice of FinOps.
FinOps tool feature alignment is evaluated and counted as a single-point-value based on (i) publicly referenceable evidence, along with (ii) a single video recording of your product, demonstrating alignment with the corresponding FinOps Framework Capability. This means the FinOps tool feature/functionality is assessed as either meeting the Framework Capability criterion (full point-value) or not meeting it (zero point-value), with no intermediate point-value level.
The FinOps Certified Platform certification requires a FinOps tool to reach a threshold of [75%] of the total possible criteria points from combining the (i) Capability Alignment Criteria and the (ii) Supplemental Criteria.
How does your software enable the following FinOps Capabilities for FinOps Core Personas?
Data Ingestion [tool criteria points: 5]
Capability to enable collection, transfer, store, and normalization of data from various sources, with a goal of creating a complete, contextual dataset of cloud usage and cost data available for analysis.
Allocation [tool criteria points: 5]
Capability to assign and share cloud costs using accounts, tags, labels, and other metadata, creating accountability among teams and projects within an organization.
Reporting & Analytics [tool criteria points: 5]
Capability to enable analysis of cloud data for creating reports to gain insights into usage and spend patterns, identify opportunities for improvement, and support informed decision-making about cloud resources.
Anomaly Management [tool criteria points: 5]
Capability to detect, identify, alert and manage unexpected or unforecasted cloud cost and usage irregularities in a timely manner to lower risk in cost-effective cloud operations.
How does your software enable the following FinOps Capabilities for FinOps Core Personas?
Planning & Estimating [tool criteria points: 3]
Capability to estimate and explore potential cost and value of workloads in an organization’s cloud environment for particular scenarios and models.
Forecasting [tool criteria points: 5]
Capability to provide or create a model of the anticipated future cost and value of cloud systems leveraging statistical methods, historical spend patterns, planned changes, and related metrics.
Budgeting [tool criteria points: 5]
Capability for setting limits, monitoring, and managing cloud spending, aligned with business objectives, to ensure accountability and predictable financial outcomes for cloud-based systems.
Benchmarking [tool criteria points: 3]
Capability to evaluate cloud optimization and value between parts of the organization or against industry peers to inform decision-making and align FinOps with business objectives.
Unit Economics [tool criteria points: 5]
Capability to develop and track metrics that provide an understanding of how an organization’s cloud use and cloud management practices impact the value of the organization’s products, services, or activities.
How does your software enable the following FinOps Capabilities for FinOps Core Personas?
Architecting for Cloud [tool criteria points: 1]
Capability to enable design and modernization of solutions with cost-awareness and efficiency to maximize business value while achieving performance, scalability, and operational objectives.
Workload Optimization [tool criteria points: 5]
Capability to analyze and optimize cloud resources to match specific usage patterns while ensuring that workloads operate efficiently and generate sufficient business value for their cost.
Licensing & SaaS [tool criteria points: 3]
Capability to optimize the impact of software licenses and SaaS investments on an organization’s cloud cost and value structure by understanding vendor-specific licensing terms, use rights, and pricing options, planning for appropriate use aimed to minimize over-deployment (a compliance risk) or under-deployment (shelfware/waste).
Rate Optimization [tool criteria points: 5]
Capability to enable and manage cloud rate efficiency through commitment discounts (RIs, Savings Plans, Committed Use Discounts), and other pricing mechanisms (Spot, interruptible VMs, cost aware region selection) to meet the organization’s operational and budgetary objectives.
Cloud Sustainability [tool criteria points: 3]
Capability of incorporating sustainability criteria and metrics into cloud optimization, to ensure environmental efficiency is balanced with FinOps practices.
How does your software enable the following FinOps Capabilities for FinOps Core Personas?
FinOps Practice Operations [tool criteria points: 1]
Capability of enabling a FinOps culture and empowering the FinOps practice through the implementation of FinOps strategy and processes.
FinOps Education & Enablement [tool criteria points: 1]
Capability of providing FinOps training, skill development, and practical activities that enable teams throughout the organization to adopt and deliver FinOps best practices.
Cloud Policy & Governance [tool criteria points: 3]
Capability to establish policies, controls and governance mechanisms to ensure that cloud use aligns with business objectives, complies with regulatory requirements, and optimizes cloud resources efficiently.
Invoicing & Chargeback [tool criteria points: 5]
Capability to enable cloud invoice reconciliation workflows and chargeback models to align cloud cost data and reporting to specific budgets and accounting requirements.
FinOps Assessment [tool criteria points: 1]
Capability to conduct repeatable, measurable analysis of the maturity of a FinOps practice in the context of the FinOps Framework for insights into strengths and areas for improvement of FinOps activities.
Onboarding Workloads [tool criteria points: 3]
Capability of orchestrating the migration of systems into, or between, cloud environments in a way that provides transparency to usage, impact and cost effectiveness.
Intersecting Disciplines [tool criteria points: 1]
Capability to enable coordination of activities between FinOps and interconnected disciplines and Allied Personas (such as, ITAM, ITFM, Sustainability, Security).
Does your software have a specific technology or FinOps activity concentration, preferred cloud provider compatibility, or achieved compliances?
FinOps Scopes [criteria points: 3 for each FinOps Scope]
This criteria is about enabling the practice of FinOps beyond public cloud.
Technology Concentration [criteria points: 10]
This criteria is for FinOps tools and professional service providers whose software functionality or consulting services exclusively concentrate on a single specific technology (like K8s, or storage optimization for data lakehouses, or automated provisioning/management of interruptible VMs, or other technology) or single specific FinOps activity.
Cloud Providers [criteria points: 3 for each cloud provider]
This criteria includes public CSPs (like Google, AWS, Azure, Oracle, etc) or private cloud infrastructure (like OpenStack, etc).
Compliances [criteria points: 3 for each compliance]
This criteria includes compliances like FedRAMP, GDPR, SOC (Type I or II), ISO 27001
FOCUS is an open-source specification that normalizes cost and usage datasets across vendors and reduces complexity for FinOps Practitioners.
The FinOps Certified Platform certification requires publicly referenceable information indicating your FinOps tool supports FOCUS by having adopted a version of the FOCUS specification to enable functionality for producing and/or importing and/or exporting FOCUS datasets. This includes having a published FOCUS conformance gap report (see example conformance gap reports here and here).
And, individuals in your organization are required to have achieved the FinOps Certified FOCUS Analyst certification based on your organization’s size.
The following table outlines the number of certified individuals your organization requires for this certification. Note the different types of individual certifications outlined in the table are mutually exclusive. For example, a FinOps Certified FOCUS Analyst certification does not substitute for any FinOps Certified Practitioner certifications.
| FinOps Platform | |||
| Company Size | FinOps Certified Practitioner | FinOps Certified Professional | FinOps Certified FOCUS Analyst |
| 5,000 + | 100 | 5 | 30 |
| 500 – 4,999 | 50 | 3 | 15 |
| 100 – 499 | 10 | 2 | 3 |
| Less than 100 | 5 | 1 | 2 |
| The “Company Size” column in this table refers to the parent organization size that was used for defining your fee structure when you joined the Linux Foundation and counts are not based on the individual business unit. For example, a 100 person product team that is part of a 1,500 person organization would fall into the “500-4,999” individual certification requirement tier, and not the “100-499” individual certification requirement tier. | |||
The “Company Size” column in this table refers to the parent organization size that was used for defining your fee structure when you joined the Linux Foundation and counts are not based on the individual business unit. For example, a 100 person product team that is part of a 1,500 person organization would fall into the “500-4,999” individual certification requirement tier, and not the “100-499” individual certification requirement tier.
The FinOps Foundation is here to advance the people who do FinOps by creating and enriching community connections. The FinOps Certified Platform certification requires member organizations to engage with the community as follows…
All of the following community engagement criteria
Additional information about opportunities for engaging with the FinOps community can be found here.
The FinOps Foundation is here to advance the people who do FinOps by providing opportunities for practitioners to contribute resources about learnings, how-tos and best practices in relation to the FinOps Framework to our Asset Library.
The FinOps Certified Platform certification requires member organizations to contribute [ 1 ] of the following resources listed below within the past 18 months aligned with the FinOps Framework.
Please contact member-cert@finops.org to start the certification process for your FinOps tool or FinOps professional services offering.
The practice of FinOps, and the landscape of FinOps tools & service providers, continues to evolve. The certification requirements have been updated to align with the latest Framework update, the FOCUS Specification, the FinOps Landscape, FinOps Foundation learning materials and the FinOps related content and language being used by practitioners in the community.
The FinOps Certified Platform certification has been simplified by consolidating the previous separate but overlapping certifications for “platform” and for “specialty solution”. Framework Capability requirements have been updated to recognize strengths and differences between software features and professional services offerings. Criteria has been updated to help you showcase and validate your FinOps capabilities. Additionally, criteria for the FOCUS specification has been introduced.
The updated certification types are FinOps Certified Platform for software tools related to FinOps, and FinOps Certified Service Provider for professional services / consultant FinOps offerings.
The FinOps Certified Platform certification has been simplified by consolidating the previous separate but overlapping certification requirements for “platform” and for “specialty solution”. Feedback also suggested there was confusion around terms like “Platform”, “Solution”, and “Specialty”.
The level of effort remains relatively unchanged, as the criteria still cover the same broad themes as past certification requirements. However, the latest criteria place clearer emphasis on community engagement and contribution expectations, introduce new FOCUS criteria, and update FinOps Capability requirements to better reflect differences between software and professional services offerings.
No. The FinOps Certified Professional individual certification does not substitute for or count towards other individual certifications. For example, one FinOps Certified Professional certification does not substitute for any FinOps Certified Practitioner certifications.
The “Company Size” column refers to the parent organization size used when defining your Linux Foundation fee structure. Counts are not based on individual business units. For example, a 100-person product team within a 1,500-person organization falls into the “500–4,999” tier, not the “100–499” tier.
The individual certification requirement is shared. If each certification requires one FinOps Certified Professional, a single individual can fulfill both requirements.
No. The Certified FOCUS Analyst certification is supplementary and separate. The FinOps Certified Practitioner validates FinOps Framework knowledge, while the FOCUS Analyst certification validates concepts, measures, and datasets specific to the FOCUS specification.
Yes. The FinOps Certified Engineer certification counts 1:1 toward the required number of FinOps Certified Practitioner certifications based on company size.
The FOCUS Analyst certification encourages internal investment in FinOps and emphasizes organization-wide alignment around cost and usage data handling. It increases the likelihood that FOCUS is reflected in product decisions, documentation, and customer experience.
The requirements recognize differences between building software and providing professional services. Consulting requires validating deeper knowledge for understanding and supporting FOCUS initiatives.
Yes. Current certifications remain valid. Members will be contacted when renewal is due.
No. Existing certifications remain valid. Renewal communication will be sent when required.
A FinOps Foundation member organization that builds, licenses, and delivers commercial software helping practitioners adopt FinOps capabilities aligned with the FinOps Framework and best practices. This includes open-source tools where the member is a founder or maintainer.
A FinOps Foundation member providing consulting or advisory services that help practitioners adopt FinOps capabilities aligned with the FinOps Framework and best practices. This may include software implementation and technology deployment as part of professional services.
Yes. Founding maintainers of qualifying open-source FinOps tools may be considered.
No. This is not a ranking or rating system. Certifications indicate alignment with FinOps best practices, Framework alignment, and active community contribution.
No. Certifications are not transferable or shareable and do not extend to white-label partners.
Each Framework Capability is assigned a weighted tool criteria value based on how software enables that capability for FinOps personas. These values are not a ranking or score.
There is publicly referenceable information indicating your platform supports FOCUS by producing, importing, or exporting FOCUS-conformant datasets.
Yes. Recertification occurs two years after certification. The Foundation will reach out when it’s time.
Contact member-cert@finops.org to begin the process.
Certification signals that:
Certifications appear on your FinOps Foundation Member Page and the FinOps Landscape.
Contact member-cert@finops.org.