A ClickHouse console in one curl

One curl, any cluster

The same single-file app ClickHouse can serve also runs locally, with no install ceremony:

That drops a launcher and a small Python runner into your home directory. It needs only python3 — no Node, no pip, nothing to build. Run altinity-sql-browser and it serves the app at localhost:8900 and opens it.

The good part is where it gets its connections. The runner reads your ~/.clickhouse-client/config.xml — the same file clickhouse-client already uses — and offers each saved connection in the login picker. Plain host/user/password entries prefill the form; ones carrying OAuth keys do an SSO sign-in. At startup it probes each host's HTTP interface (443 then 8443 for TLS, 8123 then 80 for plain) and skips the ones that don't answer, so you're not staring at dead entries.

Queries go straight from your browser to the cluster. The runner only hands over the app and the list of hosts — it never sees your data.

So it's a local console for whatever clusters you already talk to, with nothing new to trust and nothing to uninstall later.

Upgrading is re-running the same one-liner — there's no state of its own to migrate, because your connections live in the clickhouse-client config you already keep. And there's nothing to uninstall later beyond a launcher and a folder in your home directory.

When you outgrow a personal console and want the always-on, team-wide version, that's the hosted deployment — the same single file, served by ClickHouse itself. The full walkthrough for the local runner is in the local-app guide; once you've built up a set of queries worth keeping, the query library turns them into a file you can commit and share.