Hotdata vs Neon

90× faster than Neon for analytics

Keep Neon for your app. Query it with Hotdata.

At a glance

TopicHotdataNeon
What it isA columnar Rust query engine built for low latency at high concurrency.Serverless Postgres for app reads and writes.
Where data livesQueries your sources in place, or Parquet in an instant database.Postgres storage.
DeploymentIn your VPC, run by us. Or fully managed.Managed service.
PricingCompute runs only while queries run.Compute hours, plus storage.
Concurrency90×+ the throughput of Neon with 10 concurrent clients.A single Postgres compute that autoscales.
Snapshots and copiesSnapshots, time travel, and forks.Instant branches.
SearchVector, full-text, and geospatial in one SQL query.Postgres extensions like pgvector.
SQLPostgres-familiar HotSQL. PostgreSQL runs as written.PostgreSQL.

90×+Faster than Neon

Performance

90×+ faster than Neon, 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

    Neon

    34.96 s

    p50 10.50 s · 0.53 q/s

Which one fits

Choose Hotdata when

  • You want analytics 90× faster than on Postgres.
  • You want reporting and search traffic off your production database.
  • You need to join Postgres with a warehouse, a lake, or files in one query.
  • Your Postgres queries should run as written.

Neon still fits when

  • Your application needs a transactional database for reads and writes by key.
  • You want instant Postgres branches for preview environments.

Using Hotdata with Neon

Connect Neon as a read-only source. Neon handles transactions, and Hotdata handles analytics. We run it this way ourselves.

How Hotdata accelerates Neon and Supabase →

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.