Free tool

What will your warehouse cost a month?

Describe the workload — how much data, how many scheduled jobs, how often the dashboards refresh, how much analysts query — and get a monthly estimate for BigQuery, Snowflake and Redshift Serverless at each vendor’s list price, broken down by where the money goes.

Data
Scheduled transforms
BI dashboards
Ad-hoc analysis
Assumptions you can change

Scan speed is for an X-Small Snowflake warehouse, and 8 Redshift RPUs are assumed to scan as fast. Both are assumptions, not vendor figures: the bigger sizes are taken to be proportionally faster, and your own query history is the real answer.Measure yours from query history →

This is a list-price estimate, not a quote. Real bills depend on discounts, committed-use contracts and the shape of your queries — partitioning, caching and clustering change how much each query scans. Your inputs never leave this browser. They are only copied into the part of the page address after the #, which browsers do not send anywhere, so you can share the result.

Want a starting point? See three worked workloads, side by side, each of which opens back here with its inputs filled in.

Method

How it is calculated

A month is 365 ÷ 12 days. Scheduled jobs and dashboard refreshes run every day; ad-hoc queries run on working days, five in seven. 1 TB is 1,024 GB, the way BigQuery bills.

What gets scanned

  • Scheduled transforms = jobs per day × GB per run × days.
  • BI refreshes = (1,440 ÷ refresh minutes) × dashboards × GB per refresh × days.
  • Ad-hoc = queries per working day × GB per query × working days.

BigQuery, on demand

  • Compute = TiB scanned × $6.25, less the first 1 TiB a month, which is free.
  • Storage = GiB stored, less 10 free, × $0.023 at the high end. The low end prices only the last three months of growth at that rate and the rest at the long-term $0.016, because tables untouched for 90 days are billed for less. Tables a full rebuild rewrites stay on the active rate, so the more of your data is rebuilt, the closer the real figure sits to the high end.

Snowflake

  • Work in credits = GB scanned ÷ (scan speed × 60). One size up doubles both the credits an hour and the speed, so the work costs the same at every size.
  • Every time a warehouse wakes it bills at least 60 seconds, then the auto-suspend time before it sleeps. Size changes what that costs. The low end runs the day’s jobs as one batch and lets ad-hoc queries land on a warehouse that is already awake; the high end wakes it for each job and each query, but never bills more than one warehouse running all day. Dashboards wake it once per refresh.
  • Compute = credits × the edition’s price per credit. Storage = TB × $23.00. Snowflake bills compressed bytes, so if your figure is uncompressed, storage will come in lower.

Already on Snowflake and want the warehouse settings priced rather than the workload? Model your Snowflake warehouses one by one: size, Gen 1 or Gen 2, clusters, auto-suspend and the idle time it bills.

Redshift Serverless

  • Work in RPU-hours = GB scanned ÷ (scan speed × base RPUs ÷ 8) ÷ 60 × base RPUs, billed per second with a 60-second minimum per run and no idle time. The low and high ends batch and split the runs the same way as for Snowflake, with the same all-day ceiling.
  • Compute = RPU-hours × $0.375. Storage = GB × $0.024.

The “what if” line

It reruns the same estimate with the scheduled rebuilds made incremental, at the share of a full run you set, and the dashboards refreshing half as often. Those are the two leverswhere your warehouse spend actually goes ranks first after deleting what nobody uses. The twelve-month line grows storage and every scan by the monthly growth rate, compounded.

Not included: Snowflake cloud services (not billed below 10% of daily compute), BigQuery minimum bytes per query and cache hits, data transfer, and anything outside the warehouse. Snowflake Gen 2 standard warehouses use more credits an hour on AWS than the Gen 1 sizes used here.

Sources

Rates used

PlatformItemList price (USD)Applies toChecked
BigQueryOn-demand queries$6.25 per TiB scannedUS multi-region and US regions; the first 1 TiB each month is free2026-10-11
BigQueryOn-demand free tier1 TiB scanned per month freePer billing account2026-10-11
BigQueryStorage free tier10 GiB stored per month freePer billing account, logical or physical storage2026-10-11
BigQueryActive logical storage$0.023 per GiB-monthus-central1; tables modified in the last 90 days2026-10-11
BigQueryLong-term logical storage$0.016 per GiB-monthus-central1; tables not modified for 90 days2026-10-11
SnowflakeCredit, Standard edition$2.00 per creditOn demand, AWS US East (Northern Virginia)2026-10-14
SnowflakeCredit, Enterprise edition$3.00 per creditOn demand, AWS US East (Northern Virginia)2026-10-14
SnowflakeCredit, Business Critical edition$4.00 per creditOn demand, AWS US East (Northern Virginia)2026-10-14
SnowflakeStorage$23.00 per TB-monthOn demand, AWS US East (Northern Virginia); billed on compressed size2026-10-14
Redshift ServerlessServerless compute$0.375 per RPU-hourUS East (N. Virginia); per second, 60-second minimum; base capacity 4–1024 RPUs2026-10-11
Redshift ServerlessManaged storage$0.024 per GB-monthUS East (N. Virginia)2026-10-11

Snowflake warehouse sizes, credits per hour: XS 1 · S 2 · M 4 · L 8 · XL 16 · 2XL 32 · 3XL 64 · 4XL 128. Same source as the Snowflake rates.

Questions

About the estimate

Why is this a range?

BigQuery on demand bills bytes scanned, so its compute is a single figure; only storage ranges, between everything at the active rate and only recent data at it. Snowflake and Redshift bill compute time, and how fast your queries run is not something a list price can tell you. The range spans the scan speeds set under the assumptions, and the difference between batching work and waking the warehouse for every job.

Does it include discounts?

No. Every rate is the vendor’s published on-demand list price for one region. Committed-use and capacity contracts, editions bought through a marketplace, negotiated rates and credits are all left out, so a large account will usually pay less than this for the same work.

Where do the rates come from?

From the vendors’ own pricing pages: Google Cloud’s BigQuery pricing page, Snowflake’s credit consumption table and AWS’s Redshift pricing page. Each rate on this page links to its source and shows the date it was last checked against it.

Want the real number instead?

Your query history knows exactly where the bill goes. Describe your stack in a few lines and you will get a straight answer about whether an audit would pay for itself.

The current situation and what "solved" looks like is enough. Detail can wait for the call.

Tell me what is broken.

A short call is usually enough to tell whether this is a two-week fix or a two-month one — and whether I am the right person for it.