ABOUT

A lakehouse that many teams can share

thunderduck started from a simple frustration: running analytics for lots of customers meant either standing up a warehouse per tenant or trusting fragile conventions to keep their data apart. Neither scales.

So we built a platform where isolation is structural. Every tenant gets its own namespace and storage prefix, and queries are rewritten to stay inside those boundaries before they ever touch data. One platform, many customers, no leakage.

Underneath, DuckDB does the heavy lifting — but instead of an always-on warehouse, each query runs as its own right-sized job and then disappears. That makes cost honest: you pay for the compute a query used, and you can see exactly what that was.

The result is a lakehouse you can hand to a whole company of analysts, or embed as the query layer behind your own product — with the storage and catalogs staying entirely yours.

Built on
Query engine
DuckDB, one job per query on Kubernetes
Table format
Apache Iceberg
Catalog
Nessie (managed or remote)
Storage
MinIO · Amazon S3 · GCS · Azure Blob
Console
Next.js SQL Studio & monitoring

Want the full tour?

We'll walk you through the platform on a live workspace.