warehouse

Snowflake

Snowflake is a warehouse product that separates storage from compute. This profile covers what it does, how it is priced, and where it stops being the right choice.

What the product actually does

Snowflake is a cloud data warehouse with a separation between storage and compute. Data sits in object storage; queries run on virtual warehouses you size and start independently. That separation is the whole design: you can run a large warehouse for a heavy transformation job and a small one for a dashboard, concurrently, without either affecting the other.

The second property is that it is genuinely multi-tenant in the way it was designed for, not retrofitted. Workload isolation is a first-class concept rather than a configuration exercise, which is why it displaced on-premise warehouses so quickly.

How pricing works once you are inside

Snowflake bills credits for compute and a per-terabyte rate for storage. Credits are consumed per second while a warehouse is running, with a sixty-second minimum each time it starts. That minimum is the single most expensive detail in the pricing model: a warehouse that starts, runs a two-second query and shuts down bills a full minute.

The practical consequences are auto-suspend tuned to actual query cadence, right-sized warehouses rather than one large one for everything, and an alert on credit consumption before the monthly bill arrives. Teams that skip all three consistently spend two to five times what they need to.

Where it breaks down

Small, frequent queries. The per-start minimum makes an event-driven workload with hundreds of tiny queries a day disproportionately expensive. That workload belongs on a different system, and recognising it early saves a great deal of money.

Cost predictability is also genuinely difficult. Consumption-based pricing means the bill reflects behaviour, and behaviour changes as teams adopt the platform. Budget forecasts that assume a flat monthly cost are wrong within a quarter.

What switching costs

Moderate. SQL is close to standard and most models port, but Snowflake-specific features — stages, tasks, streams, the semi-structured data handling — do not. A mature Snowflake deployment uses enough of them that migration is a project.

Who should not use it

Teams with small data and predictable query patterns. The operational advantages appear at scale; below that a managed Postgres is cheaper and simpler.

Sources

Snowflake public documentation and pricing page, read October 2026. Credit consumption behaviour described from the vendor's own billing documentation.