Cloud Carbon Footprint

Cloud Carbon Footprint is an open source tool and methodology that provides visibility and tooling to measure, monitor and reduce organizations' infrastructure carbon emissions and optimize costs associated with cloud computing.

Website: https://www.cloudcarbonfootprint.org/

Type of Digital Public Good

  • Open content
  • Open data
  • ✅  Open software
  • Open standard
  • Open AI model

1. Is it relevant to one of the Sustainable Development Goals?

  • 7. Affordable and Clean Energy

    Evidence: CCF provides estimates for both energy and carbon emissions for all types of cloud usage including embodied emissions from manufacturing, with the ability to drill down into emissions by cloud provider, account, service and time period.

    Link to Evidence: https://www.cloudcarbonfootprint.org/

  • 12. Responsible Consumption and Production

    Evidence: Understanding your cloud carbon footprint baseline helps you make specific, targeted reductions to reduce your emissions, such as rightsizing, deleting idle instances, and more.

    Link to Evidence: https://www.cloudcarbonfootprint.org/

  • 13. Climate Action

    Evidence: The software tool helps users measure and analyze cloud carbon emissions, the tool helps users understand the impacts of their carbon footprint on our environment and provides specific recommendations for ways to mitigate those impacts

    Link to Evidence: https://www.cloudcarbonfootprint.org/

2. Does it use an appropriate open license?

Yes, this project is licensed under the following license(s):

3. Is ownership clearly defined?

Is the ownership of the project and everything that the project produces clearly defined and documented?

Yes

If yes - please link to the relevant copyright, trademarks, or ownership documentation for the project.

https://github.com/cloud-carbon-footprint/cloud-carbon-footprint/blob/trunk/README.md

4. Does the license of libraries/dependencies undermine the openess of the project?

Does this open project have mandatory dependencies (i.e. libraries, hardware) that create more restrictions than the original license?

No

If yes - are the open source components able to demonstrate independence from the closed component(s) and/or are there functional, open alternatives?

Not Applicable

If yes - please describe how the open source components are independent and/or list the open alternatives for the closed component:

Not Applicable

5. Is there documentation?

Does some documentation exist of the source code, use cases, and/or functional requirements. For software projects, this should be present as technical documentation that would allow a technical person unfamiliar with the project to launch and run the software. For datasets and data projects, this should be present as documentation that describes all the fields in the set, and provides context on how the data was collected and how it should be interpreted. For content collections, this should indicate any relevant compatible apps, software, hardware required to access the content and any instructions about how to use it.

Yes

If yes - please link to the relevant documentation:

6. Is non PII data and/or content accessible?

Does this project collect or use non-personally identifiable information (non-PII) data and/or content?

No

If yes - is there a mechanism for extracting or importing non-personally identifiable information (non-PII) from the system in a non-proprietary format?

Not Applicable

If yes - describe the mechanism for extracting or importing non-personally identifiable information from the system in a non-proprietary format:

Not Applicable

7. Does the project adhere to privacy and other applicable international and domestic laws?

Has this project taken steps to ensure adherence with relevant privacy, domestic, and international laws? For example, the General Data Protection Regulation (GDPR) in the European Union or the Supplementary Act A/SA.1/01/10 on Personal Data Protection for the Economic Community of West African States (ECOWAS) (yes/no)

Yes

If yes, please list some of relevant laws that the project complies with:

  • This offering does not use PII – we have ThoughtWork's privacy policy linked and stated on our microsite.

If yes, please describe the steps this project has taken to ensure adherence (include links to terms of service, privacy policy, or other relevant documentation):

8. Does the project adhere to standards and best practices?

Does this project support standards? (i.e. Web Content Accessibility Guidelines (WCAG) 2.1 or other standards such as those listed on W3C)

Yes

Which standards does this project support (please list)

  • For Codebase: Technical and Design Standards/Best - HTTP/HTTPS, CSS, JSON, REST
  • For Client and Microsite: WCAG and other W3C Standards (privacy, security, etc where applicable)

Can you point to evidence of your support? (i.e. please link to your validator, open test suite, etc.)

Was this project built and developed according to or in adherence with any design, technical and/or sector best practices or principles? i.e. the Principles for Digital Development?

Yes

Which principles and best practices does this project support (please list)

  • Measurements confirmed and kept up-to-date via Website Carbon Calculator
  • Principles for Digital Development
  • Domain Driven Design
  • Test Driven Development (https://martinfowler.com/articles/practical-test-pyramid.html)
  • Open Source Principles with transparent methodology, source code, and public forums for peer reviews and validation

9. Does the project do no harm by design?

Has this project taken steps to anticipate, prevent and do no harm by design?

On the whole, does this project take steps to ensure that it anticipates, prevents and does no harm by design?

Yes

Is there any additional information you would like to share about the mechanisms, processes or policies that this project uses to avoid doing harm by design?

The purpose of the tool is to help companies address sustainability goals through improving efficiency of cloud usage and therefore reducing carbon emissions associated with their cloud carbon usage. This project does not require users to provide personal data to be functional or valuable. Because this is an open-source tool, it is not proprietary, and users can tailor it to their own needs. Because of the collaborative nature of the methodology stakeholders are encouraged to influence the development of the tool and leverage the discussion group for expressing concerns and issues. The Thoughtworks team monitors the discussion group and provides clear guidelines for participation for the stakeholder community.

9.a. Data Privacy & Security

Does this project collect or store personally identifiable information (PII) data and/or content?

No

If yes - please list the types of data and/or content collected and/or stored by the project:

Not Applicable

If yes - does this project share this data and/or content with third parties?

No

Please describe the circumstances with which this project shares data and/or content with third parties. Please add links as relevant.

Not Applicable

If yes - does the project ensure the privacy, security and integrity of this data and/or content collection and has it taken steps to prevent adverse impacts resulting from its collection, storage and distribution.

Yes

If yes - please describe the steps, and include a link to the privacy policy and/or terms of service:

CCF does not require users to provide personal data to be functional or valuable.

9.b. Inappropriate & Illegal Content

Does this project collect, store or distribute content?

No

If yes - what kinds of content does this project, collect, store or distribute? (i.e. childrens books)

Not Applicable

If yes - does this project have policies that describe what is considered innappropriate content? (i.e. child sexual abuse materials)

Not Applicable

If yes - please link to the relevant policy/guidelines/documentation.

Not Applicable

If yes - does this project have policies and processes for detecting and moderating innappropriate/illegal content?

Not Applicable

If yes - please describe the policies and processes for detecting, reporting and removing innapropriate/illegal content (Please include the average response time for assessment and/or action. Link to any policies or descriptions of how inappropriate content is handled):

Not Applicable

9.c. Protection from harassment

Does this project facilitate interactions with or between users or contributors?

Yes

If yes - does the project take steps to address the safety and security of underage users?

Yes

If yes - please describe the steps this project takes to address risk or prevent access by underage users:

  • The software offering is not intended for underage users and is expected to be used by professionals in business environments for tracking and managing carbon emissions associated with an organization's cloud usage.

If yes - does the project help users and contributors protect themselves against grief, abuse, and harassment?

Yes

If yes - please describe the steps taken to help users protect themselves.

Development & deployment countries

List of countries this project was developed in.

  • United States of America

List of countries this project is actively deployed in.

Not Applicable