Stay organized with collections
Save and categorize content based on your preferences.
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.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-29 UTC."],[],[],null,["# Open source compliance\n\nProducts that include open source software must comply with the license\nrequirements of the included open source software. Many Googlers are also open source\ncontributors or maintainers, so we're especially sensitive to treating the\ncommunity with respect. We have found that the easiest and fastest way for\nyou to ensure open source compliance for most libraries is to include the\nfull source code and license text in your solution.\n\nWe recommend using the following guidelines to ensure compliance with\nopen source licenses:\n\n- If you're using what is pre-installed on a Compute Engine supported\n OS image, and not installing additional open source components, you don't\n need to provide the source code or license text for the components.\n\n- If you're installing an open source component that's under a GPL or LGPL\n license, then install the license text along with the source code\n on the instance image.\n\n- If you're installing an open source component on top of a\n Compute Engine supported OS image, *and* the component license is one\n of the allowlisted licenses (MIT, BSD, and Apache or other), provide\n only the license text file on the instance image, along with a list of\n components.\n\nYou are not required to submit an open source compliance worksheet to\nCloud Marketplace for review, but products must comply with the\nlicensing requirements of any included open source software.\n\nIf an open source software developer finds you in violation of their license,\nthey can submit a [takedown notice](https://www.google.com/dmca.html).\nYour listing can be pulled from Cloud Marketplace until the issue is resolved."]]
