This work is licensed under CC BY 4.0 - Read how use or adaptation requires attribution
Early Bird registration still available for FinOps X 2024

Framework Overview

The FinOps Framework provides the operating model for how to establish and excel in the practice of FinOps. Like FinOps, the Framework is evolving and informed by community experiences, contributions, and conversations. It’s built by the community, for the community.

How to contribute

The open source FinOps Framework updates its definitions, guidance, and information based on the collective experience of  FinOps practitioners. These improvements come from Working Group outputs, Special Interest Group work, community discussions, and more.

Check out some of our Contribution Guidelines to learn how to tell your story or present FinOps best practices. You can also see active Working Groups, which are small groups that meet regularly to create and iterate on new best practices and guidance for FinOps practitioners.

Frequently Asked Questions

How do I submit changes to the FinOps Framework?

If you see something that needs to be updated, augmented, or removed, we want to hear about it. This project is by the community and for the community and your voice matters.

There are multiple ways to submit changes:

  • Submit an update or let us know of an error via the "Make Suggestion" button (top-right corner of Framework pages)
  • Reach out to the members and team in the #framework slack channel

What is the review process?

Changes to each respective section of this site will be reviewed during FinOps Foundation team meetings, or meetings with the Technical Advisory Council. During these council meetings, commits and Pull Requests can be reviewed and voted upon to be merged.

The FinOps Foundation team uses automation tools to rebuild the site multiple times a week to capture the latest changes or to make small updates to maintain the site.

What are the review cycles and timings?

The FinOps Foundation’s core operating members maintain the organization as a business. Its technical components, however, must be reviewed and voted upon by a greater group of community members. These meetings are scheduled throughout the month and the timeliness of reviewing commits and changes will vary depending on when these meetings occur.

Issues and small changes like link fixes and typos might occur immediately, as those don’t require a significant amount of code review, voting, and/or approval.