Course contents

SnowPro Core COF-C03 Study GuidePart 5: Data protection and sharingSnowflake Marketplace & Listings

Snowflake Marketplace & Listings

Snowflake Marketplace & Listings

Definition

The Snowflake Marketplace is the public discovery surface for data and app products, built on the same Secure Data Sharing mechanism. Listings can also be private, offered only to accounts the provider names. A listing is what a provider publishes: metadata, sample data, pricing (free or paid), and the actual share reference.

Listings come in two flavors worth telling apart. A public listing is discoverable by anyone browsing the Marketplace. A private listing is shared only with specific accounts the provider names, functioning as a governed, invitation-only version of the same publishing workflow, useful for a company sharing curated data with a short list of partners without exposing it publicly.

Paid listings add commerce on top: the provider sets pricing (subscription or usage-based), Snowflake handles billing, and the consumer's spend flows through their existing Snowflake relationship rather than a separate vendor contract. And listings solve the geography problem shares alone can't: with auto-fulfillment, Snowflake replicates the product to whatever region a consumer buys from, so a provider in AWS eu-west-1 can serve a consumer in Azure Japan East without either side hand-building replication. The provider pays for the regional copies. The consumer pays for the listing, if it's paid, and for its own compute. A raw share, by contrast, stops at the region border: without a listing, you replicate the database to your own account in the consumer's region and share from there.

Sharing across regions. Provider IsmaFrost is in AWS eu-west-1, the consumer in Azure Japan East. A direct share cannot cross the region border. A listing with Cross-Cloud Auto-Fulfillment can: Snowflake copies the data once to the consumer's region and keeps it refreshed, at the provider's expense; the consumer mounts a read-only database and pays the compute of its own warehouse.PROVIDER REGION · AWS EU-WEST-1CONSUMER REGION · AZURE JAPAN EAST1 · DIRECT SHARESHARESALES_SHAREdirect shareCONSUMERConsumer accountnothing arrives✗2 · LISTING WITH AUTO-FULFILLMENTLISTINGSALES_LISTINGauto-fulfillment onMANAGED BY SNOWFLAKERegional copyrefreshed by SnowflakeREAD-ONLYConsumer database✓Provider pays: replicationand storage in Japan EastConsumer pays: compute of its own warehouse.Other route: replicate the database to your own account in that region, then share from there.refusedcopied onceper regionpoints to

PROVIDER REGION · AWS EU-WEST-1

CONSUMER REGION · AZURE JAPAN EAST

1 · DIRECT SHARE

SHARESALES_SHAREdirect share

refused

✗CONSUMERConsumer accountnothing arrives

2 · LISTING WITH AUTO-FULFILLMENT

LISTINGSALES_LISTINGauto-fulfillment on

copied once per region

MANAGED BY SNOWFLAKERegional copyrefreshed by Snowflake

Provider pays: replication and storage in Japan East

points to

✓READ-ONLYConsumer database

Consumer pays: compute of its own warehouse.

Other route: replicate the database to your own account in that region, then share from there.

Figure 5.7 A direct share stops at the region border; a listing with Cross-Cloud Auto-Fulfillment crosses it by copying the data once into the consumer's region. Top row: refused. Bottom row: the provider pays the copy, the consumer pays its own compute.