CHouseUI
Install & upgrade

Compatibility matrix

Tested ClickHouse, PostgreSQL and SQLite versions, plus browser and runtime requirements.

Version combinations CHouse UI has been tested against end-to-end.

Tested versions

ComponentVersionNotes
ClickHouse24.11Monitoring suite verified end-to-end against a production cluster
ClickHouse25Query logs, metrics, fleet
ClickHouse23.8 and 26.5Data observability end-to-end against every pipeline source (Kafka, RabbitMQ, NATS, S3Queue, AzureQueue, PostgreSQL replication); features a version lacks show unsupported on this version
PostgreSQL18RBAC database (RBAC_DB_TYPE=postgres)
SQLite3.51.0RBAC database via Bun's built-in SQLite (RBAC_DB_TYPE=sqlite)

Runtime requirements

RequirementMinimum
Bun (development)1.0+
chouse CLI 1.xCHouse UI server 3.14 or later (chouse status checks)
Kubernetes (Helm chart)1.25+
RAM2 GB recommended
Ports5521 (UI, API and MCP at /mcp), 8123 (ClickHouse HTTP)

Deployment targets

TargetNotes
Docker / Docker ComposePrimary install path — see Docker deployment
Kubernetes / HelmSigned OCI chart on GHCR — see Helm chart
Source (bun run dev)Frontend :5173, backend :5521

Monitoring caveats

The monitoring suite reads ClickHouse system tables (system.query_log, system.part_log, system.replicas, …). Clusters must have:

  • query_log enabled (default on most installs)
  • Sufficient permissions for the connection user to read system.*
  • Clock sync between CHouse UI and ClickHouse hosts (time-window filters)

If a system table is missing, the corresponding tab shows an empty/degraded state rather than failing the page — see Monitoring overview.

Browsers

Any current Chromium- or Gecko-based browser. The UI is responsive on desktop and tablet; container-query layouts adapt per component rather than per viewport.

Edit this page on GitHub ↗