ClickHouse Cloud Cost Optimization
Cut your ClickHouse Cloud bill. OhChimp finds services with idle scaling disabled, long idle timeouts, and compute waste, and writes up each fix.
What OhChimp optimizes for ClickHouse Cloud
Some of the cost levers OhChimp checks for ClickHouse Cloud. Each one becomes a reviewable plan you approve before anything changes.
Idle scaling disabled on a running service
Idle scaling is the primary ClickHouse Cloud compute-savings lever, and a running service with it turned off bills compute continuously even when it serves no queries. OhChimp finds those services, attaches the compute cost they actually accrued over the window from your usageCost data, and drafts a plan to enable idle scaling and set an idle timeout so the service can pause.
Idle scaling on but no idle timeout
A service can have idle scaling enabled and still never pause, because no idle timeout is set. OhChimp catches that case, shows the compute spend it has been billing continuously, and writes the plan to set a timeout so the service pauses when it goes quiet.
Idle timeout set too long
An idle timeout above 60 minutes keeps a service warm and billing compute for that long after its last query before it pauses. For a bursty workload, that warm-but-idle time adds up. OhChimp flags services with an unusually long timeout and proposes tightening it to match how the workload actually behaves.
Compute vs storage cost breakdown
OhChimp aggregates your usageCost data into a per-service breakdown and splits each service into compute, storage, backup, and data-transfer cost. That tells you which services drive the bill and whether the spend is compute you can pause or storage you need to address differently.
Full service footprint across states and tiers
OhChimp inventories every service the key can see, including stopped and freshly-created zero-cost ones, with its state, tier, region, provider, and idle-scaling settings. That shows your full footprint instead of only the services that show up in cost or findings, so nothing hides from the review.
Spend split across multiple organizations
If your API key spans more than one organization, OhChimp analyzes the first one and tells you the rest exist, so you know a single org's billed total covers only that org. It points you at pinning a specific organization on the integration to analyze that one directly.
Worked example
For example, say OhChimp reads your organization and finds a production service running with idle scaling disabled, billing compute continuously through nights and weekends, plus a second service whose idle timeout is set to 180 minutes.
It drafts one plan to enable idle scaling and set a sensible timeout on the first service, and another to tighten the second service's timeout, each with a confidence score, a risk level, and rollback steps. You press apply. OhChimp cannot yet measure what a single ClickHouse Cloud plan saves, so it does not mark one VERIFIED. The saving stays an estimate, and when the 30 days of monitoring end the result reads "Inconclusive."
ClickHouse Cloud cost optimization FAQ
How does OhChimp connect to ClickHouse Cloud?
With an organization API key (Admin or Developer role) over HTTP Basic auth, using the key ID and key secret. OhChimp reads your organizations, your service inventory with idle-scaling config, and the usageCost billing API. Every call is read-only, and it verifies the key at connect time so an under-privileged key is caught immediately.
Does OhChimp need write access or see my data?
No. OhChimp uses read-only API calls to list services and read billed cost. It never writes to your account, and it never stores application data, secrets, or workload contents. Dollar figures come straight from ClickHouse Cloud's own usageCost billing, where one ClickHouse Credit equals one US dollar.
What ClickHouse Cloud costs does OhChimp actually reduce?
The main one is compute that bills continuously because idle scaling is disabled or has no idle timeout set, so the service never pauses. OhChimp also flags idle timeouts set too long for bursty workloads, breaks each service into compute, storage, backup, and data-transfer cost, and surfaces spend hidden across multiple organizations.
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 you are always the one who clicks. OhChimp applies the matching code and infrastructure changes together.
How are ClickHouse Cloud savings verified, and what does it cost?
Today ClickHouse Cloud savings stay estimates. OhChimp cannot yet measure what a single ClickHouse Cloud plan saves, so it does not mark one VERIFIED, and when the 30 days of monitoring end the result reads "Inconclusive." The only savings OhChimp measures today come from lowering the CPU and memory requests of a Kubernetes Deployment, StatefulSet, or DaemonSet. Pricing is a flat monthly fee, OhChimp never takes a cut of your savings, and paid plans carry a year-one ROI guarantee that lets you request a refund of your first 12 months of subscription fees if the verified savings on your Costs tab fall short of them. Estimated savings do not count.
What keeps a service awake, and the Gen 2 services that cannot idle: ClickHouse Cloud idle scaling: why it never idles.
Related integrations
Teams running ClickHouse Cloud usually run these too. OhChimp finds the waste in each and drafts every fix as a plan you approve.
MongoDB Atlas
Cluster tier, storage, and idle compute
Elastic Cloud
Deployment tier, hot/warm tiers, retention
Redis Cloud
Plan tier, memory, and throughput fit