Data Collaboration · Topic 5 of 5

Snowflake Marketplace, Listings and Native Apps

Private vs public listings, Snowflake Marketplace, free, trial and paid access, Cross-Cloud Auto-Fulfillment and how Snowflake Native Apps run.

  • 5 min
In a nutshell
  • A listing = share or Native App + metadata (title, description, sample queries), on the Secure Data Sharing model.
  • Private listings target named accounts; public listings appear on Snowflake Marketplace.
  • Listings support free, limited trial and paid access; paid listings are region limited.

What it is

A listing is an enhanced form of Secure Data Sharing. It wraps a share or a Snowflake Native App together with metadata such as a title, description, sample SQL queries and usage examples, so consumers can discover and understand the product.

Snowflake Marketplace is where public listings are published for any Snowflake customer to find. A Snowflake Native App is a packaged application, with code and optional data, that a consumer installs and runs inside its own account.

Data productshare or app packagewrapped inListingmetadata, termspublished asPrivate listingchosen accountsData productshare or app packagewrapped inListingmetadata, termspublished asPublic listingSnowflake Marketplace

How it works

Private and public listings

TypeWho can see and get itTypical use
Private listingOnly the specific consumer accounts the provider namesSharing with known partners or customers, including across regions
Public listingAny Snowflake customer browsing Snowflake MarketplaceReaching many unknown consumers, building a data business

Both use the same provider and consumer model as direct shares. The consumer still reads live data with its own compute, and nothing is copied into the consumer account within one region.

Snowflake also offers organizational listings for sharing data products between accounts inside one organization. They focus on internal sharing and do not support pricing plans.

Creating and getting a listing

Providers create listings in Snowsight with the ACCOUNTADMIN role or a role with provider privileges. Using listings requires accepting Snowflake's provider terms, and publishing on Snowflake Marketplace also needs a provider profile.

Consumers browse Snowflake Marketplace in Snowsight, open a listing and select Get. This creates a database (or installs an app) in their account, which they query like any imported database.

ProviderSnowsightpublishSnowflake Marketplacepublic listingGetConsumer accountimported databasequery withConsumer warehouse

Access options

OptionMeaning
FreeInstant access to the full published data product
Limited trialMarketplace only; instant but limited access for a set period, after which the consumer can request full access
PaidConsumer pays through Snowflake using the provider's pricing plan; available only in supported regions

Paid private listings require approval from Snowflake. Pricing plans and offers let one paid listing carry several options or terms for individual consumers.

Cross-Cloud Auto-Fulfillment

A direct share stops at the region boundary. Listings remove that limit with Cross-Cloud Auto-Fulfillment: Snowflake automatically replicates the data product to the regions where consumers request it. The provider does not have to set up replication manually, but pays the replication costs.

Exam tip

"Share with consumers in several regions and clouds with the least administration" points to a listing with Cross-Cloud Auto-Fulfillment, not a direct share plus manual replication.

Listing vs direct share

RequirementPick
One partner, same region, nothing moreDirect share
Consumers in other regions or cloudsPrivate listing with Cross-Cloud Auto-Fulfillment
Rich description, sample queries and usage metricsListing
Charge consumers for accessPaid listing
Reach unknown customersPublic listing on Snowflake Marketplace

Snowflake Native Apps

The Snowflake Native App Framework lets a provider share business logic, not just data. A provider builds an application package that holds:

  • a manifest file that defines the app's configuration, including the setup script location and versions;
  • a setup script of SQL that runs when the consumer installs or upgrades the app;
  • application logic such as stored procedures and UDFs, optional shared data, and optional Streamlit user interfaces.

The provider releases versions and patches to roll out updates. The package is distributed through a listing, either public on Snowflake Marketplace or private to specific accounts, and it can be free or paid.

Providerapplication packagelistingConsumerinstalls appsetup script createsApplication objectruns in consumer accountreadsConsumer datawith granted privileges

When a consumer installs the app, an application object is created in the consumer's account and the setup script builds its objects. The app runs there, next to the consumer's data, so that data does not leave the account. The consumer grants the app only the privileges it needs. Apps can also use Snowpark Container Services, in which case the consumer provides a compute pool.

Event sharing lets a consumer send the app's logs and events back to the provider for troubleshooting and monitoring, if the consumer enables it.

Watch out

A Native App does not move consumer data to the provider. When a scenario wants a vendor's logic applied to sensitive customer data that must stay in the customer account, the answer is a Snowflake Native App.

Common mistakes

Thinking Marketplace data is copied into your account. Getting a listing in the same region creates an imported database over live shared data; you pay compute to query it, not storage.

Using a public listing for a confidential partner deal. Public listings are visible to every Marketplace user. Use a private listing for named partners.

Setting up manual replication for every region. Cross-Cloud Auto-Fulfillment replicates a listing's data product automatically.

Treating a Native App as a remote service. It installs and runs inside the consumer's account.

Assuming limited trials exist for private listings. Limited trial is a Marketplace option.

What to remember for the exam

  • A listing = share or Native App + metadata (title, description, sample queries), on the Secure Data Sharing model.
  • Private listings target named accounts; public listings appear on Snowflake Marketplace.
  • Listings support free, limited trial and paid access; paid listings are region limited.
  • Cross-Cloud Auto-Fulfillment replicates listing data to other regions automatically.
  • Consumers select Get in Snowsight to create a database or install an app.
  • Native Apps: application package with manifest file and setup script, versions and patches, installed and run in the consumer account.

Check yourself

  • A provider wants any Snowflake customer to discover and subscribe to its weather data. What should it use?

    A public listing on Snowflake Marketplace.

  • How does a listing reach consumers in a different cloud region without manual replication?

    Cross-Cloud Auto-Fulfillment replicates the data product to the consumer's region automatically.

  • Where does a Snowflake Native App run after a consumer installs it?

    In the consumer's own account, as an application object created by the app's setup script.

Topic 5 of 5 in Data Collaboration

Test yourself on Data Collaboration

The full Snowflake SnowPro Core COF-C03 question bank has 845 questions, with timed practice exams and an explanation for every answer.

This study guide is independent and is not affiliated with, endorsed by, or sponsored by Snowflake. Vendor names, certification names and exam codes are trademarks of their respective owners and are used for identification only.