Skip to main content

FrostWatch cover

FrostWatch logo

❄️ FrostWatch

Snowflake cost monitoring shouldn't cost more than the savings.

CI PyPI Python 3.11+ Docker License: MIT GitHub Sponsors GitHub Stars

FrostWatch is an open source, self-hostable, AI-powered cost and query observability tool for Snowflake. Point it at your Snowflake account and get instant answers to "where is all our money going?" - no SaaS contract, no percentage-of-spend pricing, no phone-home.

FrostWatch Dashboard

Cost breakdown by warehouse, anomaly detection, and AI-powered explanations, all in one dashboard.

Anomalies Query Explorer
Anomalies Query Explorer

Try it in 30 seconds (no Snowflake needed)

pip install frostwatch
frostwatch demo
# → open http://localhost:8000

frostwatch demo seeds the local database with 35 days of realistic synthetic data - warehouse cost trends, dbt model breakdowns, injected anomaly spikes, AI explanations, pre-baked query rewrites, and a weekly digest - so you can explore the full UI before connecting a real Snowflake account.

What it does

  • Cost breakdown by warehouse, user, role, and query tag - updated on a schedule you control
  • Anomaly detection that flags unusual spend spikes against a rolling 21-day baseline
  • Plain-English explanations of anomalies and expensive queries, powered by your own LLM (Anthropic, OpenAI, Gemini, or a local Ollama model)
  • Query fingerprinting - group near-identical queries by SQL pattern, surface the patterns that drive the most spend
  • Week-over-week regression detection - automatically flag query patterns that became more expensive this week vs last (medium / high / critical severity)
  • Cost forecasting - per-warehouse credit projections for the next 1–30 days using linear regression on historical data
  • AI query rewrites - submit any expensive query to your LLM and get back optimized SQL, root-cause analysis, clustering recommendations, and estimated savings %
  • dbt model attribution - per-model credit and performance breakdown parsed from query_tag
  • dbt Cloud integration - sync run metadata from dbt Cloud; cost breakdown by job and environment; model spend threshold alerts; manifest.json enrichment (owner, description, materialization, tags)
  • GitHub Actions - built-in workflow to post dbt cost summaries as PR comments after every dbt run
  • Resource monitor management - sync existing monitors, recommend quota sizes using p95 spend analysis, generate copy-paste CREATE RESOURCE MONITOR DDL, alert when monitors approach their limits
  • Budget tracking - configurable per-user and per-role daily credit budgets with over-budget flagging
  • Weekly digests delivered to Slack or email
  • Clean web UI - dark-themed React dashboard, no BI tool required
  • REST API - all data accessible via /api/* endpoints
  • CLI - sync, config, and server management from the terminal

Quickstart

# 1. Copy and edit the config
curl -O https://raw.githubusercontent.com/arunrajiah/frostwatch/main/frostwatch.yaml.example
cp frostwatch.yaml.example frostwatch.yaml
# Edit frostwatch.yaml with your Snowflake credentials and LLM API key

# 2. Start
docker compose up -d

# 3. Open the UI
open http://localhost:8000

Option B - pip

pip install frostwatch

# Initialize config
frostwatch config init
# Edit ~/.frostwatch/config.yaml with your credentials

# Start the server
frostwatch serve

Option C - from source

git clone https://github.com/arunrajiah/frostwatch
cd frostwatch

# Install Python package in editable mode
pip install -e ".[dev]"

# Build the frontend
cd frontend && npm install && npm run build && cd ..

# Initialize config
frostwatch config init

# Run
frostwatch serve --reload

Configuration

All config lives in ~/.frostwatch/config.yaml. Every field can also be set via environment variable with the FROSTWATCH_ prefix.

snowflake_account: "xy12345.us-east-1"
snowflake_user: "FROSTWATCH_USER"
snowflake_password: "your_password"
snowflake_role: "ACCOUNTADMIN"       # needs SELECT on ACCOUNT_USAGE

llm_provider: "anthropic"            # anthropic | openai | gemini | ollama
llm_api_key: "sk-ant-..."

slack_webhook_url: "https://hooks.slack.com/services/..."
email_recipients: ["ops@example.com"]

schedule_cron: "0 8 * * 1"          # weekly digest - Monday 8am
sync_cron: "0 */6 * * *"            # data sync - every 6 hours
credits_per_dollar: 3.0              # adjust for your Snowflake contract rate
snowflake_query_limit: 500           # queries fetched per sync

