ClickHouse Cost Optimization
Cut your ClickHouse bill from inside the cluster. OhChimp finds weak codecs, costly queries, merge pressure, and idle replicas, verified on your real bill.
How does OhChimp connect to ClickHouse?
OhChimp connects with a read-only user over TLS (default secure port 8443). It reads the server version to confirm the connection, then runs probe queries against system tables with a 30-second execution cap. The user only needs read access to system tables.
Does OhChimp need write access or see my data?
No. OhChimp uses a read-only user and reads metadata, table and column sizes, and aggregated query stats from ClickHouse system tables. It never stores your application rows, secrets, or workload contents.
What ClickHouse costs does OhChimp actually reduce?
Waste inside the engine that a node bill never shows: columns with weak compression codecs, expensive SELECT queries, tables under merge pressure, over-partitioned tables, idle or lagging replicas, and memory or thread settings that force bigger nodes than your load needs.
Who applies the changes, and can they be rolled back?
You do. Each fix is a reviewable plan with a confidence score, a risk level, and rollback steps. Nothing changes until you click apply, and OhChimp ships the matching code and infrastructure changes together. You are always the one who presses the button.
How are ClickHouse savings verified, and how does pricing work?
Against your real bill. A plan is marked VERIFIED only after 7 or more days, a drop of at least 10%, and 3 consecutive positive checks. Until then it stays flagged "not implemented." Pricing is a flat monthly fee with no cut of your savings, plus a year-one ROI guarantee: a full refund of subscription fees if OhChimp does not pay for itself in your first 12 months on a paid plan.