CHUKEI
Self-hosted proxy
Runs inside your infrastructure and sits directly in the Snowflake query path.
Apache-2.0your VPChostname-only pilot
- Verified cache hits and suspend controls
- Replay evidence before wider rollout
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 proof before rollout.
SELECT region, SUM(amount) FROM analytics.marts.daily_revenue WHERE dt >= DATEADD(day,-7,CURRENT_DATE) GROUP BY 1 b3:9f2a…e7 is eligible.daily_revenue. chukei serves the checked result. Warehouse stays asleep.team=growth, app, user, and query source.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.
Hosted optimizers and dashboards help teams see or plan changes. chukei runs in your path so one Snowflake workload can reduce repeated compute, then prove what changed.
Runs inside your infrastructure and sits directly in the Snowflake query path.
Hosted platforms for visibility, recommendations, forecasting, and managed optimization.
Useful for explaining where spend went, but usually outside the production query path.
The core difference is where the tool runs and whether it can act before a human reads a report.
Vendor SaaS or read-only dashboards
Recommendations, reports, or manual changes
Demo, trial, quote, or build reports
Out-of-path or vendor-specific behavior
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.