Skip to main content

Connect ClickHouseBusiness plan

Updated Nov 4, 2026

On My Data → Add data → Connect a warehouse or database, choose Live — query in place, then ClickHouse. Cognizon queries your self-hosted ClickHouse server directly over HTTPS; nothing is copied.

Before you start

  • Create a dedicated ClickHouse user with profile readonly=2 — not 0 (not read-only) and not 1 (which rejects the per-query limits Cognizon sends on every query).
  • Create a row policy on every table you plan to connect, scoping that user (directly or via a granted role) to only the rows it may see. Cognizon checks for it when you register a table and refuses a table with no row policy; it never adds its own filter on top.
  • The server must be reachable over HTTPS. Plain HTTP is only accepted for a local or development server.
  • Connecting ClickHouse requires a plan with connectors enabled (Business or Enterprise).

Steps

  1. On My Data, open Add data → Connect a warehouse or database, then choose Live — query in place.
  2. Pick ClickHouse.
  3. Fill in: Name, Host, Port (optional, defaults to 8443), Database, User, Password, and HTTPS (optional — leave as true; set to false only for a local/dev server reachable over plain HTTP).
  4. Click Test connection, then Save connection once it passes.
  5. Pick a Table from the list Cognizon discovered, give it a Dataset name, and register it.

Good to know

  • ClickHouse is Live-only — there is no scheduled daily-copy path for it, unlike Postgres, BigQuery, or Google Sheets.
  • Every query Cognizon sends also carries per-connection row and byte ceilings (max_rows_to_read / max_bytes_to_read), on top of whatever your row policy already restricts.
  • The password is stored in Google Secret Manager, never in Cognizon's own database.
  • Connecting ClickHouse requires a plan with connectors enabled (Business or Enterprise).

FAQ

Why does my ClickHouse user need readonly=2 specifically?

readonly=0 is not read-only at all, and readonly=1 rejects the per-query row/byte limits Cognizon sets on every query it runs. readonly=2 allows those limits while still blocking writes.

Who decides which rows Cognizon can see?

You do, entirely through your own ClickHouse row policy on each connected table. Cognizon does not add its own filtering on top — it relies on the policy you've set for the connected user.

Does my ClickHouse server need to be on HTTPS?

Yes, for any production use. Plain HTTP is only accepted for a local or development server you explicitly mark as non-secure in the connection form.

Can I copy ClickHouse data into my workspace instead of querying it live?

No — ClickHouse currently supports Live (query in place) only; there is no scheduled daily copy for it.