chukei runs in your infrastructure, serves verified repeated reads, lets idle warehouses sleep, and passes unsafe queries straight through to Snowflake. Use replay when you need to validate the savings before rollout.
You already see your Snowflake spend. chukei acts on it — in the query path, in your infrastructure.
Show where money went. Someone still has to act.
Reuses safe reads, sleeps idle warehouses, verifies every saved credit.
The warehouse. chukei sits in front, not in its place.
Point one Snowflake JDBC, Python connector, or dbt workload at chukei instead of changing every client at once. Credentials stay with the driver and SQL stays the same.
Replay QUERY_HISTORY when you need evidence first, then use the proxy to verify cache hits and keep unsafe decisions on Snowflake.
Built for teams that need cost reduction they can validate before a wide rollout: one Snowflake workload, verified cache hits, signed evidence, and fail-open passthrough.
Point one JDBC, Python, or dbt workload at chukei. SQL and credentials stay with the existing driver, and rollback is changing the hostname back.
Deterministic repeated reads can return from a verified proxy cache instead of burning warehouse credits on the same dashboard or report again.
Detect idle windows and begin in suggest-only mode. Enforce suspend later only for the warehouses and roles you choose.
Attach spend and avoided credits to the query source: user, app, team, and dbt metadata where available, without relying on perfect query tags.
Replay QUERY_HISTORY and export signed JSON evidence so finance, platform, and security can review the savings case before broader routing.
Run the Apache-2.0 proxy in your environment. Cache misses, parse failures, unsafe SQL, and plugin errors pass through to Snowflake.
Savings vary by workload mix and existing tuning. Use replay against your own QUERY_HISTORY before routing traffic.
chukei replay reads a Snowflake QUERY_HISTORY export before traffic moves. Use it to size the opportunity, then deploy the proxy where verified cache hits and safe suspend decisions can actually cut spend.
Download chukei, deploy it in your infrastructure, and point one low-risk Snowflake workload at the proxy. Replay query history first when you need a savings case.