Pay for the queries you run
Start free. Scale into per-query billing when you go to production. Talk to us for private deployments and compliance.
Free
For trying it out and small projects.
- 1 company workspace
- Up to 3 catalogs
- Shared query compute
- 7-day usage history
- Community support
Pro
For teams running production workloads.
- Unlimited catalogs
- Dedicated, right-sized query jobs
- Pay-per-query CPU & RAM billing
- Full monitoring & history
- Role-based access
- Email support
Enterprise
For scale, compliance, and control.
- Everything in Pro
- Private / self-hosted deployment
- SSO & audit logging
- Per-tenant storage credentials
- SLA & priority support
- Solutions engineering
Prices shown are placeholders — final usage rates are set per workspace.
Questions, answered
How does per-query billing work?
Each query runs as its own Kubernetes job. We meter the CPU-seconds and peak RAM it consumed, so you pay for real compute instead of an always-on warehouse.
Where does my data live?
Your tables and query results stay in object storage (MinIO, S3, GCS, or Azure Blob) under a storage prefix scoped to your company. thunderduck orchestrates the compute; you keep the data.
How is one tenant isolated from another?
Queries are rewritten into your company's private namespace before they execute, and results are written to your private prefix. A tenant cannot reference another tenant's catalog.
Can I bring my own catalog?
Yes. Use the managed Nessie catalog, or connect a remote Nessie server and flat-file sources you already run.
Not sure which plan fits?
Tell us about your workloads and we'll recommend a setup. Cloud or On-Premise