ClickHouse Playground
A fast, open-source, column-oriented, analytical database.

๐ก To explore ClickHouse's scaling capabilities, check out the this multi-node playground.
๐ง System Components
- ClickHouse Server: High-performance columnar database engine optimized for analytics
- CH-UI: Web UI for ClickHouse - SQL editor, schema browser, and dashboards
๐ ๏ธ Tools
clickhouse-client: Interactive command-line client for running queriesclickhouse-local: Tool for processing local files with ClickHouse SQLch-ui: Server binary behind the CH-UI tab
๐ฏ Getting Started
Using CH-UI
Open the CH-UI tab and sign in with the ClickHouse credentials:
- Username:
default - Password:
iximiuz
CH-UI authenticates against ClickHouse itself, so those are the only credentials involved - there's no separate CH-UI account.
How CH-UI reaches ClickHouse
The browser never talks to ClickHouse directly. CH-UI's server holds the ClickHouse client and runs your queries for you, connecting to http://127.0.0.1:8123 from inside the playground. You can point it elsewhere in /etc/ch-ui/server.yaml:
sudo systemctl restart ch-ui
The CH-UI tab goes through a Caddy proxy on port 13488 rather than CH-UI's own 3488. CH-UI sends X-Frame-Options: DENY, which would otherwise blank out the tab.
Connecting to ClickHouse
# Connect using the interactive client
clickhouse-client
# Connect with specific database
clickhouse-client --database=default
# Execute single query
clickhouse-client --query "SELECT version()"
Credentials
If you need to connect from another client, use the following credentials:
- Host:
localhost - Port:
9000(native) or8123(HTTP) - Username:
default - Password:
iximiuz - Database:
default
Running Queries
# Start interactive session
clickhouse-client
# Example queries in the client
SHOW DATABASES;
SELECT version();
SELECT name FROM system.tables LIMIT 5;
๐ Learn More
๐งฉ Related Content
๐งช Playgrounds
Happy learning! ๐
A real VM, not a container
Get root on a VM with its own kernel, so Docker, Kubernetes, and systemd just work.
Read the docs โ
SSH from browser or CLI
Use the built-in web terminal, or connect with labctl ssh, plain ssh, scp, or rsync.
Read the docs โ
Drive it with AI
Let Claude, Codex, or any MCP client start this playground and run commands in it.
Read the docs โ
Expose HTTP(S) ports
Give any web app running inside the VM a public URL - for yourself or to share with others.
Read the docs โ
Share terminals
Invite others into your terminal session, or open it yourself from another device.
Read the docs โ
Customize with init scripts
Add shell scripts that run at boot to install packages, clone repos, or seed test data.
Read the docs โ
Private networking
VMs reach the internet via NAT with no public IP; several VMs share bridge networks.
Read the docs โ
Ephemeral or persistent
By default, VMs are destroyed when the session ends; enable persistence to keep the disks for next time.
Read the docs โ
Built-in container registry
A private registry.iximiuz.com for every playground to share images across services and VMs.
Read the docs โ