See frostwatch.yaml.example for the full reference.

Snowflake permissions

FrostWatch only reads from SNOWFLAKE.ACCOUNT_USAGE. The minimum required grant:

-- Create a dedicated role (recommended)
CREATE ROLE frostwatch_role;
GRANT IMPORTED PRIVILEGES ON DATABASE SNOWFLAKE TO ROLE frostwatch_role;
GRANT ROLE frostwatch_role TO USER your_user;

The ACCOUNTADMIN role already has this access. No data is ever written to Snowflake.

LLM providers

Provider llm_provider Default model
Anthropic (Claude) anthropic claude-sonnet-4-6
OpenAI openai gpt-4o
Google Gemini gemini gemini-2.0-flash
Ollama (local) ollama llama3 - set llm_base_url to your Ollama server

FrostWatch is BYO-LLM. Your data never passes through a hosted proxy - it goes directly from your server to the LLM provider using the API key you supply.

CLI reference

frostwatch demo              Seed synthetic data and start server - no Snowflake needed
frostwatch serve             Start the web server (default: http://localhost:8000)
frostwatch serve --reload    Start with auto-reload for development
frostwatch sync              Run a one-off Snowflake sync
frostwatch config init       Create ~/.frostwatch/config.yaml from the example
frostwatch config show       Print current config (secrets masked)
frostwatch version           Print version

API

The REST API is available under /api. Interactive docs are at http://localhost:8000/docs when the server is running.

Key endpoints:

Method Path Description
GET /api/dashboard Cost summary + recent anomalies
GET /api/queries Top queries by credit usage
GET /api/warehouses Per-warehouse cost aggregates
GET /api/anomalies Detected anomalies with LLM explanations
GET /api/dbt Credit + cost breakdown by dbt model
GET /api/insights/fingerprints Top query patterns by total credits
GET /api/insights/regressions Query patterns that regressed week-over-week
GET /api/insights/forecasts Per-warehouse cost projections (7-day)
GET /api/insights/pruning Query patterns with poor partition pruning
POST /api/insights/rewrites Request an AI rewrite for a query
GET /api/insights/rewrites/{query_id} Fetch a previously generated rewrite
GET /api/dbt/runs dbt Cloud runs with cost attribution
GET /api/dbt/jobs Cost breakdown by dbt Cloud job
GET /api/dbt/environments Cost breakdown by dbt Cloud environment
GET /api/dbt/threshold-alerts Models that exceeded daily credit threshold
GET /api/dbt/metadata Enriched model metadata from manifest.json
POST /api/dbt/sync-cloud Sync run metadata from dbt Cloud API
POST /api/dbt/manifest Upload and parse a dbt manifest.json
GET /api/resource-monitors Synced Snowflake resource monitors
GET /api/resource-monitors/recommendations Quota recommendations per warehouse
GET /api/resource-monitors/generate-sql Copy-paste DDL for a warehouse
GET /api/resource-monitors/proximity-alerts Monitors near their credit limits
GET /api/resource-monitors/budgets Per-user and per-role spend vs budget
POST /api/sync Trigger a manual Snowflake sync
GET /api/settings Current configuration
PUT /api/settings Update configuration
POST /api/settings/test-snowflake Test Snowflake connectivity
POST /api/reports/generate Generate an AI cost report

Architecture

┌─────────────┐     read-only     ┌──────────────────────────────────┐
│  Snowflake  │ ◄───────────────  │  frostwatch serve                │
│ ACCOUNT_    │                   │                                  │
│ USAGE views │                   │  FastAPI + APScheduler           │
└─────────────┘                   │  ├── /api/*  (REST)              │
                                  │  └── /       (React SPA)         │
┌─────────────┐                   │                                  │
│  LLM API    │ ◄───────────────  │  SQLite  (local cache + history) │
│ (your key)  │                   └──────────────────────────────────┘
└─────────────┘

FrostWatch runs entirely inside your infrastructure. The only outbound calls are to Snowflake and your chosen LLM provider.

Roadmap

See ROADMAP.md.

Sponsors

FrostWatch is free, MIT-licensed, self-hosted, and solo-maintained. It runs on your infrastructure with your LLM key - no SaaS contract, no percentage-of-spend pricing, no phone-home.

For data teams running FrostWatch in production: sponsorship is the sustainable replacement for paid FinOps tooling. A $500/month org sponsorship is roughly 1% of what Select.dev charges to monitor a $50k/month Snowflake spend, and it funds the project for everyone - including smaller teams and non-profits who can't justify either.

Sponsorship currently funds:

  • Multi-account support (currently single-account; tracked in ROADMAP.md)
  • Snowflake-native scheduled task migration helpers
  • Expanded forecasting models beyond linear regression (seasonality, change-point detection)
  • Direct integrations with PagerDuty / Opsgenie for real-time alerts

Suggested tiers:

  • $25/month (individual) - keeps the project alive; shoutout in the next release notes
  • $100/month (team) - priority issue triage + roadmap input
  • $500/month (org) - your logo in the README + a quarterly call to discuss your team's Snowflake workflows

Who should sponsor: data engineering teams at companies running Snowflake, Snowflake consulting partners whose engagements include cost optimization, FinOps practices using FrostWatch in client work, and anyone whose Snowflake bill has surprised them in the last quarter.

Sponsor arunrajiah

Contributing

Contributions are welcome! Please open an issue before starting large changes so we can align on direction.

  • Read CONTRIBUTING.md for setup instructions and PR guidelines
  • Follow our Code of Conduct
  • All PRs require passing CI (lint, type check, tests, frontend build) and one maintainer review

License

MIT - free to use, modify, and self-host. See the license file for details.

Metadata

Release files for frostwatch 0.4.3

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for frostwatch 0.4.3
File Size Uploaded Provenance Actions
frostwatch-0.4.3.tar.gz 63.7 kB With provenance Details for frostwatch-0.4.3.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for frostwatch 0.4.3
File Interpreter ABI Platform Actions
frostwatch-0.4.3-py3-none-any.whl Python 3 none any Details for frostwatch-0.4.3-py3-none-any.whl

Total release size: 340.8 kB

Release files / frostwatch-0.4.3.tar.gz

Download URL frostwatch-0.4.3.tar.gz
Size 63.7 kB
Tags Source
SHA-256 checksum
How to use checksums
d7dd000df6e2221a2e9e30d0e736c2affe20e8b4cca9b73b61328b1bed3416ec
BLAKE2b-256 checksum
How to use checksums
3e370413d3855f75bb58373f1b574f8806c8e630d34ab0fdc76b46b8baa3716b
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

Release files / frostwatch-0.4.3-py3-none-any.whl

Download URL frostwatch-0.4.3-py3-none-any.whl
Size 277.0 kB
Tags Python 3
SHA-256 checksum
How to use checksums
9357b21e2e068b6fea8e2ca11512ca74d1c861232340c1606bc5292cb04a63dc
BLAKE2b-256 checksum
How to use checksums
dd9f21d00af9be3d717fc02ddd09a340a3beb8129cadab317d3c288eeada5e81
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

Security for frostwatch 0.4.3

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for frostwatch-0.4.3.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Oct 27, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page