Snowflake Marketplace Provider Economics: Revenue Share, Listing Requirements, and Buyer Discovery
Headline finding: the take rate is real but login-gated, the infrastructure tax on a small listing is roughly 2% of bookings, and the binding cost is human hours.
The question
Verbatim: "What are Snowflake Data Marketplace's actual provider economics (revenue-share terms, listing requirements, buyer discovery mechanics) — concretely enough to evaluate as a data-marketplace entry point?"
Context: the [[01-projects/data-marketplace/index]] What's-Needed list names "Understand Snowflake marketplace economics" as an explicit open item. Filed from the 2026-08-11 curiosity sweep. Double relevance: the dormant data-marketplace bet, and phData Snowflake domain knowledge.
What we already know (from the vault)
- The founding vision is "Substack for databases" — small, opinionated, well-maintained datasets published and monetized by individuals, per [[2026-04-03-magic-of-small-databases]]. Snowflake Marketplace is a different shape: enterprise procurement rails with mandatory human review of every listing.
- Cortex Knowledge Extensions (CKE) are a marketplace listing type, and no publishing gate is documented. [[2026-09-24-cortex-knowledge-extensions-vs-agent-publish]] found no documented restriction on who may publish a CKE, and flagged there that absence of a stated gate is weaker evidence than an explicit permission. This brief adds the missing scale number: 17 CKE listings live on 2026-10-16, roughly 0.4% of the catalog. The packaging primitive exists; supply is thin.
- We have already run the consumer side of a marketplace listing in anger. [[2026-04-16-bq-to-snowflake-ga4-via-gard-connector]] documents installing the free Google Analytics Raw Data (GARD) connector from the Marketplace and records the economic shape: "The connector listing itself is free; you pay only for Snowflake compute (warehouse credits) on the ingest side and BigQuery Storage Read API egress on the source side." That is the free-listing case. This brief fills in the paid case.
- RDCO is dormant and phData is the main bet (founder, 2026-09-23, per Ray memory). The question is therefore not "should we go to market here" but "do the numbers permit this as a near-zero-hours side bet, and what is worth knowing for phData."
- Cross-tenant publishing of agents on Snowflake is still hardening per [[2026-09-23-cortex-agent-cross-tenant-marketplace-publish]] and [[2026-07-08-cortex-agent-cowork-skill-native-publish]]. The data-share path, by contrast, is mature and fully documented.
What the web says
Naming precision, as of 2026-10-16. "Snowflake Data Marketplace" is now just Snowflake Marketplace. Everything in it is a "Data Product," covering three listing types: data shares, Snowflake Native Apps, and Connected Apps. Managed applications and professional services are not eligible for listing (Provider and Consumer Policies). Cortex Knowledge Extensions are now a first-class marketplace category, not a separate surface. Everything below describes the public Snowflake Marketplace provider path unless stated otherwise.
1. Revenue share: a fee exists, the number is not public
Snowflake does not publish a take rate, percentage, or transaction fee anywhere publicly reachable. It confirms the fee exists and puts the number behind a Snowsight login. This is the single most important finding and it is a negative one.
The confirming sentence, provider-facing: "Snowflake Marketplace charges a transaction fee, which is deducted from the Provider's payout," with the instruction to "Find the fee schedule by navigating in Snowsight: Admin → Billing & Terms → Fee" (provider-transactions-invoicing-collections).
The contract does the same thing. The Snowflake Provider and Consumer Terms (effective 2026-03-31) say the customer "is responsible for the Snowflake fees set forth in the relevant Monetization Offering Fee Schedule" (§3.5 Exh. A), and §12.30 defines that schedule as one "made available in Snowsight or as described in the Documentation." The fee is incorporated by reference into a document Snowflake maintains unilaterally. It is not an exhibit to the terms. Terms changes take effect 30 days after posting (§11.8); no notice period is stated for fee-schedule changes.
The net-payment formula is published even though the inputs are not: payout "shall equal the Product Cost minus: (i) the Fees; (ii) any Taxes" plus pre-noticed expenses (§3.5 Exh. A).
Do not quote a percentage. A third-party site surfaced in search claiming "25-30% commission" with no sourcing; that is unverified and is not cited here. The only percentage published anywhere in the corpus is a 1.5% per month late charge (§2.2 Exh. A), which is not a take rate. The single action that produces the real number is an organization-administrator (ORGADMIN) login to Snowsight → Admin → Billing & Terms → Fee.
Does it differ by listing type? Partially answerable:
- Free listings: no Snowflake billing, so no transaction fee. Free private listings do not even require accepting the Provider and Consumer Terms, provided the Customer-Controlled Data Sharing Functionality Terms are accepted (collaboration-listings-about).
- Paid listings billed through Snowflake (usage-based or subscription): the fee applies, amount undisclosed.
- Capacity-commit purchases (Marketplace Capacity Drawdown): Snowflake pays the provider directly rather than via Stripe (provider-listings-pricing-model). Whether the fee differs is not documented.
- "Request a quote" / bring-your-own-contract: there is no documented flow by that name. The real mechanism is a
Requestbutton that collects consumer contact details, after which the provider negotiates by email and hand-publishes a private listing, either free or under a Snowflake pricing plan. "Offers" let a provider set individualized billing, payment terms, and contract dates. Whether a fully off-platform transaction escapes the transaction fee is not documented in either direction. Do not assume it does.
Other commercial terms that matter and are public:
- Snowflake is explicitly not the seller of record. "Snowflake is not the seller of record of any Products" (§2.2). The provider carries tax collection, remittance, and reporting (§2.6, §3.9 Exh. A). Snowflake "will not determine whether any Taxes apply to a Transaction," though docs say it acts as a "marketplace facilitator" for US taxes where registered (provider-transactions-invoicing-collections). 1099/W-9/W-8 obligations are never mentioned.
- Payouts run through a Stripe Express connected account, contracted directly between provider and Stripe. "There is no additional cost to Providers for using the Stripe connected account." Payouts are "made 30 days after payment is received in full," and only after Snowflake collects. Net terms on the consumer invoice are set by the provider, so real cash timing is provider net terms + collection + 30 days. USD only; a US billing address is required for USD payouts. (provider-transactions-invoicing-collections, provider-becoming)
- Collections risk sits with the provider. Snowflake makes "a best-effort attempt to collect payment on the Provider's behalf"; "Providers are ultimately responsible for collecting payment" (provider-transactions-invoicing-collections). Snowflake may offset prior overpayments and disputed amounts (§3.6 Exh. A); the provider has no set-off right (§2.5 Exh. A).
- Marketplace sits outside the Service. Docs state "Snowflake Marketplace, including our on-platform monetization offering, is not part of the Service," while data sharing and listings are (collaboration-listings-legal). Inference, flagged as such: the plumbing is inside the Master Services Agreement (MSA), the storefront and payments layer is not, so MSA service levels and liability caps likely do not reach the monetization layer.
2. Listing requirements and cost to become a provider
Sources: provider-becoming, provider-listings-creating-publishing, provider-profiles-managing, provider-listings-workflows.
- Account: "You must use a full Snowflake account. Trial accounts can share data with specified consumers, but not on the Snowflake Marketplace." No Reader accounts. No required edition is documented — there is no Enterprise or Business Critical gate. The only edition restriction found: "VPS providers can't create paid listings" (Virtual Private Snowflake). So the entry ticket is a normal paying Snowflake account, not a premium tier.
- Roles: ACCOUNTADMIN or a role with provider privileges. Data listings need global
CREATE LISTING+CREATE SHAREplus OWNERSHIP of shared objects. ORGADMIN must accept the Provider and Consumer Terms. Note a sharp operational trap: "The role that attaches a data product to a listing and publishes the listing must be the same role that created, and therefore owns, the ... share," and "You can't transfer OWNERSHIP of a share." - Provider profile, created in Snowsight → Marketplace → Provider Studio → Profiles. Required fields: 256px square logo under 2 MB, company name, a 2-3 sentence description, business contact email, technical contact email, a public privacy-policy URL, a consumer contact email, and a support link or email. "Your provider profile must be approved before you can offer paid listings or marketplace listings." Stated turnaround: Snowflake "will review your profile and respond to you within approximately 1 business day."
- Paid listings add a human gate. "Contact your Snowflake business development partner or submit a case with Marketplace Operations ... This step is required for listing approval." Also required: a Stripe Express connected account and a billing address in a supported country.
- Listing review. "Every listing in the Snowflake Marketplace must go through the review and approval process." For a data share this is a metadata review, ~1 business day. Native Apps add an automated security scan, plus "approximately 3 business days" for manual security review if the scan fails, and reviews that "may take up to 14 days." Sample SQL must pass validation before submission. Public listings require at least one Business Need tag.
- Content restrictions. Providers "may not include any actual or synthetic Personal Data" in listing information; public listings "may not disclose or reveal any Sensitive Personal Data"; providers must describe personal-data types in their products and warrant lawful collection. Explicitly prohibited: duplicate or undistinguished listings, off-platform advertisements, and "practices to manipulate their position in the Marketplace discovery experience."
- Obligations after listing. There is no uptime or freshness service-level agreement (SLA) and no mandated refresh cadence. The real obligations are policy duties, and the one hard number is a support clock: providers "are expected to respond promptly, and respectfully" to inquiries "within three (3) business days," and degraded AI objects "must be remediated within 3 business days of being notified." Providers also may not "materially change their Products, including by removing core fields or significantly reducing the update frequency." Translation: once listed, you cannot quietly let it rot, and you owe a recurring inbox with a three-day clock.
- Documented limits: no more than 100 listings per provider; auto-fulfillment enforces a default 10 TB data-product size limit; after publishing a private listing you cannot change the associated share; "You cannot convert your share to a paid listing if your share has active consumers." No cap on consumer accounts is documented.
Cross-cloud and cross-region replication, who pays (provider-listings-auto-fulfillment, provider-understand-cost-auto-fulfillment). A listing visible in another region means the data is physically replicated there, into a Snowflake-managed secure share area (SSA), one per region per organization. The provider pays: "When you make a data product available in other regions, you incur additional costs" covering replication compute, duplicated storage, and cross-region egress. Crucially, "these usage costs are attributed to one Snowflake-managed secure share area for each region" under the provider's organization, not to the consumer's account. That is the opposite of manual replication, which bills the target account. Refresh intervals run from one minute to eight days and drive the compute bill. The Egress Cost Optimizer caches data for 15 days so that post-seed egress is charged only on updates. Business Critical is not required; Tri-Secret Secure on SSAs requires a support ticket. Auto-fulfillment is unavailable on trial accounts. Monitoring views: ORGANIZATION_USAGE.LISTING_AUTO_FULFILLMENT_USAGE_HISTORY and LISTING_AUTO_FULFILLMENT_REFRESH_DAILY.
3. Buyer discovery mechanics
Sources: consumer-listings-exploring, consumer-listings-access, provider-listings-managing, provider-listings-monitor-studio, plus the live public catalog measured 2026-10-16.
- Three surfaces: the public web catalog at
app.snowflake.com/marketplace(browsable signed-out), the same catalog inside Snowsight whereGet/Request/Buyactually fire, and SQL (SHOW AVAILABLE LISTINGS). The public catalog is fully client-rendered React; plain HTTP fetches return nothing. Organic search-engine discovery into the catalog should be treated as unproven. The documented off-platform traffic path is a provider-defined referral link that deep-links to the listing. - Taxonomy, measured live 2026-10-16: 30 categories, the largest being Financial (1,274 listings), Marketing (635), AI & ML (553), Geospatial (441), Health and Life Sciences (320). Cortex AI Ready carries 179; Cortex Knowledge Extensions 17. Buyers filter on availability (Instantly Accessible vs By Request), category, 36 Business Needs, geography, data time coverage, price (Free / Free to Try / Paid), provider, cloud region, legal terms, and an "Eligible for Marketplace Capacity Drawdown" toggle.
- Ranking is opaque and there is no paid placement. Sort options are exactly three: Most Popular (default), Most Recent, Title. How "Most Popular" is computed is not documented. No relevance sort is exposed. No Featured/Promoted/Sponsored placement product appears in docs, the monetization blog, or the UI, and manipulating discovery position is explicitly prohibited by policy. ("Featured objects" in Snowflake docs means something else: tables a provider flags inside their own data dictionary.) What is curated: mandatory human listing review, a hand-picked homepage carousel (on 2026-10-16: PolicyMap, LSEG, The Washington Post, SDG Group, Socialgist, Just Sentiment) with no documented selection process, and the Cortex AI Ready badge.
- Trial-led selling dominates the catalog. Live price-facet split on 2026-10-16: Free 972 · Free to Try 1,888 · Paid 791, summing to 3,651 of 4,315 public data products; the remaining 664 carry no price facet (by-request or unpriced listings). So of the listings that expose a price, ~52% are Free to Try, ~27% are Free, and ~22% are Paid-only — a trial-then-convert motion is the single commonest shape, and "Free to Try" listings monetize after the trial just as Paid ones do. Limited trials run 1 to 90 days and can be scoped by time or by data subset. Pre-commitment, a buyer can inspect the data dictionary, a Data Preview of up to 10 rows if the provider enables it, validated sample SQL, and optional view-only notebooks.
- The Request flow is a manual sales conversation. The consumer completes a contact form (Snowflake forces identity: users on free email domains must supply extra detail, and a consumer without profile contact info is blocked). The provider is emailed and sees the request in Provider Studio with the consumer's Snowflake region, company, contact information, and a free-text message. The provider then contacts them, negotiates, and hand-publishes a private listing. There is no documented decline path, request expiry, or SLA beyond the general 3-business-day policy duty. Note that self-serve paths exist alongside this: Instantly Accessible listings transact through
GetorBuywithout provider involvement. - Provider analytics, and the identity asymmetry. This is the sharpest mechanical finding.
LISTING_TELEMETRY_DAILY(views and clicks) is aggregate only — event counts, distinct account counts, region, no consumer-identifying column — andSNOWFLAKE_REGION = 'NONE'marks viewers not signed in to Snowflake at all, so part of your "views" is anonymous web traffic.LISTING_EVENTS_DAILY(get, request, trial, purchase, cancel, uninstall) is fully identified: consumer account locator, account name, organization, email, contact name, company name, terms-accepted date. Paid listings add earnings history, charges by type, trial counts, and purchase counts. Two constraints: "There can be up to two days of latency" on these views, and reading them requires a warehouse, so a provider pays credits to read their own analytics. Retention is 365 days. - Scale and revenue. Measured live 2026-10-16 from the public catalog API: 4,315 public data products, 1,123 provider profiles. Snowflake's own blog of 2026-06-30 reports over $100M in gross bookings earned by Marketplace partners between 2026-01-01 and 2026-06-16, up 277% year over year, across more than 1,700 transactions (snowflake-marketplace-agentic-ai-growth). The footnote defines gross bookings as consumer payments to providers, not Snowflake revenue. Company-reported listing counts from investor materials (secondary summaries, dated): 3,678 at Q4 FY2026, 3,971 at Q1 FY2027, 4,105 as of 2026-07-31. The live 4,315 is consistent with that secondary series.
4. The honest unit economics
This subsection is Ray's own model built on the sourced facts above, not web content. Every number below is an assumption, labeled as one. The take rate is unknown, so it is modeled as a sensitivity rather than asserted.
Assumed provider and product
- One curated dataset, 200 GB compressed, rebuilt and refreshed daily.
- Public Marketplace listing, Free to Try with a 30-day limited trial, then subscription at an assumed $1,500 per month.
- Assumed steady state after 12 months: 4 paying consumers, spread across 3 Snowflake regions beyond the home region. $6,000 per month gross bookings, $72,000 per year.
Assumed infrastructure costs. List prices are third-party-reported consensus for AWS US East and are not verified against Snowflake's own rate card — Snowflake's pricing page renders prices client-side and the authoritative Snowflake Service Consumption Table did not resolve to a fetchable document. Treat these as order-of-magnitude.
- Credits at ~$2.00 (Standard) to $3.00 (Enterprise) each; storage at roughly $23 per TB per month on a capacity contract, with some sources citing ~$40 on demand.
- Home-region storage, 0.2 TB: ~$5/month.
- Auto-fulfillment storage, 3 extra regions × 0.2 TB: ~$14/month.
- Cross-region egress: ~200 GB seed per region one-time, then an assumed 2 GB/day delta × 3 regions. At a nominal
$0.02/GB, that is **$12 one-time and ~$4/month** steady state, with the Egress Cost Optimizer suppressing re-seeding. - Build and auto-fulfillment refresh compute: assume 1 extra-small (XS) warehouse-hour per day, 30 credits/month: ~$60-90/month.
- Provider Studio analytics reads: assume a few credits per month, ~$5-10/month.
Assumed cash infrastructure total: roughly $90 to $125 per month, call it $1,100 to $1,500 per year. Against $72,000 of gross bookings that is 1.5% to 2%. The infrastructure tax on a small Snowflake Marketplace listing is not the problem.
Net to the provider, by take rate (gross $72,000/yr, infra $1,300/yr):
| Snowflake take rate | Snowflake's cut | Provider infra | Provider net cash |
|---|---|---|---|
| 0% (hypothetical floor) | $0 | $1,300 | $70,700 |
| 10% | $7,200 | $1,300 | $63,500 |
| 20% | $14,400 | $1,300 | $56,300 |
| 30% | $21,600 | $1,300 | $49,100 |
The spread between a 10% and a 30% take rate is $14,400 per year on this model, larger than every infrastructure line combined by a factor of ten. The one number Snowflake withholds is the one number that moves the answer most. Any plan built on this without logging in to read the fee schedule is built on a guess.
What the model leaves out, and why it dominates. None of the above prices the human. Curating and maintaining a dataset good enough to pass review and keep four enterprise consumers renewing is the real cost: source acquisition, daily pipeline babysitting, documentation that satisfies the "accurately describe the Products" policy, a support inbox on a 3-business-day clock, and a manual negotiation for every inbound Request. Add the accounts-receivable reality: the provider is seller of record, carries tax and collections risk, and is paid 30 days after Snowflake collects, on provider-set net terms. Assumption: 5 to 15 hours per month at steady state, more during the first year. That figure is a judgment call, not a sourced benchmark.
And the demand-side distribution is unknown. $100M of gross bookings across more than 1,700 transactions over five and a half months is a ~$59,000 mean transaction. Across the 2,679 public listings that can monetize (791 Paid plus 1,888 Free to Try) that is ~$37,300 per monetizable listing per half-year. Both figures are rough: the bookings window is Jan-Jun 2026 and also captures private listings, apps, and capacity-drawdown deals, while the listing counts are public listings measured on 2026-10-16. Different scopes, different dates. More importantly, no per-listing earnings distribution is published anywhere, and a mean cannot show a typical outcome. Financial alone holds 1,274 of 4,315 listings and the curated homepage carousel features institutional vendors such as LSEG and The Washington Post, which is suggestive of concentration but is not measurement. Do not read $37,300 or $59,000 as what a new small provider would earn.
Convergences and contradictions
- Convergence on the free-listing shape. [[2026-04-16-bq-to-snowflake-ga4-via-gard-connector]] recorded from the consumer side that a free Marketplace listing costs only warehouse credits plus source-side egress. The provider docs confirm the mirror image: free listings carry no transaction fee, and free private listings do not even require accepting the Provider and Consumer Terms. The vault's one piece of lived Marketplace experience generalizes correctly.
- Contradiction with the vault's founding thesis. [[2026-04-03-magic-of-small-databases]] frames the bet as "Substack for databases": low-ceremony self-publishing of small, opinionated datasets. Snowflake Marketplace is the inverse. Mandatory human review of every listing, a business-development gate on anything paid, a required public privacy policy, a 100-listing cap, a 3-business-day support duty, and a discovery layer with no relevance sort and no paid placement. It is an enterprise procurement rail with a catalog attached, not a self-serve publishing platform. A small-database publisher is structurally mismatched to it.
- Contradiction with the question's framing. The question asked whether the take rate "differs by listing type (free / paid / usage-based / auction-style)." There is no auction-style listing, and there is no documented "request a quote" listing type. The real taxonomy is free / limited-trial / paid / private / organizational, with "Request" being a lead-capture button rather than a transaction mode. The question assumed a richer commercial surface than Snowflake actually ships.
Synthesis for RDCO
On the data-marketplace bet: the answer is no, and the reason is not the infrastructure cost. That cost turns out to be trivially small. A 200 GB dataset replicated to three extra regions runs on the order of $100 a month to maintain, roughly 2% of a plausible $72,000 of annual bookings. If the question had been "does Snowflake eat the margin on a small listing," the answer would be a clean no. The binding constraints are elsewhere: a take rate nobody outside a Snowsight login can see, a per-listing earnings distribution that is entirely unpublished, and a workload shape that is poorly matched to the hours actually available.
The workload shape is decisive. Snowflake Marketplace is not a storefront you can leave unattended. Self-serve paths exist, and Get and Buy do transact without the provider in the loop, but custom or negotiated deals all arrive as a Request that emails a company name and a human's address and expects a reply, policy sets a 3-business-day response clock on every inquiry, paid listings require contacting a Snowflake business-development partner before approval, and view telemetry is anonymous and two days stale so the only actionable signal arrives already attached to a person who wants an answer. That is a recurring, inbound, time-bounded obligation. For a founder whose main bet is a full-time phData role, it collides with the same calendar phData owns. This is not the teaching-and-consulting conflict from 2026-09-23; a dataset is a product, not a service. It is a calendar conflict, and the three-day clock does not care which.
One carve-out is worth naming rather than burying. A free listing has materially different physics: no transaction fee, no Stripe account, no business-development gate, no collections or tax exposure, and if private, not even the Provider and Consumer Terms. The only residual obligations are compute and the support-response duty. If Snowflake Marketplace presence were ever wanted as a credibility artifact rather than a revenue line, that is the version that costs almost nothing. This is explicitly not a recommendation; it is the only door this research leaves open, and whether it conflicts with the phData no-selling rule is an open question listed below.
On phData domain knowledge: this is the more valuable half of the brief, and it is immediately usable. A Snowflake client asking "should we publish our data on the Marketplace" is a conversation a Data Solutions Architect (DSA) or Technical Account Lead (TAL) will have, and most of the answer is counterintuitive. Five facts carry weight. First, auto-fulfillment bills the provider, not the consumer: cross-region costs land in a Snowflake-managed secure share area under the provider's organization, the opposite of manual replication, and it is the cost surprise that will land in a client's bill. Second, no premium edition is required to be a provider; a full non-trial account is the whole prerequisite, and only Virtual Private Snowflake is blocked from paid listings. Third, the review gates are fast for data shares (about 1 business day on metadata) and slow for Native Apps (up to 14 days, with a 3-day manual security review if the automated scan fails), which should shape any accelerator packaging decision alongside [[2026-09-24-cortex-knowledge-extensions-vs-agent-publish]]. Fourth, the telemetry-versus-events identity split is an easy misreading: marketplace analytics is not a web-analytics funnel, it is anonymous above the fold and a full contact record below it, with two days of lag and a warehouse bill to read it. Fifth, the 100-listing cap and 10 TB auto-fulfillment default are limits worth knowing before an architecture is drawn. Carry the CKE number alongside these: 17 Cortex Knowledge Extension listings on a 4,315-listing catalog means supply is thin and buyer demand is unmeasured, so anyone proposing a CKE-based accelerator as a distribution play should be shown that denominator first.
Why this is in the vault
Closes the "Understand Snowflake marketplace economics" line item on [[01-projects/data-marketplace/index]] with a documented negative. Separately, it is the reference a phData DSA or TAL needs when a Snowflake client asks who pays for cross-region listing replication, which editions can publish, how long listing review takes, and what a provider can actually see about buyers.
Open follow-ups
- Snowflake publishes the Marketplace fee schedule only inside Snowsight (Admin → Billing & Terms → Fee). Is the rate flat, tiered by volume, or different between usage-based and subscription pricing plans, and is it visible to any account or only to approved providers?
- Is there any published or reconstructable distribution of earnings across Snowflake Marketplace providers, as opposed to the $100M aggregate? Public provider disclosures, Snowflake partner case studies with dollar figures, or filings from listed data vendors (LSEG, FactSet, Dun & Bradstreet) that break out Snowflake Marketplace as a channel would all serve.
- Snowflake's "Most Popular" default sort governs catalog-wide discovery and is entirely undocumented. Has any provider, partner blog, or Snowflake conference session described what feeds it (installs, queries, recency, views)?
- Does the "Cortex AI Ready" badge have published eligibility criteria, and does carrying it measurably change discovery position or install rate?
- Would a free Snowflake Marketplace listing have credibility value for phData sales, and does publishing one conflict with phData's no-clients-no-selling rule?
Related
- [[01-projects/data-marketplace/index]]
- [[2026-09-24-cortex-knowledge-extensions-vs-agent-publish]]
- [[2026-04-16-bq-to-snowflake-ga4-via-gard-connector]]
- [[2026-04-03-magic-of-small-databases]]
- [[2026-09-23-cortex-agent-cross-tenant-marketplace-publish]]
- [[2026-07-08-cortex-agent-cowork-skill-native-publish]]
- [[2026-09-11-phdata-snowflake-partnership-warm-start-map]] — the phData/Snowflake partner relationship this domain knowledge feeds
- [[2026-08-18-mostlymetrics-usage-based-pricing-one-way-door]] — usage-based vs subscription pricing, the same choice a Marketplace provider makes at listing time
- [[2026-06-20-bookstores-for-agents-2026-live-comps]] — the comparable question for agent/MCP marketplaces, where take rates are mostly published
Sources
Vault
~/rdco-vault/01-projects/data-marketplace/index.md~/rdco-vault/06-reference/research/2026-09-24-cortex-knowledge-extensions-vs-agent-publish.md~/rdco-vault/02-sops/2026-04-16-bq-to-snowflake-ga4-via-gard-connector.md~/rdco-vault/06-reference/2026-04-03-magic-of-small-databases.md~/rdco-vault/06-reference/research/2026-09-23-cortex-agent-cross-tenant-marketplace-publish.md~/rdco-vault/06-reference/research/2026-07-08-cortex-agent-cowork-skill-native-publish.md
Snowflake primary — legal and commercial
- https://www.snowflake.com/legal/snowflake-provider-and-consumer-terms/ (effective 2026-03-31)
- https://docs.snowflake.com/en/collaboration/collaboration-listings-legal
- https://docs.snowflake.com/en/collaboration/provider-transactions-invoicing-collections (the only page confirming a transaction fee exists)
- https://docs.snowflake.com/en/collaboration/provider-listings-pricing-model
Snowflake primary — provider requirements
- https://docs.snowflake.com/en/collaboration/provider-becoming
- https://docs.snowflake.com/en/collaboration/provider-listings-creating-publishing
- https://docs.snowflake.com/en/collaboration/provider-profiles-managing
- https://docs.snowflake.com/en/collaboration/provider-listings-workflows
- https://docs.snowflake.com/en/collaboration/provider-consumer-policies
- https://docs.snowflake.com/en/collaboration/collaboration-listings-about
- https://docs.snowflake.com/en/collaboration/provider-listings-auto-fulfillment
- https://docs.snowflake.com/en/collaboration/provider-understand-cost-auto-fulfillment
- https://docs.snowflake.com/en/collaboration/provider-listings-auto-fulfillment-eco
Snowflake primary — discovery and analytics
- https://docs.snowflake.com/en/collaboration/consumer-listings-exploring
- https://docs.snowflake.com/en/collaboration/consumer-listings-access
- https://docs.snowflake.com/en/collaboration/provider-listings-managing
- https://docs.snowflake.com/en/collaboration/provider-listings-monitor-studio
- https://docs.snowflake.com/en/sql-reference/data-sharing-usage
- https://docs.snowflake.com/en/sql-reference/data-sharing-usage/listing-events-daily
- https://docs.snowflake.com/en/sql-reference/data-sharing-usage/listing-telemetry-daily
Snowflake blogs (dated, company-authored)
- https://www.snowflake.com/en/blog/snowflake-marketplace-agentic-ai-growth/ (2026-06-30: $100M gross bookings, +277% YoY, 1,700+ transactions)
- https://www.snowflake.com/en/blog/marketplace-monetization-turn-data-apps-revenue-stream/ (2024-02-27)
Live measurement
- Public Snowflake Marketplace catalog and
pep.guest.v1.GuestServiceBrowse / ShowCategories API, measured 2026-10-16: 4,315 public data products, 1,123 provider profiles, price facets Free 972 / Free to Try 1,888 / Paid 791 (3,651 of 4,315; 664 carry no price facet), 30 categories.
Secondary, labeled as such — not verified against primary filings
- Investor-materials listing counts via third-party summaries: Investing.com, Q4 FY2026 = 3,678 · sergeycyw Substack, Q1 FY2027 = 3,971 · Yahoo Finance, Q2 FY2027 as of 2026-07-31 = 4,105 · TipRanks Marketplace-listings KPI tracker.
- Snowflake list prices (credits per edition, storage per TB) via third-party pricing guides. Snowflake's own pricing page renders prices client-side and did not yield figures; the Snowflake Service Consumption Table PDF did not resolve to a fetchable document. All dollar figures in the unit-economics section are order-of-magnitude, not rate-card verified.
- Snowflake's own product page (
snowflake.com/en/product/features/marketplace/) states "over 820 providers" and "more than 3,400 live" products. Undated and materially below the live catalog measured here, so it is recorded as stale and not used as a figure anywhere in this brief. - Explicitly not cited: an unsourced third-party claim of a "25-30% commission." No Snowflake-authored take-rate figure exists in public.