Stream into ClickHouse Kafka API with your free account

The ClickHouse Kafka API connector uses Estuary’s Dekaf compatibility layer to expose Estuary collections as Kafka-compatible topics that ClickHouse Cloud can ingest through ClickPipes. Instead of managing your own Kafka broker, you create a Dekaf materialization in Estuary and configure ClickPipes to read from Estuary using Kafka-compatible connection details. This is useful when your ClickHouse workflow depends on ClickPipes or when you want ClickHouse Cloud to manage the ingestion path.

• Materialize Estuary collections as Kafka-compatible topics that ClickHouse ClickPipes can consume.
• Use Dekaf when you want to ingest into ClickHouse Cloud through ClickPipes instead of writing directly with Estuary’s native ClickHouse connector.
• Connect ClickPipes using Estuary’s Dekaf broker address, schema registry address, SASL_SSL, and the PLAIN SASL mechanism.
• Use the full Dekaf materialization name as the Kafka and schema registry username.
• Use the Dekaf auth token as the Kafka and schema registry password.
• Map each Estuary collection binding to a Kafka-compatible topic for ClickHouse ingestion.
• Stream CDC updates from source systems into ClickHouse with low-latency, incremental delivery.
• Configure deletion behavior based on how you want ClickHouse to handle CDC-aware deletes and Kafka-style delete events.