Hotdata vs Snowflake

Faster than an X-Large Snowflake warehouse

Without paying for one.

At a glance

TopicHotdataSnowflake
What it isA Rust query engine built for low latency at high concurrency.A cloud data warehouse.
Where data livesQueries your sources in place, or Parquet in an instant database.Loaded into Snowflake storage.
DeploymentIn your VPC, run by us. Or fully managed.Managed service.
PricingCompute runs only while queries run.Per-warehouse credits. Bigger warehouses cost more.
Concurrency5× faster than Snowflake with 10 concurrent clients.Latency rises past 10 streams.
Snapshots and copiesSnapshots, time travel, and forks.Zero-copy clones.
SearchVector, full-text, and geospatial in one SQL query.Vector and keyword search functions.
SQLPostgres-familiar HotSQL. PostgreSQL, DuckDB, Snowflake, and ClickHouse SQL run as written.Snowflake SQL.

16×Bigger Snowflake warehouse, still slower than Hotdata →

Performance

5× faster than Snowflake, with 10 clients querying at once.

p95 query latency
  1. 1

    Hotdata

    4 vCPU · 16 GiB

    0.38 s

    p50 0.17 s · 51.1 q/s

  2. 2

    Snowflake

    ~8 vCPU · 16 GiB

    1.74 s

    p50 0.85 s · 10.9 q/s

Which one fits

Choose Hotdata when

  • You need answers 5× faster, on half the vCPUs.
  • Concurrency keeps climbing, and sizing up to an X-Large warehouse isn't the answer.
  • Your apps need vector, full-text, and SQL filters in one query.
  • You want it in your own VPC, run for you.
  • Your Snowflake SQL should run as written.

Snowflake still fits when

  • Your analysts and BI tools need a governed warehouse as the source of truth.
  • You run large batch transformations, and query concurrency is low.

Using Hotdata with Snowflake

Connect Snowflake as a read-only source and join it with everything else. Snowflake SQL runs as written.

Connecting a source →

Deployed in your 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.