# Snowflake Cost Optimization: Explained > How Snowflake spend breaks down across warehouse credits and storage, and how to cut it by scheduling warehouse suspend and resume, rightsizing, and consolidation. Source: https://zop.dev/learn/snowflake-cost-optimization Published: 2026-07-01 · Author: avinash-gaurav · Tags: zopnight, learn --- Snowflake cost splits into compute, storage, and cloud-services. Compute is billed in credits for every second a virtual warehouse runs, and in non-production most of those credits are spent between queries while nobody is working. That makes warehouse scheduling the most direct Snowflake cost lever, ahead of storage cleanup and structural rightsizing. This guide keeps the theory short and spends most of its length on what you can actually do. Every recommendation here is one ZopNight can help you execute, starting from a read-only connection. ## Where Snowflake cost comes from Warehouses bill credits per second of runtime by size and edition, independent of the data they touch. Storage bills on active bytes per table. Left running between queries, a non-production warehouse keeps burning credits for no productive work, which is why idle compute is the first place to look. ## Schedule warehouses to your hours A virtual warehouse can suspend and resume independently of storage. Scheduling a [warehouse](https://zop.dev/zopnight/snowflake/warehouse) to SUSPEND outside working hours and RESUME before the team needs it removes the credits you were spending on nights and weekends, with no effect on stored data. Auto-suspend timeouts help, but a schedule stops the warehouse for the whole off-hours window instead of paying the timeout every evening. ## Rightsize and consolidate Beyond scheduling, warehouses are often larger than their query load needs or split when they could be consolidated. Resizing up or down to match real usage, setting multi-cluster minimum and maximum limits, and consolidating overlapping warehouses all remove structural waste. Resource monitors and tag guardrails keep the savings from drifting back. ## How ZopNight helps ZopNight connects Snowflake as a standalone account over key-pair JWT or a personal access token, discovers nine object types from ACCOUNT_USAGE and SHOW queries, and schedules warehouse suspend and resume alongside your cloud resources. Snowflake recommendations flag idle warehouses, resizing, multi-cluster limits, auto-suspend and resource-monitor guardrails, and storage cleanup on tables, materialized views, stages, and pipes. ## Key takeaways - Warehouse credits, not storage, are the fastest Snowflake lever. - Suspend and resume warehouses on a schedule to stop idle compute. - Rightsize, consolidate, and set auto-suspend and resource-monitor guardrails. - ZopNight connects standalone and schedules warehouses like any cloud resource. ## Where ZopNight fits ZopNight turns this from reading into doing. It ships 490 built-in audit rules across AWS (216), GCP (127), and Azure (147), 124 of those recommendations are wired to act end to end, 28 one-click and 96 guided, and it starts read-only so you can see the opportunity before you act on any of it. The most direct place to begin is scheduling non-production resources to your working hours, which is covered in the [FinOps](https://zop.dev/learn/finops) guide and shown concretely for [AWS EC2](https://zop.dev/zopnight/aws/ec2). ## How ZopNight schedules non-production resources The loop that does this is deliberately mechanical, and it starts read-only. You connect your cloud provider with a read-only role, and ZopNight discovers every non-production resources across your regions and accounts. It records a per-action permission verdict for each one, so you can see where it can list a resource but not yet stop it, and you review that inventory, filter it by status or type, and search for the specific resources you care about before anything is scheduled. Scheduling itself is a cron you write once in plain terms, stop at 7 PM, start at 8 AM on weekdays, pinned to your timezone so the jobs fire at local business hours rather than UTC. A weekly 24-hour grid shows the schedule visually so you catch gaps and overlaps before you save, and an estimate of active versus inactive hours appears before you commit. Resources attach individually or bundle into groups like "dev-cluster" or "staging-db" so a whole environment follows one cadence. Actions run in dependency order, so a database comes up before the app server that depends on it. When something needs to stay up, an override forces a non-production resources ON or OFF for a defined window, carries a reason so teammates understand why it exists, and expires automatically so nothing is left running by accident. If a start or stop fails, ZopNight retries up to three times and falls back to a dead-letter queue rather than silently dropping the action, and every state change lands in an audit trail that records whether a schedule, an override, or a specific user triggered it. ## Getting started Getting started is intentionally low-stakes: - Connect your cloud provider with a read-only role. Nothing is scheduled or changed at this stage. - Let ZopNight discover your non-production resources and review exactly what it found, filtered by account, region, and status. - Create a schedule in your timezone and attach the non-production resources or groups you want it to cover. - Watch the first cycle run, with Slack, Teams, or Google Chat notifications on every start, stop, and failure, then layer in idle cleanup and guided rightsizing. Production stays excluded by default throughout, and because discovery and recommendations are read-only, you can prove the value before you enable a single action. ## Frequently asked questions ### Does scheduling a warehouse affect stored data? No. Suspend and resume act on compute only; databases, tables, and query history are untouched. ### How does ZopNight connect to Snowflake? As a standalone account authenticated by key-pair JWT or a personal access token, reading usage from SNOWFLAKE.ACCOUNT_USAGE.