The FinOps Framework is built by the community, for the community, and as such, it is periodically updated to reflect the community’s maturing definition of FinOps. We welcome your suggestions that streamline and simplify components of the Framework.
Framework updates may be simple changes (such as rephrasing) to more comprehensive proposals (such as adding a new section or changing a Capability). Framework updates will typically be considered when they materially improve the completeness, accuracy, or clarity of the description.
Format: The ideal length is a few lines to a few paragraphs in written format.
FinOps Framework content strives to be cloud, vendor, and organization neutral in almost all cases unless specific references are required to illustrate concepts.
You may also contribute individually by creating a piece of content that draws from your experience. Contributions should help anyone consuming the content to better understand how an aspect of FinOps can be performed.
Contributions should be aligned with the FinOps Foundation Framework and not be contradictory or confusing by using other concepts. Content submissions can include references to Cloud Service Providers (CSPs), products, or tools used, but cannot pitch, recommend or sell any product or service. If the resource was essential to solving your problem, you should name it, but avoid making testimonials. Individual submissions will be reviewed before they can be published to the most appropriate location.
Suggested contribution types
Playbooks are prescriptive examples of how you or your organization performs one or more FinOps activities or Capabilities. These contributions should be a ‘How To’ guide, detailing how you implement the Capability, assess performance, engage your organization, and produce results. The goal of a playbook is to guide someone through the process of “doing” a FinOps task.
How does someone do [a specific FinOps activity or task]?
Format: Use the Playbook Template and include supporting images, figures, graphs, and charts.
– Webpage or Document (preferred): 2+ written pages
– Video: Slideshow that walks through all the elements from the Playbook Template
Examples
Papers are detailed write-ups about a Framework capability or concept. Papers typically go into some aspect of a FinOps element that is not readily apparent or may only apply in certain circumstances, or which may only be experienced by practitioners of a certain type/size/maturity. These long-form, academic reports or whitepapers offer nuanced interpretations or understandings of an aspect of FinOps.
How should I think about [a FinOps concept, capability and/or process]?
Format: Use the FinOps Paper Template and include supporting images, figures, graphs, and charts.
– Webpage or Document: 2+ written pages
Examples
Utilities are resources that other community members can use in their day-to-day FinOps practices. They help other practitioners with FinOps challenges.
Has anyone created something that I can use to do [a specific FinOps activity or task]?
Formats:
– web-based tool
– scripted programs
– code snippets (gists, text)
– code snippets (text)
– spreadsheets (including macro/formulas)
– pseudo- code
– binary files
Example: Azure CPU Coverage with Commitment Based Discounts
Additional Requirements:
We will add content to the Asset Library if it helps address or improve the following:
All content contributions will be reviewed by TAC. We may not be able to use your submission for a variety of reasons. If your content is selected, we will attribute it to you (unless you prefer to remain anonymous).
At the top of each of the asset pages on the FinOps.org website, you will see a button that says “Make Suggestion.” If your contribution is straightforward, you can enter it right there on that form. Please include your contact information so our staff can reach out if they have any questions.
You may compose any of the contributions described on this page into an email or document, and forward it to hello@FinOps.org. Put “Content Contribution” in the Subject line, and include all the other information requested below.
We can’t wait to see your informative contribution!