Run lightweight SQL and connection checks to confirm whether a ClickHouse instance is managed by ClickHouse Cloud or self-hosted.
Run SELECT hostName() to reveal the server’s fully-qualified domain name. ClickHouse Cloud endpoints contain “.clickhouse.cloud”. If the substring is present, you are connected to a managed cloud cluster.
Query system.build_options and system.settings. Entries such as cloud_environment or cloud_storage indicate a cloud deployment. On self-hosted servers those rows are empty or absent.
Managed clusters use HTTPS or Native protocol endpoints like https://{org}-{region}.clickhouse.cloud
.Self-hosted nodes usually expose IP addresses or custom domains.
Yes. Cloud and self-hosted instances share the same SQL dialect, so e-commerce analytics queries against Customers, Orders, and OrderItems run identically.
Always store endpoint URLs in environment variables, document deployment type in runbooks, and restrict credentials based on environment to avoid accidental cross-environment queries.
Use the hosted option when you prefer hands-off maintenance, automatic scaling, and predictable pricing.Keep self-hosting for custom networking or on-prem compliance.
.
No. The SQL dialect and functions are identical to open-source ClickHouse.
Yes. Use clickhouse-backup or INSERT FROM INFILE to copy data, then update application connection strings.