Account & Warehouse Design
Org → account → role hierarchy designed for clarity. Per-workload warehouses sized to query mix, not vibes.
Org · Account · WH sizingSnowflake's killer idea was simple: separate compute from storage so each scales on its own clock. We build warehouses that exploit that idea ruthlessly — multi-cluster for concurrency, sized for the workload, governed at the column.
We treat Snowflake credits like any other production budget: instrumented, alarmed, owned by a person.
Org → account → role hierarchy designed for clarity. Per-workload warehouses sized to query mix, not vibes.
Org · Account · WH sizingContinuous Snowpipe ingestion, change streams for incrementality, dynamic tables where they earn it. Replayable, idempotent, observable.
Snowpipe · Streams · Tasks · Dynamic TablesPython in the warehouse for feature engineering and model inference. Cortex for the LLM use cases that live next to your tables.
Snowpark · Cortex · MLColumn-level masking, row-access policies, classification, native tag-based propagation. Audit-grade access without bottlenecking analysts.
Masking · Row access · Tags · HorizonIceberg tables for the workloads that need open formats. Native Snowflake sharing for partners. Both, designed without duplicating the lake.
Iceberg · Secure SharingResource monitors, query timeouts, warehouse auto-suspend, scheduled review of the top-10 cost queries. The bill stops being a quarterly surprise.
Resource monitors · Query timeouts · TaggingA clean account is the cheapest performance win in the warehouse. We start there.
Most Snowflake bills are paying for sprawl — overlapping warehouses, the same dashboard hitting four different schemas, ad-hoc queries from the largest cluster the user can grab. We collapse the sprawl on day one.
Roles map to job-to-be-done. People come and go; the role hierarchy stays.
BI, ELT, Data Science, ad-hoc — each on the warehouse sized for it, monitored independently.
Hard caps and notifications. Cost surprises become cost conversations.
Declarative pipelines without orchestrating tasks by hand. Refresh policy a deliberate decision.
Snowflake ships a lot. We've put each of these in production and have an opinion.
Three quick takes.
Right-sized warehouses, multi-cluster only where concurrency demanded, resource monitors on every workload, query timeout discipline.
Streaming ingestion with sub-minute latency, dynamic tables for incrementality, dashboards always within 90 seconds of reality.
Secure Sharing for de-identified analytical sets, row-access policies per partner, full audit. Zero data movement, full control.
30 minutes. Bring last month's credit usage; we'll point to the top three places the bill is leaking — for free.