What this is
Bond publishes your organization's data as a live, read-only Snowflake share. Once enabled, 12 views in the ANALYTICS_SHARED schema appear as a database inside your Snowflake account and refresh automatically as your data updates, typically within minutes. There is no ETL job to build, no daily file to manage, and no extra fee from Bond.
Bond's Snowflake account is hosted on AWS US East (Ohio), region code us-east-2. This only matters in one specific case: if you are unloading data to your own cloud storage (S3/GCS/Azure Blob) on the way to a non-Snowflake platform, a same-region bucket avoids egress fees and a cross-region one adds a small fee.
Does this apply to you?
If your data lives in… | How you access Bond data | What you pay |
Snowflake (any cloud, any region) | The share appears as a database in your account. Query it directly, no copy required. Cross-region or cross-cloud customers are handled by Snowflake's built-in replication, set up on Bond's side. | Nothing to Bond, and no storage charge for the shared data. You pay your own Snowflake compute for the queries you run against the share. |
Another platform (Redshift, BigQuery, Databricks, a BI tool's native connector) | You need a daily copy of the data landed in your destination. | Your own Snowflake compute to unload it. See the cost matrix below, typically $1–$30/month. |
Where the compute lands. In both rows above, the queries run in your Snowflake account, so the compute is billed to you at your own credit rate. The alternative is a Reader account that Bond provisions on our side: you can query the shared data but cannot load or add data of your own, and the compute is billed to Bond. Having your own Snowflake account is the more flexible option and the one we recommend.
How to enable the share
Setup is the same regardless of which row above describes you. The share is the entry point in both cases. Your Bond CSM handles our side; this section covers what we need from you and what you will run on yours.
1. Make sure you have a Snowflake account
Any Snowflake edition works. Standard is the entry-level consumption tier and is more than enough for accessing the share. If you do not have an account yet, sign up at signup.snowflake.com. Choose AWS, and if you are creating an account specifically to access Bond data, pick us-east-2 (Ohio) to keep things simple.
2. Send your CSM two pieces of information
Your Snowflake account identifier in
ORG_NAME.ACCOUNT_NAMEformYour Snowflake account locator (for example
AB12345). We need this to add your account to the share.
You can find both by running this in your Snowflake account and sending your CSM the result:
SELECT
CURRENT_ORGANIZATION_NAME() || '.' || CURRENT_ACCOUNT_NAME() AS account_identifier
, CURRENT_ACCOUNT() AS account_locator;
Your CSM will reply confirming your account has been added to the share. You can then move on to step 3. No further information is needed from us.
3. Create the database from the listing
Bond's listing ID is GZT1Z25AYVC. Run this once in your Snowflake account:
SHOW AVAILABLE LISTINGS;
CREATE DATABASE bond_data FROM LISTING 'GZT1Z25AYVC';
You can name the database whatever you like. bond_data is just a suggestion.
4. Query the share to confirm it is working
The shared views live in the ANALYTICS_SHARED schema. Each view is automatically filtered to your organization, so there is no need to add WHERE organization_id = filters. For every column definition, see ANALYTICS_SHARED.
SELECT * FROM bond_data.ANALYTICS_SHARED.CUSTOMERS LIMIT 10;
5. Grant access to your team
GRANT IMPORTED PRIVILEGES ON DATABASE bond_data TO ROLE your_analytics_role;
The share refreshes automatically as Bond's data updates, typically within minutes.
If you see "Shared data not available" right after creating the database, especially if your Snowflake account is in a different region from ours, give it 10–30 minutes for replication to complete. If the error persists, reach out to your Bond CSM and we will work with Snowflake support to resolve it.
If you are already on Snowflake, you can stop reading here. The data is in your warehouse the moment your CSM grants the share. There is no ETL, no movement, no daily job, and no fee from Bond, even if your account is on a different cloud or region than ours. The rest of this guide covers the second scenario only: moving a copy to a non-Snowflake platform.
The short answer on cost
For the "moving a copy to another platform" case: a full daily export of your Bond data costs a few cents per day in Snowflake compute, typically $1–$30 per month, depending on your size and how you run it. There are no storage charges on shared data and no Bond-side fees.
You are paying for two things only:
Compute (credits). Every time you query or unload from the share you spin up a virtual warehouse. Snowflake bills per second with a 60-second minimum each time the warehouse resumes.
Egress. Only if the destination is in a different cloud region from Bond's (
us-east-2). Same-region unloads are free.
You do not pay for storage of the shared tables (Bond pays this), a Snowflake Enterprise tier (Standard On-Demand is enough), or anything to Bond. The share itself is included with your Bond plan.
How much data is "all of it"?
The 12 shared tables grow roughly in proportion to your customer count and transactional activity. Here is what a daily full export looks like across three reference sizes:
Org size | Customers | Rows / day | Uncompressed | Compressed |
Small (single facility) | ~5,000 | ~360,000 | ~580 MB | ~80–130 MB |
Medium (established multi-program) | ~20,000 | ~1.5 million | ~2.5 GB | ~350–500 MB |
Large (multi-facility enterprise) | ~75,000 | ~3.7 million | ~5.7 GB | ~800 MB–1.2 GB |
By a wide margin the biggest contributor is ACTIONS, a transactional ledger recording every revenue, payment, and deferred-revenue event for your organization, used for financial reconciliation and reporting. It accounts for roughly two-thirds of total volume at every size. Because it is transactional, pulling only new and changed rows each day shrinks it dramatically (see Tips below). Organizations with heavy membership billing or payment-plan-heavy programs can run 3–5× larger than the averages above.
Three ways to run it
Pick one approach. Your monthly cost depends on which one you use and how much data your organization generates.
Same-region unload. A scheduled
COPY INTO @stagedrops CSV or Parquet files into your S3, GCS, or Azure Blob bucket, in the same cloud region as Bond's Snowflake account.Cross-region unload. Same idea, but the destination is in a different cloud or region (adds a small egress fee).
JDBC / ODBC connector. An off-the-shelf tool (Fivetran-style, a BI tool's native connector, a custom script) pulls rows over the wire. Easiest to set up; the warehouse stays running longer.
Estimated monthly Snowflake cost
Approach | Small (~5k cust.) | Medium (~20k cust.) | Large (~75k cust.) |
Same-region unload | $1–$2 | $3–$5 | $6–$10 |
Cross-region unload | $1–$3 | $3–$6 | $7–$12 |
JDBC / ODBC connector | $4–$8 | $10–$20 | $20–$40 |
The small tier is still essentially floored by Snowflake's 60-second warehouse minimum. At that volume you are paying for the warm-up, not the work. Medium and large costs scale primarily with how much of the ACTIONS ledger needs to move each day, which is why an incremental approach cuts these numbers further.
Organizations with unusually heavy transactional volume (very large membership bases on payment plans, very high event throughput) can land 2–3× higher than the figures above. At the extreme high end, roughly 20 GB/day on ACTIONS alone, plan for ~$25–50/month on same-region unloads, or reach out to your Bond CSM for a tailored estimate.
Tips to keep your bill minimal
Use a single X-Small warehouse for daily exports. Anything bigger is wasted on this volume.
Run all tables in one session so you pay the 60-second warehouse minimum once, not twelve times.
Set auto-suspend to 60 seconds on the export warehouse.
Go incremental on
ACTIONS. Filter onACTION_TIME >= DATEADD(day, -1, CURRENT_DATE()).ACTIONSis two-thirds of your volume; pulling only new and changed rows can cut total daily bytes by 5–10× and meaningfully reduce medium- and large-tier compute. For the other 11 tables, filter on_UPDATED_AT.Co-locate your Snowflake account in the same cloud region as Bond's if you have a choice. This eliminates egress entirely.
What this guide does not cover
Costs of the destination platform (your warehouse, BI tool, or third-party connector vendor)
Ad-hoc analytics workloads. These are typically much larger than a daily export, and cost depends on how heavily your team queries the data.
One thing to double-check: Snowflake's per-credit pricing varies slightly by cloud, region, and edition. The numbers in this guide assume Standard Edition On-Demand on AWS US East (Ohio) at $2.00/credit. Your effective rate may be a few cents higher or lower.
Have questions about your specific volume or setup? Reach out to your Bond CSM and we will size it for your organization.