Take the State of FinOps 2025 Survey

FinOps Certified Platform

FinOps Certified Platforms have demonstrated  that they have products or features that map to most FinOps Framework Capabilities. These comprehensive products offer support for key FinOps activities defined in the Framework.

Why get certified?

Validate your offer: Buyers trust the Foundation as a neutral party with no stake in positioning one tool over another. So, when shopping, buyers visit the FinOps Landscape to see tools that have been validated by the Foundation to meet their unique set of needs.

Marketing: If your organization becomes a FinOps Certified Platform, this designation will be displayed on your Member Page and on the FinOps Landscape.

Increase FinOps expertise: This certification requires a number of individuals in your organization to become certified. Completing individual certifications increases the FinOps knowledge and expertise that your employees hold, in turn helping them deliver better FinOps tools to the market.

Certification Requirements

To become a FinOps Certified Platform, your organization must meet the requirements below.

Pre-Requisites
  1. Be a General or Premier Member of the FinOps Foundation and a Member of the Linux Foundation
  2. Obtain adequate individual certifications within your organization
Mandatory Requirements
  1. Publicly-facing content that shows how your product features map to most FinOps Framework Domains and Capabilities
  2. Host an active Product Support Channel in FinOps Foundation Slack (email us to set this up)
  3. Recorded demonstration of your product highlighting feature alignment to the Framework Capabilities
Optional Requirements

(must meet 3 of 5)

 

Individual Certification Requirements

A number of individuals in your organization must achieve the FinOps Certified Practitioner certification in order for your organization to become a FinOps Certified Platform. The number is based on your company size. For example, if your organization has 1200 people in it, then you need at least 35 individuals—who are actively working at the company—who have each achieved the FinOps Certified Practitioner certification. Note that one FinOps Certified Professional counts for five FinOps Certified Practitioners.

Company Size FinOps Certified Practitioners Required
0-99 3
100-499 10
500-4999 35
5000+ 50

The Company Size is determined by the parent organization size (which was used for defining your fee structure when you joined the Linux Foundation). Employee count is not based on the individual business unit. For example, a 100-person product team that is part of a 1500-person organization would fall into the 500-4999 tier, not the 100-499 tier.

Please contact member-cert@finops.org to start the certification process.

Badge for FinOps Certified Platform

Q&A

What’s the difference between a FinOps Certified Platform and FinOps Certified Specialty Solution?

A FinOps Certified Platform is a full-service FinOps tool that addresses key use cases for a FinOps Practitioner. A FinOps Certified Speciality Solution is a FinOps tool that focuses on one (or few) very specific FinOps use cases such as rate optimization or container cost management.

See the list of current FinOps Certified Platforms and FinOps Certified Specialty Solutions on FinOps Landscape for examples.

What is an example of mapping tool features to FinOps Capabilities?

Here are a few examples of features that map to Framework Capabilities:

Features / Functionality Framework Capability
Anomaly Alert Functionality
  • Anomaly Management
Create and monitor budgets
  • Budgeting
Create Custom Metrics
  • Unit Economics
Commitment-based discount reporting
  • Rate Optimization
Cost Allocation Model
  • Allocatioin
  • Reporting & Analytics
  • Invoicing & Chargeback
Forecasting based on previous spend
  • Forecasting 
Ingest 3rd Party Data 

(either via API, CSV, manual input, etc)

  • FinOps Practice Operations
  • Intersecting Disciplines
Real-time cloud billing data reporting 
  • Onboarding Workloads
  • Data Ingestion
  • FinOps Education & Enablement
  • FinOps Practice Operations
Real-time cloud resource utilization reporting
  • Workload Optimization
  • Cloud Policy & Governance

What is the definition of a contributor for a working group?

A contributor is defined as someone who is interested in the subject matter and is willing and able to participate in the WG. These individual are expected to perform the following duties: 

  • Regularly attend WG meetings (at least 50%)
  • Actively contribute to WG efforts by taking on action items and participating in group discussions
  • Assist working group lead with their duties as needed
  • For additional details, see the Working Group FAQ