Engineer-first ClickHouse growth and ACID gaps
Product manager at Firebolt on on scaling challenges and ACID compliance in OLAP databases
ClickHouse is winning because its distribution model reinforces its product strengths. Strong engineers adopt it first for a very concrete reason, it runs fast analytical queries on huge event and log tables at much lower infrastructure cost than Elasticsearch, OpenSearch, Datadog, Snowflake, or BigQuery, and the open source path lets teams prove that value themselves before a sales process ever starts.
-
That engineer led motion is not just brand. In one production migration from OpenSearch, a team cut its cluster to roughly one third of the prior CPU and memory footprint, extended log retention from 7 days to 30 days, and still paid about half as much. That kind of before and after result spreads through infrastructure teams quickly.
-
The open source funnel matters because ClickHouse is a power user tool. Teams can start self hosted on a small server, learn the tuning knobs, and only later move to cloud. That lowers adoption friction, creates in house expertise, and makes ClickHouse feel like an engineer's tool rather than a top down platform purchase.
-
The main threats are not weak demand or warehouse competition, but the harder parts of enterprise packaging. Evidence across the ecosystem points to gaps around ACID style transactional workflows, cluster management, upgrades, and enterprise controls like RBAC, audit trails, and compliance, which matter when turning open source usage into durable large cloud contracts.
From here, the path is clear. If ClickHouse keeps converting self hosted users into managed revenue while closing the enterprise feature gap, its engineer led adoption engine can keep taking observability, embedded analytics, and real time query workloads from legacy search and warehouse products. The company already has the growth and product pull to do it.