Guidelines for publishing an app to the Snowflake Marketplace¶

Publish an app in the Snowflake Marketplace¶

When your application package is ready to be published on the Snowflake Marketplace, you must submit it to Snowflake for approval.

Before creating a listing, verify that you understand the enforced requirements and ensure that your application package follows each requirement. If an application package does not follow these requirements, your submission may be rejected.

If you receive a rejection notification for the application package you submitted, make the recommended changes and resubmit your application package for approval.

Standards for Native Apps on the Snowflake Marketplace¶

Snowflake provides a platform that allows providers to build, distribute, and monetize apps.

The Snowflake review process ensures the quality of the apps that are published to the Snowflake Marketplace. To ensure a streamlined review process, providers must adhere to the following standards for apps that are published to the Snowflake Marketplace.

Immediate utility

Apps must provide consumers immediate utility and be used within Snowflake without external requirements.

Standalone

Apps must be standalone. Consumers must be able to use the app and app functionality within their account.

Data intensive

Apps that access Snowflake data must use the data appropriately.

Monetized on-platform

Snowflake recommends that monetized apps use the monetization features that Snowflake provides. When an app uses Snowflake on-platform monetization, Snowflake users can use their capacity commitments to purchase third-party solutions.

Transparent

Apps should use Snowflake features to maximize resource and access visibility. of the app. Apps should simplify the configuration process for the consumer.

Enforced requirements¶

Snowflake uses the following standards to determine if a Native App meets the requirements for publication on Snowflake Marketplace. These requirements are verified when you submit a listing with an attached application package to the Snowflake Marketplace.

1. Immediate utility

   1. Apps must not be shell apps that advertise functionality.

   2. Apps must include a clear framework for utilizing app functionality.

2. Standalone

   1. Apps must not redirect consumers to an external service to enable application functionality.

   2. App interfaces must be accessible after installation directly from Snowflake with a Streamlit UI or a custom UI hosted in Snowflake.

   3. Apps must require consumers create users or roles to provide access to an external service that accesses the consumer Snowflake account.

   4. Apps must use the Snowflake Marketplace as a distribution platform for cross-selling external applications or services.

3. Data intensive

   1. Apps must leverage data in one of the following ways:

      1. Share data from the app provider’s account.

      2. Use datasets from the Snowflake Marketplace.

      3. Access data in the consumer account.

4. Monetized on-platform

   1. Apps that are monetized on-platform must include all functionality within Snowflake.

5. Transparent

   1. All account-level privileges and references that the app requires must be listed in the application package manifest file.

   2. All resource requirements for the Snowflake Native App must be listed in the marketplace.yml file of the app. The app must create these resources as part of installation and setup.

   3. If a listing includes an account-level privilege or reference in the security section of the manifest file and the application package contains a Streamlit app, you must use the Snowsight to create a user interface to request privileges and references from the consumer.

   4. If an application package does not include a Streamlit app or custom user interface for the app, the readme file included in the application package must contain the following information:

      1. A description of what the app does.

      2. The steps the consumer must perform to configure the app after it is installed.

      3. The stored procedures and user-defined functions the app uses.

      4. The privileges the app requires.

      5. Example SQL commands that show consumers how to use the app.

   5. If the readme file includes SQL statements or code examples, you must use codeblocks.

   6. Use a single or multi-page Streamlit app instead of multiple separate Streamlit apps, when possible. This includes multi-user Streamlit apps.

   7. If the app provides sample data, you must include procedures on how to use the sample data, including the code required to create the database, if necessary.

   8. If an application package does not contain a readme file, you must provide usage examples in the Sample SQL section of the listing, configure a default Streamlit app, or a default web endpoint.

Best practices when publishing a Snowflake Native App¶

In addition to the requirements for submitting an application package to the Snowflake Marketplace, Snowflake also recommends the following best practices when publishing a Snowflake Native App:

• Ensure that all required files are uploaded to the named stage for the version of the app you are submitting, including:

  • The manifest.yml file.

  • The setup script.

  • The readme.md file.

  • Any external stored procedures or user-defined functions required by the application package.

  • Any Streamlit files required by the application package.

  • Any external source code, including Python, Java, etc.

• Ensure that the version of the app you are developing passes the automated security scan.

• Test the new version of your application package by creating the application object locally by using the CREATE APPLICATION command.

  • Do not add a new version to your application package or set the DISTRIBUTION property to EXTERNAL while you are developing and testing an app. These actions trigger the automated security scan which delays the development cycle.

    Instead, create the application object using files on a named stage.

  • If your app includes a Streamlit app, test the application in Snowsight to ensure the Streamlit app works as expected.

  • Verify that interactions between the Streamlit app and Snowflake Worksheets are seamless and that the consumer does not have to navigate excessively between the two.

• Review all parts of a listing before submitting it for approval.

• Ensure that there are no typos or other textual errors in the listing, readme file, and Streamlit app.