Open source compliance

Products that include open source software must comply with the license requirements of the included open source software. Many Googlers are also open source contributors or maintainers, so we're especially sensitive to treating the community with respect. We have found that the easiest and fastest way for you to ensure open source compliance for most libraries is to include the full source code and license text in your solution.

We recommend using the following guidelines to ensure compliance with open source licenses:

  • If you're using what is pre-installed on a Compute Engine supported OS image, and not installing additional open source components, you don't need to provide the source code or license text for the components.

  • If you're installing an open source component that's under a GPL or LGPL license, then install the license text along with the source code on the instance image.

  • If you're installing an open source component on top of a Compute Engine supported OS image, and the component license is one of the allowlisted licenses (MIT, BSD, and Apache or other), provide only the license text file on the instance image, along with a list of components.

You are not required to submit an open source compliance worksheet to Cloud Marketplace for review, but products must comply with the licensing requirements of any included open source software.

If an open source software developer finds you in violation of their license, they can submit a takedown notice. Your listing can be pulled from Cloud Marketplace until the issue is resolved.