The open ecosystem around ClickHouse

Summary

ClickHouse’s open ecosystem spans clients, dashboards, ingestion pipelines, projects built on its engine, and agents that query it, with 2,600+ contributors, 240,000+ commits, and hundreds of millions of downloads cited. It describes open standards including OpenTelemetry for observability, Model Context Protocol (MCP) for AI tooling, and Iceberg and Delta Lake for lakehouse data, plus Iceberg REST catalogs, Apache Polaris, and Unity Catalog. The surrounding stack includes ClickStack, chDB, Langfuse, LibreChat, official language clients, a Kubernetes operator, Postgres bridges such as PeerDB and pg_clickhouse, and integrations with Airflow, dbt, Grafana, Fivetran, and Sigma. Specific updates include full Iceberg v2 support, Iceberg writes in 25.8, Paimon in 25.10, chDB v4’s DataStore API, and a Python client v1.0 with native async and 4x faster cold starts. The post frames this openness as supporting flexible tooling and community-led growth, reporting more than 200 integrations while noting that the ecosystem’s next direction remains unknown.

Takeaways

1. 1

   ClickHouse supports OpenTelemetry through an exporter in the OpenTelemetry Collector contrib repository, and OpenTelemetry forms the spine of the ClickStack observability stack.

2. 2

   The ClickHouse MCP server lets compatible agent frameworks explore tables, write queries, and read results without requiring a bespoke integration for each framework.

3. 3

   The official Kubernetes operator automates sharding, replication, scaling, and safe rolling version upgrades through Kubernetes custom resources.