Skip to main content
ClickHouse Cloud does not bill per byte scanned. It bills compute for every hour a service is awake, plus storage. A service that receives no queries scales to zero after its idle timeout and stops billing compute; any query, however small, wakes it. An agent is the worst kind of client for that model. It explores, retries, and asks the same thing several ways, spread across the day, so the service rarely gets to sleep. Custom tables change who wakes the service. Agents answer from a cached copy inside BOW, and only the scheduled refresh touches ClickHouse.

​
How it works

1

Define the query once

On the agent’s tables page, choose Custom table and write the rollup in ClickHouse SQL, for example revenue by region and status over the orders table.
2

Pick a schedule

Each refresh wakes the service, runs your SQL, and streams the result into an encrypted local copy. The service then idles again.
3

Agents answer from the copy

Questions run against the copy in DuckDB SQL. A turn answered from the copy sends no queries to ClickHouse at all, not even a connection check.

​
What it can save

Compute cost is units × price per unit-hour × hours awake. The figures below are a projection, not a measurement on a live ClickHouse Cloud service. They assume a 15-minute idle timeout, four refreshes a day, and Scale-tier pricing of about 0.30 USD per unit-hour; check ClickHouse’s pricing page for current rates. On a 2-unit Scale service, the business-hours case comes to roughly 131 → 13 USD a month; on a 12-unit service used around the clock, roughly 3,400 → 140 USD. Storage is billed the same either way.
The saving only exists if agents are what keeps the service awake. If ingestion, dashboards, or an application already query it all day, the service never idles and custom tables save little compute, though they still take agent load off it and answer in milliseconds.

​
The schedule decides the bill

Every refresh is a wake-up. With a 15-minute idle timeout:
  • Four refreshes a day keep the service up about an hour a day.
  • An hourly refresh keeps it up about six hours a day, whether or not anyone asks a question. Most of the saving is gone.
Refresh as often as people actually ask, not as often as you wish the data were fresh. Daily, shortly after your batch loads, is right for most rollups. See Choosing a schedule.

​
Before you start

  • Turn on Custom tables under AI settings.
  • Use a connection with shared credentials.
  • Give the ClickHouse user SELECT on the source tables and system.parts, and KILL QUERY. See the ClickHouse connector notes.
Write rollups, not mirrors. SELECT * FROM events on a billion-row table hits the row ceiling and is aborted; a GROUP BY that reads the whole table and returns a few thousand rows is exactly what a custom table is for.

Custom queries

Creating, scheduling and activating a custom table.

Overview

What BOW Fast is for and which connectors support it.