Hotdata vs ClickHouse

9× faster than ClickHouse

On the same hardware, with your ClickHouse SQL as written.

At a glance

Topic	Hotdata	ClickHouse
What it is	A Rust query engine built for low latency at high concurrency.	A column-oriented analytics database.
Where data lives	Queries your sources in place, or Parquet in an instant database.	Loaded into ClickHouse tables.
Deployment	In your VPC, run by us. Or fully managed.	Self-hosted or ClickHouse Cloud.
Pricing	Compute runs only while queries run.	Compute by the hour, plus storage.
Concurrency	9× faster than ClickHouse with 10 concurrent clients.	Scales up with bigger services.
Combining sources	Join Postgres, warehouses, lakes, and files in one query.	Built around its own tables.
Search	Vector, full-text, and geospatial in one SQL query.	Vector and full-text indexes.
SQL	Postgres-familiar HotSQL. PostgreSQL, DuckDB, Snowflake, and ClickHouse SQL run as written.	ClickHouse SQL.

9× faster than ClickHouse, with 10 clients querying at once.

p95 query latency

You want 9× lower tail latency on the same hardware.
Your data lives in Postgres, a warehouse, and object storage, and you don't want to load it all first.
Your ClickHouse SQL should run as written, next to Postgres and Snowflake SQL.
You want it run for you, in your own VPC.

We deploy Hotdata into your own VPC and operate it for you. If you would rather not run any infrastructure, a fully managed option is also available.

Security: Your data stays in your own cloud account. You keep control of the infrastructure, access, and keys.
Performance: Hotdata runs in the same network as your databases and object storage, so reads stay inside your cloud.