Reader Accounts
A reader account is a Snowflake account the provider creates and owns, on behalf of a consumer who has no Snowflake account of their own. It can only read data shared by the provider that created it, can't load or change data, and the provider pays its compute.
The IsmaFrost version: a retail partner with no Snowflake account needs weekly sell-through data. Youness creates a reader account, adds it as a consumer on the share, creates one small warehouse and one login inside it, and hands the partner a URL. The partner queries live data in a browser; every credit their queries burn lands on IsmaFrost's bill, which is also why the warehouse Youness gave them is an X-Small with AUTO_SUSPEND = 60 and a resource monitor of its own. One reader account per partner, never a shared one, so revoking a relationship is one drop, not a password rotation for everyone.
PROVIDER · ISMAFROST
READER ACCOUNT
SHARESALES_
DATABASE FROM SHARESHARED_
STATEMENTCREATE MANAGED ACCOUNT … READER
createsqueries
COSTPays reader creditson the IsmaFrost bill
billedWAREHOUSEREADER_WHcreated by provider
created, owned and paid by IsmaFrost
signs in
CONSUMERPartnerno Snowflake account
Read-only: no loading, no DML. One reader account per external organization.
A sound design for an unknown mix of Snowflake and non-Snowflake consumers: give each non-Snowflake consumer its own reader account rather than pooling unrelated parties in one, because a shared reader account mixes their billing, isolation and access. A reader account lives in the provider's region. For a consumer in another region or cloud, replicate the database and the share to an account you own in that region and share from there, or publish a listing with Cross-Cloud Auto-Fulfillment.
Reader accounts are billed to the provider, not the reader. A scenario proposing that the consumer pays their own reader-account compute is always wrong; that defeats the entire "no Snowflake account needed" pitch to a non-Snowflake customer.

