Ducktober is here - 8 launches in 8 daysSee what's live
Give each user, customer, or AI agent a dedicated instance — fully isolated, independently sized, and scaled to zero when idle.
Manage DuckDB compute instances by user, then add read scaling replicas for read-heavy workloads.
We were able to identify specific organizations, and even better, specific users, who need more compute. We can scale individually for each one, so we get a much faster UX without paying to scale an entire cluster.
Josh Nakka
Co-Founder @ Pricemedic
Hypertenancy allows you to manage compute instances independently for sub-second query performance with dramatically lower costs. Provision Pulse instances for your agents, speedy Standards for your most important app users, or a Mega for that backfill — you'll only pay for what you use.
Agents can generate SQL without running amok. Hypertenancy sandboxes each agent's compute, so a runaway query can't blow up your bill or take down your warehouse.
Attach read-scaling replicas to individual compute instances to handle read-heavy workloads from agentic applications and business intelligence tools. Scale instances independently with as many replicas as you need.
With other warehouses, you provision for peak and pay for that capacity always. Using hypertenancy, you get a serverless architecture built for real-world workloads.
Create service accounts and provision compute programmatically via our REST API. Each user-internal or end-user-gets a dedicated duckling that spins up on first query and scales to zero when idle. No cluster scaling or tuning required.
`md:<database>` connection strings. Your app uses tokens to route queries; MotherDuck handles instance lifecycle, scaling, and spin-down.Deploy sandboxed agents, built responsive applications, or simply power up your data stack with sub-second queries for every user.
