Guidelines for Looker Marketplace Submission

The following is a high-level overview of the process of offering Visualizations, Blocks, Apps, and Actions to the Looker Marketplace.  Looker Marketplace guidelines are subject to change without notice.

1. Choose what you want to offer

You can offer one or more of the following product types on the Looker Marketplace:

  • Visualizations: javascript visualizations built on top of the Looker Custom Visualization API
  • Blocks: LookML models and dashboards specific to a data source and set database schema
  • Apps:  applications built using Looker’s extension framework
  • Actions: workflows built on top of Looker’s Action API that push data from Looker into other applications

You can learn more about how to build and submit content for the Marketplace here.

2. Verify that you meet the requirements to submit your product to the Looker Developer Program.

  • Requirements for your organization
  • Your organization must sign or click to agree, as applicable, to the Looker Marketplace Agreement.
  • Requirements for your product
  • Your product must be production-ready (not alpha or beta).
  • Only submissions of LookML Code Blocks, Visualizations, Apps, and Actions will be considered for inclusion in the Looker Marketplace, and must not include professional services.
  • The Looker Developer Relations team will review submissions on an ongoing basis. Submissions that do not meet the requirements will not be added to the Looker Marketplace and the developer will be notified.
  • Operational requirementsYour organization must be willing to commit resources to create and maintain the products that you list in Looker Marketplace, and provide timely support to your customers.

3. Selecting a pricing model

If your submission is approved for listing in the Looker Marketplace, you will need to select a pricing model. You can choose one of the following pricing models for your product:

  • No additional charge: Customers only pay for their Google Cloud resources, such as the cost of their Looker subscription. You are offering your submission without an additional charge.
  • Bring your own license (BYOL): Customers pay you for your product directly, and are billed separately for their use of Google Cloud resources. You must provide a way for your customers to get a license from you, typically through a website. After the customer gets their license, you are responsible for validating the license.

4. Preparing to list your product

After your vendor agreement is finalized, you receive instructions to complete the following steps:

  1. Complete a Looker Marketplace Submission Form, which will be reviewed by the Looker Developer Relations team when considering your submission for inclusion in the Looker Marketplace. 

Considerations for Inclusion in the Looker Marketplace

As part of the submission review, Looker Developer Relations will consider your submission for inclusion in the Looker Marketplace.  Below are highlights of the review.  This is not an exhaustive list:

  • No dynamic sourcing of code.  All code that will execute in this app must be present within the static assets submitted for review. 
  • No minified or obfuscated code.  All code must be clearly readable and documented if necessary to allow for effective code review.
  • No performance impact on Looker. App must not significantly degrade the performance of Looker.
  • Transparency. App developers must be fully transparent and clear about application purpose and behavior and any additional steps or requirements expected of the user/Customer. All external connections should be identified.
  • Customer instructions. App must take appropriate care given the sensitivity of data and ensure that it follows customer instructions, including when connecting to third party connections.
  • Vulnerability management.  All direct dependencies used by the app must be free of Critical or High severity vulnerabilities. If a vulnerability is discovered, the code must be updated within 48 hours. App must sanitize all rendered data as to not introduce Cross Site Scripting vulnerabilities.
  • Open source.  Applicable open source compliance will be reviewed.
  • Pricing model.  Developers may only include one of the approved pricing models.

Considerations for Open Source Compliance

As part of the submission review, Looker Developer Relations will review that you: 

  • Identify the applicable open source license for your product, if any.
  • Confirm that you are meeting notice and attribution obligations and demonstrate how you meet these obligations.
  • If applicable, confirm that you are provided any necessary source bundles, and demonstrate how you meet this obligation.  
  • Confirm that you are not shipping modified AGPL or any SSPL (modified or unmodified).

5. Optionally, sign up to become a Google Cloud Marketplace vendor and prepare your GTM strategy

Sign up as a Google Cloud Marketplace vendor on the Google Cloud Marketplace page in Partner Advantage. After you provide the required information, a Business Development representative works with you to finalize the agreement.  Once you sign up, it typically takes 1-2 weeks to finalize the vendor agreement.  Participants in Partner Advantage may also want to review details about our Google Cloud’s GTM benefits.

Google Cloud
  • ‪English‬
  • ‪Deutsch‬
  • ‪Español‬
  • ‪Español (Latinoamérica)‬
  • ‪Français‬
  • ‪Indonesia‬
  • ‪Italiano‬
  • ‪Português (Brasil)‬
  • ‪简体中文‬
  • ‪繁體中文‬
  • ‪日本語‬
  • ‪한국어‬
控制台