6.3 Snowflake Marketplace, Listings, and Data Exchange
Key Takeaways
- Snowflake Marketplace is the public catalog where providers publish listings and consumers discover them across regions and clouds.
- Listings come in three types: free (instant access), personalized (request a custom dataset), and paid (monetized with usage- or term-based pricing).
- Data Exchange is a private, invite-only marketplace an organization runs for its own members, partners, or customers.
- Listings auto-fulfill across regions and clouds via replication, which direct shares cannot do.
Snowflake Marketplace
The Snowflake Marketplace is the global, public catalog where providers publish listings of data, and any Snowflake consumer can discover and access them. Marketplace is built on Secure Data Sharing, so the same principles apply: getting a free listing creates a read-only, no-copy database in the consumer account, and the consumer queries it on its own warehouse.
Marketplace solves the discovery and cross-region problems that direct shares cannot. A direct share works only within one region and cloud and must be set up account-by-account. A listing is discoverable by anyone, can target many consumers, and auto-fulfills across regions and clouds by replicating the underlying data on the provider's behalf.
The three listing types
| Listing type | How the consumer gets data | Typical use |
|---|---|---|
| Free | Instant access on request; no payment | Public/open datasets, lead generation |
| Personalized | Consumer submits a request; provider fulfills a custom share | Bespoke or account-specific data |
| Paid | Consumer purchases via Snowflake billing | Monetized commercial data products |
A free listing grants access immediately once replicated to the consumer's region. A personalized listing lets a consumer request data tailored to them, which the provider then fulfills. A paid listing monetizes the data: Snowflake handles billing, and providers set usage-based or term-based pricing. Across all three, the provider continues to own and pay for the underlying storage.
Cross-Region and Cross-Cloud Fulfillment
The Marketplace's biggest advantage over direct shares is automatic cross-region / cross-cloud delivery. Because the underlying mechanism is still Secure Data Sharing — which is single-region — Snowflake bridges regions by replicating the data. For a free listing, the provider must replicate the data to each selected region (or enable auto-fulfillment, which replicates to a consumer's region after they request the listing). The provider assigns a warehouse and a replication interval for auto-fulfillment.
This is the practical rule to carry into the exam:
- Same region and cloud, specific known consumer → use a direct share.
- Different region/cloud, or public discovery, or monetization → use a Marketplace listing.
Provider responsibilities
To publish, a provider must complete profile and provider requirements, create a share or auto-fulfillment configuration, attach descriptive metadata (title, description, sample queries, usage examples), and submit the listing for Snowflake review. Rich metadata improves discoverability and is part of listing quality.
Data Exchange — the Private Marketplace
A Data Exchange is a private, invite-only version of the Marketplace that an organization stands up for a defined group — internal business units, partners, suppliers, or customers. It is administered by the organization (an exchange admin manages members and their roles as provider, consumer, or both), and listings are visible only to invited members rather than the entire Snowflake ecosystem.
| Feature | Marketplace | Data Exchange |
|---|---|---|
| Audience | Public — all Snowflake accounts | Private — invited members only |
| Administered by | Snowflake | The organization |
| Listing visibility | Global catalog | Closed group |
| Monetization | Yes (paid listings) | Member-defined / internal |
| Built on | Secure Data Sharing | Secure Data Sharing |
Use a Data Exchange when an enterprise wants the listing experience (discovery, metadata, request workflows) but must restrict who can see and request the data. Use the public Marketplace when the goal is broad discovery or commercial distribution. Both are listing-based and therefore both can fulfill across regions through replication — a capability a plain direct share lacks.
Direct Shares vs. Listings — the Core Comparison
The exam frequently forces a choice between a direct share and a listing. They share the same engine (Secure Data Sharing) but differ in reach and workflow:
| Dimension | Direct share | Listing (Marketplace / Data Exchange) |
|---|---|---|
| Discovery | None — you must know the consumer account | Catalog with search, categories, metadata |
| Region/cloud reach | Same region & cloud only | Cross-region/cloud via auto-fulfillment |
| Number of consumers | Added one account at a time | Many consumers, including unknown ones |
| Monetization | No | Yes (paid listings) |
| Metadata / documentation | Minimal | Rich (title, description, sample SQL) |
| Setup overhead | Lowest | Higher (review, replication) |
A direct share is the lightweight choice when you already know exactly who the consumer is and they sit in your region. The moment a scenario adds discovery, monetization, many or unknown consumers, or another region or cloud, the answer shifts to a listing. Free listings can be fulfilled to a consumer's region without manual approval once replication is in place, while paid and personalized listings add billing or custom-fulfillment steps.
Provider and consumer responsibilities in Marketplace
Providers are responsible for completing provider requirements, attaching a share or auto-fulfillment configuration, supplying high-quality metadata, and maintaining data freshness. Consumers browse the catalog, request or purchase a listing, and on access receive a read-only database in their account that they query with their own warehouse. Throughout, the no-copy, provider-pays-storage invariants of Secure Data Sharing still hold — a listing is a discovery and fulfillment wrapper on top of the same sharing mechanism, not a separate way of moving data.
A data provider wants to monetize a dataset and make it discoverable to any Snowflake customer worldwide, including in other cloud regions. Which mechanism fits best?
Which listing type lets a consumer submit a request for a dataset tailored specifically to them, which the provider then fulfills?
An enterprise wants a listing-style catalog with discovery and request workflows, but visible only to its invited partners — not the public. What should it use?