Snowflake Marketplace
Snowflake Marketplace works differently from the hyperscaler marketplaces: what you sell is a data product or an application, your customers are called consumers, and they are identified by a Snowflake account identifier rather than a cloud account or tenant ID. Becoming a provider is a prerequisite you complete in Snowflake before Suger is involved — you need a full Snowflake account (trial and reader accounts cannot list), the ACCOUNTADMIN role or a role with provider privileges, and the accepted Provider and Consumer Terms.
There is one more step here that the other marketplaces do not have: a provider profile representing your company must exist before you can publish any paid listing. Suger connects to your Snowflake account with key-pair authentication, then manages listings, pricing plans, private offers, usage reporting, and revenue from the console.
The path to your first Snowflake sale
- Integration — confirm your account qualifies as a provider, generate a key pair, and connect with your account, user, and private key.
- Provider Profile — the company identity consumers see, including the consumer contact address Snowflake expects you to answer within 24 hours.
- Pricing Plan — usage-based and subscription-based plans, and the per-query, monthly-fee, and billable-event charging options behind them.
- List Product — create the listing in Provider Studio and decide whether it is public on the Marketplace or shared with specified consumers only.
- Create Private Offer — discount a published pricing plan for one consumer, or charge a flat one-time contract value with optional installments.
After a consumer subscribes
- Usage Metering Upload — report consumption for many entitlements at once by uploading a CSV, with a validation preview before anything is submitted.
- Revenue — how Suger joins Snowflake’s invoice and disbursement provider views by invoice number so billed amounts, fees, and payouts line up with your other channels.
Scope and limits
Spotted something wrong or out of date on this page? Tell us and we'll correct it.