Product 01
Serverless DuckDB analytics [CO001, CO007, CV001, CV010] Diligence report
MotherDuck
DuckDB cloud analytics with isolated compute, public funding traction, and limited financial disclosure.
MotherDuck looks like a differentiated DuckDB analytics asset with real funding and adoption signals, but the public record is still too thin on operating metrics to underwrite a buy.
Coverage and disclosure
Public disclosure is strongest on product, launch, and funding history; current ARR, margin, retention, governance, and incident detail remain opaque.
Cover facts
Company profile
MotherDuck is a private, Series B cloud analytics company built on DuckDB and positioned around isolated compute for people and agents, hybrid local/cloud query execution, and a self-serve product-led motion. The public record supports real funding and adoption momentum, but still leaves current revenue quality, customer concentration, and governance structure largely undisclosed.
- Website
- motherduck.com
- Founders
- Jordan Tigani
- Founding location
- Seattle, Washington, United States
- Headquarters
- Seattle, Washington, United States
- Product
- Serverless cloud analytics platform built on DuckDB with isolated compute per user and agent session.
- Customers
- Analysts, engineers, data teams, and agent/workflow builders.
- Business model
- Usage-based cloud analytics with free entry, paid tiers, and AI-unit add-ons.
- Stage
- Series B
- Funding status
- Disclosed total funding reached $100M in 2023; later private-market trackers put cumulative funding around $133M.
Executive summary
Top strengths
- Differentiated DuckDB-based product architecture with isolated compute for users and agents.
- Real funding base and credible private-market support.
- Visible adoption and customer-story momentum across analytics and agent workflows.
Top risks
- Current ARR, margin, and retention are still undisclosed.
- Vendor-favorable terms and low liability caps increase downside risk.
- Competitive pressure and customer concentration remain opaque.
Open gaps
- Current ARR, burn, runway, and revenue quality are still not public.
- Customer concentration, retention, and churn remain undisclosed.
- Governance, board control, and enterprise security posture are still thinly disclosed.
Contents
01Company Overview
1.1 Identity and product position
MotherDuck presents itself as a cloud data warehouse built on DuckDB, with a strong emphasis on speed, isolation, and developer ergonomics. The company’s own materials frame the product around internal BI, customer-facing analytics, and agent-native workflows, which positions it closer to a modern analytics control plane than a generic warehouse. That positioning matters because it explains both the early product story and the company’s current go-to-market posture. Public sources are consistent on the DuckDB foundation, while the exact commercial scale of the business remains opaque.[CO001, CO002, CO003, CO004, CO005, CO006, CO007, CO016]
| metric | value/status | date | confidence | gap |
|---|---|---|---|---|
| Founded | 2022 | 2022 | medium | Based on third-party profile; no founding announcement was reviewed. |
| Headquarters | Seattle | unknown | medium | Only third-party profile evidence surfaced in the assigned pool. |
| Product | Serverless SQL analytics on DuckDB | 2026-09-22 | high | Company-owned positioning is clear. |
| Business model | Freemium-to-paid cloud analytics | 2023-2026 | medium | Public pricing has changed and exact current pricing is not summarized in reviewed sources. |
| Latest reported valuation | $400M | 2023 | medium | Third-party reporting only; not a company filing. |
| Total capital raised | $100M+ | 2023 | high | Supported by company blog and third-party funding profile. |
| Current revenue/run-rate | not disclosed | 2026-09-22 | low | No reviewed public source gives a current run-rate. |
| Current customer count | not disclosed | 2026-09-22 | low | Only launch-era usage proxies were public. |
| Headcount | ~11 database experts (profiled) | 2023-2026 | low | This is a third-party profile count, not an internal employee roster. |
| Locations | Seattle HQ; product surfaces show US-East-1 and EU-region presence | 2024-2026 | medium | Public materials do not disclose a full office map. |
Several rows are partial or historical rather than current; null or not disclosed means no reviewed public source supplied a current company KPI as of runDate.
[CO001, CO002, CO003, CO004, CO005, CO006, CO007, CO015, CO016]1.2 Leadership, founders, and governance
The public leadership picture centers on CEO and co-founder Jordan Tigani, whose BigQuery background gives MotherDuck direct category credibility. A third-party profile also describes Antony Courtney and Boaz Leskes as founding engineers with deep infrastructure pedigrees, which reinforces the team’s database experience even though the public governance picture is incomplete. No reviewed source exposed a board roster or voting control detail, so the company appears founder-led but not fully governance-transparent from the outside.[CO008, CO009, CO010]
| person | role | background | founder-market fit or functional coverage | key-person dependency |
|---|---|---|---|---|
| Jordan Tigani | CEO and public co-founder | Former Google BigQuery founding engineer and public face of the company | Direct analytics-warehouse founder-market fit | high |
| Antony Courtney | Founding engineer | Background in web UI, languages, and runtimes; previously at Snowflake and Facebook | Bridges product ergonomics and systems execution | medium |
| Boaz Leskes | Founding engineer | Background in Elasticsearch and cloud platforms; previously at Elastic and Buzzcapture | Bridges database and cloud infrastructure depth | medium |
Leadership surfaced here reflects public materials and a third-party profile; governance and board composition remain undisclosed in the reviewed evidence.
[CO008, CO009, CO010]1.3 Funding history and investor base
MotherDuck’s financing story is unusually clean for a private startup: an initial raise in late 2022, a 2023 launch with $47.5M already disclosed, and then a Series B that pushed total capital raised to $100M. The company’s own blog says the Series B added Felicis as lead and kept a broad syndicate of prior backers in place, which is a useful signal for diligence because it suggests continuing investor confidence rather than a forced reset. Reported valuation data is still third-party sourced, so it should be treated as directional rather than definitive.[CO011, CO012, CO013, CO014, CO015]
| stakeholder | role | control or economic importance | diligence ask |
|---|---|---|---|
| Felicis | Series B lead investor | Primary fresh capital and credibility anchor | Confirm follow-on support and board influence |
| a16z | Existing investor | Important signal of prior category conviction | Assess whether thesis and support are still active |
| Madrona | Existing investor | Regional/data-network relevance | Confirm whether local ecosystem support continues |
| Amplify Partners | Existing investor | Infrastructure thesis alignment | Check whether infra roadmap support remains strong |
| Altimeter / Redpoint / Zero Prime | Existing investors | Broader syndicate durability | Verify who is still actively engaged on follow-on rounds |
This is an investor map, not a cap table; the rows reflect named investors in public announcements and profile pages, not current ownership percentages.
[CO011, CO012, CO013, CO014, CO015]1.4 Milestones, traction, and watch-outs
The milestone arc is clear: a 2023 launch, public traction claims measured in thousands of users, later product maturation, and then expansion signals such as a dedicated EU region and updated commercial terms. That arc supports a narrative of continued execution, but the public record also surfaces a cautionary note: independent commentary highlights pricing pressure and a narrower competitive position against larger incumbents. Taken together, the company looks real and active, yet still dependent on a narrow niche and a few public leadership signals.[CO003, CO004, CO005, CO006, CO015, CO016]
Timeline of MotherDuck’s launch, funding, traction, and product expansion milestones.
Dates are exact where surfaced in reviewed sources; some milestone labels summarize source prose rather than formal press-release titles.
First raise [CO003]
Big Data is Dead [CO001, CO007]
Cloud platform launch [CO003, CO004]
Series B / $100M raised [CO005, CO011]
General availability [CO016]
Dedicated EU region [CO016]
Terms updated [CO016]
Independent outlook refresh [CO015]
02Market Analysis
2.1 Market boundary and substitutes
MotherDuck is not best thought of as a generic warehouse clone. Its own positioning combines a cloud data warehouse, dedicated compute per user and agent, and a developer workflow that can move from local DuckDB to cloud execution. The practical market boundary therefore includes the analytics runtime and warehouse layer bought by small product, data, and engineering teams, plus the adjacent stack layers that determine whether queries arrive on time: ingestion, lightweight orchestration, and agent tooling. The status quo substitutes are still the large cloud warehouses and lakehouses, but for many startups the real alternative is not a new vendor at all; it is spreadsheets, CSVs, transactional SQL, or a patchwork of BI and ETL tools. This is why the market should be framed around the job to be done - fast answers with low ops - rather than around a single named database category. [CM010, CM012, CM013]
| segment/category | included spend | excluded spend | buyer/payer | relevance |
|---|---|---|---|---|
| Lean serverless warehouse/runtime | Query runtime, storage/compute, and local-cloud workflow continuity | BI-only tools, ETL-only tools, and manual spreadsheets | Analytics engineer or data engineer; payer is the startup data/engineering budget | Core spend bucket |
| Traditional cloud warehouse | Snowflake/BigQuery/Redshift-style compute and storage | Embedded app logic and agent orchestration | Platform/data leaders; payer is the centralized data budget | Primary substitute |
| Lakehouse / object-storage analytics | Query and compute over parquet/object storage plus governance | Standalone SaaS BI and workflow tooling | Data platform teams; payer is the platform budget | Adjacent substitute or upgrade path |
| Agentic ingestion / orchestration | Pipeline creation, scheduling, and monitoring | Raw storage and dashboarding | Data and product engineering; payer is the product engineering budget | Expansion layer |
| Status-quo analytics stack | Spreadsheets, manual SQL, and patchwork BI | Governed warehouse/runtime | Operators and analysts; payer is usually an ad hoc department budget | Fallback alternative |
Boundary is modeled from product positioning and startup-guide comparisons; included and excluded spend are not mutually exclusive categories.
[CM001, CM002, CM003, CM004, CM005, CM006, CM007, CM010, CM012, CM013]2.2 Sizing lenses, not a single TAM
The source set does not support a clean vendor-specific TAM, so the right move is to preserve multiple sizing lenses. The narrowest lens is the lean startup warehouse wedge: teams with small-to-mid data volumes, a need for rapid iteration, and minimal platform overhead. A second lens is the adjacent agentic analytics and runtime market, where MotherDuck is broadening the use case from query serving to natural-language pipeline creation and monitoring. A third lens is the enterprise departmental wedge, where DuckLake-style object-storage deployments can support selected teams inside larger organizations without replacing their core warehouse. Taken together, the evidence suggests a market that expands from startup analytics into broader data-app infrastructure, but the public sources here do not isolate a trustworthy spend number. That uncertainty should stay visible rather than being hidden behind a single aspirational TAM slide. [CM008, CM009, CM011, CM015, CM016]
| publisher/year | geography | value | CAGR | methodology | confidence | limitation |
|---|---|---|---|---|---|---|
| MotherDuck / 2026 guide | global | Startup wedge: teams with GB-to-low-TB data and low-ops needs | n/a | Source-backed segmentation from product positioning | medium | Not a spend estimate |
| SiliconANGLE / 2026 | global | Traction proxy: about 850 paying customers; Flights priced at about $0.60/hour | n/a | Launch and adoption proxy | medium | Feature pricing, not market size |
| Amplify Partners / 2022 | global | Small/faster-data, edge, and interactive-analytics thesis | n/a | Investor thesis lens | medium | Older and qualitative |
| Bytebase / 2022 | global | DuckDB commercialized as analytics infrastructure for the long tail | n/a | Independent synthesis of the startup playbook | medium | Not a market report |
These are evidence-constrained lenses and traction proxies, not a formal third-party TAM/SAM/SOM estimate.
[CM005, CM008, CM009, CM010, CM011, CM015, CM016]A layered view of the market from the broad enterprise warehouse market down to the narrow startup wedge MotherDuck is best positioned to win first.
Layer widths indicate hierarchy, not quantitative proportions.
Ordinal layer weights only; the chart expresses relative scope, not market share.
[CM005, CM008, CM011, CM015, CM016]2.3 Buyer path and adoption constraints
The likely buyer is the person closest to analytics friction: an analytics engineer, data engineer, or full-stack developer building dashboards, customer-facing analytics, or AI-assisted data workflows. Budget authority usually sits with the startup’s engineering or data leader, while the user is often a small team that wants local-dev continuity, predictable cost, and a short path from sign-up to first query. The strongest adoption driver is not raw scale; it is the chance to remove the hidden tax of cluster sizing, infrastructure maintenance, and context switching between local and cloud environments. The main constraints are equally clear. Large distributed workloads, heavy governance, and a mature lakehouse ecosystem still favor incumbent platforms. And as MotherDuck pushes into agentic ingestion, the market expands, but it also inherits a new integration burden: buyers will judge whether the combined stack is simpler than stitching together Fivetran, dbt, BI, and an AI agent layer themselves. [CM014, CM015, CM016]
| segment | buyer | user | payer | workflow | budget owner | adoption trigger |
|---|---|---|---|---|---|---|
| Startup analytics team | Head of engineering or analytics lead | Analytics engineer | Startup engineering/data budget | First dashboards, models, and ad hoc analysis | Engineering or data leadership | Need for faster time-to-first-query and low ops |
| Product engineering / AI app team | Product engineering lead | Full-stack developer or agent developer | Product engineering budget | Embedded customer-facing analytics and AI-assisted data work | Product engineering | Need for low-latency, user-visible analytics |
| Scaling data platform team | Data/platform lead | Data engineer | Platform budget | Multi-source ingestion and governed analytics | Data/platform leadership | Need to reduce manual pipeline work |
| Finance / ops analyst | Ops or finance leader | Analyst | Department budget | Internal reporting and planning | Ops or finance | Need for self-serve analytics without a heavy warehouse stack |
Buyer roles are inferred from the product and market-positioning sources; actual org charts vary by company size.
[CM002, CM004, CM005, CM007, CM014, CM015, CM016]03Competitors
3.1 Competitive landscape and substitute classes
MotherDuck's practical competitive set is broader than direct DuckDB peers. The company itself frames the product as a serverless cloud warehouse built on DuckDB, while the official comparison material positions SQLite as the embedded transactional alternative and Turso / SQLite Cloud as the cloudified SQLite path. That means buyers can compare MotherDuck not only against other managed analytics tools, but also against staying on embedded engines, staying on Postgres plus replicas, or letting teams keep a local-first workflow and adding cloud sharing only where needed. The strongest takeaway from the public material is that MotherDuck is competing on workflow shape as much as on raw query execution.[CP001, CP004, CP006, CP009, CP010, CP012]
| Competitor | Category | Scale / funding | Target segment | Differentiation | Limitation |
|---|---|---|---|---|---|
| MotherDuck | Managed DuckDB cloud warehouse | $100M+ raised; 2 rounds; 2,000 launch users | Analysts, engineers, and data scientists | Hybrid local-cloud execution plus collaboration | Still looks like a managed layer over DuckDB rather than a totally new category |
| DuckDB self-build | Embedded analytical engine / internal build | Open-source ecosystem scale; no company funding figure in scope | Engineers who can own infra | Fast local analytics with no service wrapper | No managed collaboration, sharing, or hosted control plane |
| SQLite / cloud SQLite | Embedded transactional DB and cloud wrappers | Massive installed base; cloud vendors are niche relative to SQLite itself | App developers and transactional workloads | Simple operational footprint and broad familiarity | Weaker fit for complex analytics and multi-user OLAP-style work |
| Traditional warehouse | Distributed OLAP incumbent | Large enterprise adoption; scale is established but not quantified here | Centralized analytics teams and enterprise buyers | Mature governance and broad warehouse feature sets | Heavier ops, more cost sensitivity, and less local-first ergonomics |
| Postgres + replicas | Status-quo substitute | Existing production stack; scale tied to the buyer's app | Teams already standardized on Postgres | Stays inside familiar operational tooling | Analytics and concurrency are not its native strength |
Public evidence here is category-level rather than exhaustive vendor benchmarking; funding and scale are only filled where the fetched sources make them explicit, and the remaining cells are intentionally coarse so unknowns stay visible.
[CP001, CP004, CP006, CP009, CP010, CP011, CP012]3.2 Product, pricing, and go-to-market comparison
Public positioning centers on hybrid local-cloud query execution, collaboration, and pay-for-use economics. That makes MotherDuck easier to contrast with both open-source DuckDB, which brings the engine but not the managed collaboration layer, and with DBCode-style integrations that improve the developer surface without changing the underlying ownership model. The pricing story is comparatively thin: the homepage advertises pay-for-use pricing, and the startup program offers a credit-like package for qualifying startups, but the market still lacks a clean public view into realized enterprise pricing or discounting. On the GTM side, the public record suggests a product-led motion aimed at analysts, engineers, and data scientists rather than a heavy enterprise field-sales motion.[CP001, CP002, CP004, CP005, CP006, CP007, CP008, CP011]
| Buying criterion | MotherDuck | DuckDB self-build | SQLite / cloud SQLite | Traditional warehouse |
|---|---|---|---|---|
| Hybrid local-cloud split | Yes | Partial | No | No |
| Collaboration and sharing | Yes | No | Partial | Yes |
| Analytics on files / lake data | Yes | Yes | Partial | Yes |
| Low-ops managed service | Yes | No | Yes | Partial |
| Public trust / control posture | Mixed: terms are explicit, but data-processing rights are broad | Depends on self-hosting | Usually vendor-managed | Depends on vendor and contract |
| Developer experience surface | Strong | Strong but self-managed | Moderate | Strong but heavier |
Unsupported cells are marked as partial, no, or mixed rather than guessed; this matrix is a buyer-facing lens, not a complete feature audit.
[CP001, CP002, CP003, CP007, CP008, CP009, CP010, CP011]| Option | Price / packaging | Included capabilities | Discount or unknowns | Implication |
|---|---|---|---|---|
| MotherDuck | Pay-for-use; startup program offers $16,000 of value for an $8,000 annual commitment | Managed DuckDB cloud analytics with collaboration | Realized enterprise discounts are not public | The public pricing story is simple, but not fully transparent |
| DuckDB self-build | Open source engine; infra cost depends on the buyer | Engine only | Operational cost and support are unknown | Cheapest license cost, but the buyer owns the stack |
| SQLite / cloud SQLite | Open source core plus vendor hosting where applicable | Transactional DB or cloud wrapper | Cloud pricing varies by vendor | Good for app data, weaker for analytics-heavy use cases |
| Traditional warehouse | Usually contract-based and usage-based | Full warehouse and governance stack | Discounting is negotiated | Usually wins on breadth, not simplicity |
| Postgres + replicas | Existing infra plus replica / warehouse spend | Operational DB plus extra analytics path | Cost depends on current stack | Status quo can be cheap to start, but not optimized for analytics |
List pricing and startup-program pricing are public; realized enterprise discounts, credits, and renewal terms are usually opaque, so those cells are deliberately marked as unknown rather than inferred.
[CP002, CP004, CP005, CP008, CP009, CP010, CP011]3.3 Differentiation durability and displacement risk
MotherDuck's moat appears to rest on convenience and a coherent workflow, not on a unique data engine. The strongest risk is commoditization from the bottom: DuckDB can absorb more of the analytic workload itself, while cloud SQLite and generic warehouse products can keep improving their managed layers. The strongest counterweight is the company's hybrid execution model, which is hard to copy perfectly because it blends local and cloud compute, sharing, and user-friendly collaboration. Even so, the public evidence does not show an exclusive distribution channel, a hard switching cost moat, or a clear regulatory wedge; the product is differentiated, but not obviously insulated.[CP001, CP003, CP007, CP009, CP010, CP011]
MotherDuck sits in the high-convenience, high-analytics-specialization corner, while DuckDB and cloud SQLite alternatives trade off managed workflow depth against simplicity or local control.
| Item | X (2–5) | Y (2–5) | Context |
|---|---|---|---|
| 1. MotherDuck | 5 | 5 | Hybrid local-cloud execution plus collaboration pushes the product toward the top-right on convenience and specialization. |
| 2. DuckDB self-build | 4 | 3 | Strong analytics engine, but the buyer owns orchestration, sharing, and service ergonomics. |
| 3. SQLite / cloud SQLite | 2 | 2 | Excellent simplicity for transactional or embedded workloads, but weaker for complex analytics. |
| 4. Traditional warehouse | 4 | 4 | Broad warehouse capability and governance, but a heavier operational and pricing footprint. |
| 5. Postgres + replicas | 3 | 2 | Familiar status quo for many teams, yet not purpose-built for cloud analytics workflows. |
| 6. DuckDB + DBCode | 4 | 4 | An IDE-led workflow can improve developer ergonomics, but it still leaves the buyer with the managed-service burden. |
The axes are ordinal scores based on public positioning, not measured benchmarks; higher x means more specialized analytics orientation, and higher y means a smoother managed workflow for the buyer.
[CP001, CP007, CP009, CP010, CP011, CP012]04Financials
4.1 Revenue model and pricing surfaces
MotherDuck looks much closer to a consumption-led analytics platform than a classic seat-based SaaS business. The official site and launch announcement describe serverless analytics with hybrid local/cloud execution, while the pricing and startup-program pages expose the public monetization surfaces: free access, list-price tiers, usage credits, and AI-unit add-ons. That is enough to see how customers can enter cheaply, expand into paid tiers, and then incur overages or add-on spend as usage grows. What it does not reveal is realized pricing, margin by tier, or the share of customers still sitting on promotional credit. For that reason, the right financial read is a clear monetization mechanism with opaque realized economics, not a clean subscription disclosure.[CI002, CI003, CI004, CI005, CI006, CI007, CI014, CI015]
| Stream | Mechanism | Unit | Current value / status | Quality | Diligence ask |
|---|---|---|---|---|---|
| Free entry tier | Self-serve product access that lowers adoption friction and can convert into later paid usage | User / organization | Publicly visible | Useful top-of-funnel, but not a revenue figure | Request free-to-paid conversion and activation rate |
| Paid compute / storage usage | Consumption billing for serverless analytics capacity | Compute credits and storage usage | List pricing disclosed; realized mix undisclosed | Core monetization surface, but margin not public | Request realized pricing and tier mix by cohort |
| AI functions | AI-powered SQL / embedding features billed separately in AI Units | AI Units | Publicly described | Upside add-on, but usage intensity unknown | Request attach rate and margin by workload type |
| Startup program | Promotional annual commitment with bundled credits and fee waiver | Annual commitment / credits | Publicly visible promotional offer | Likely acquisition tool rather than steady-state ARPU | Request net retention after promo expiry |
List pricing and promotional offers are public; realized revenue share, take rates, and margin by stream are not disclosed in the prefetched sources.
[CI002, CI003, CI004, CI005, CI006, CI014]| Plan or offer | Public price / terms | Included value | Discount or unknowns | Source |
|---|---|---|---|---|
| Free | Free to use until billing begins | Entry access to the product and product-led usage | Duration of the free window and later conversion are not public | Official blog announcement |
| Lite | $25 per organization per month | Base paid tier with compute / storage credits | Realized discounting and annualized revenue not disclosed | Sacra research page |
| Business | $100 per organization per month | Higher paid tier with larger included usage | Realized contract mix not disclosed | Sacra research page |
| Startup program | $8,000 annual commitment for $16,000 of value; $13,000 in consumption credits plus $3,000 annual platform fee waived | Promotional growth offer for qualifying startups | Excludes existing paying customers and larger funded startups | Official startup-program page |
These are list prices and promotional terms, not realized revenue; the company does not disclose contract-level take rates or customer-specific discounting in the prefetched pack.
[CI002, CI003, CI004, CI005, CI006, CI014]MotherDuck appears to monetize adoption by moving users from free entry and promotional credits into paid tiers, then into overages and AI-unit consumption.
| Node / Connection | Node / from | To | Context |
|---|---|---|---|
| Node 1 | Free entry [free-entry] | Low-friction self-serve access and trial usage. | |
| Node 2 | Startup program [startup-program] | Promotional credits and fee waivers for qualifying startups. | |
| Node 3 | Paid tiers [paid-tiers] | Lite and Business list-price plans. | |
| Node 4 | Usage overages [usage-overages] | Additional compute and storage spend beyond base credits. | |
| Node 5 | AI Units [ai-units] | Separate monetization for AI functions. | |
| Node 6 | Revenue capture [revenue-capture] | Recurring and usage-based monetization that accrues as customers expand. | |
| Connection 1 | Free entry [free-entry] | Paid tiers [paid-tiers] | |
| Connection 2 | Startup program [startup-program] | Paid tiers [paid-tiers] | |
| Connection 3 | Paid tiers [paid-tiers] | Usage overages [usage-overages] | |
| Connection 4 | Paid tiers [paid-tiers] | AI Units [ai-units] | |
| Connection 5 | Usage overages [usage-overages] | Revenue capture [revenue-capture] | |
| Connection 6 | AI Units [ai-units] | Revenue capture [revenue-capture] |
4.2 Traction and funding signals
The public funding trail is consistent enough to establish that MotherDuck has raised real capital, but not enough to produce a fully current valuation bridge from public data alone. The company’s own announcement put the 2023 Series B at $52.5M and total capital raised at $100M; independent trackers broadly agree on the $100M base and later research coverage pushes the total higher to roughly $133M with a 2025 Series B+ estimate. Tracxn also reports 160 employees as of late August, which gives a rough scale proxy, while the launch blog said the product had 2,000 users querying it and feedback from over 100 users. The traction story is therefore real, but the public record still stops short of verified customer-count, revenue, or recurring-revenue disclosure.[CI001, CI008, CI009, CI010, CI013, CI014, CI015]
4.3 Capital adequacy and underwriting blockers
The biggest financial blocker is not whether MotherDuck can attract capital; it is whether the public evidence is sufficient to judge how much capital the company actually needs. The terms of use give the company broad rights to process customer and usage data, reserve the right to modify or discontinue the service, and cap liability at $100, which makes contract and legal risk part of the financial picture even before cash-flow questions. But the crucial inputs for underwriting -- cash balance, burn, runway, and debt obligations -- are not disclosed in the prefetched source pack. Until those figures are available, the most responsible conclusion is that MotherDuck has a credible funding base and a plausible monetization path, but still lacks the disclosure required for a confident capital-adequacy call.[CI007, CI009, CI011, CI012, CI013]
| Metric | Value | Confidence | Why it matters | Diligence ask |
|---|---|---|---|---|
| Gross margin | low | Needed to judge whether serverless execution and storage economics scale profitably | Request product-family gross margin bridge | |
| CAC / payback | low | Determines whether self-serve and startup incentives convert efficiently | Request cohort CAC and payback by acquisition channel | |
| Cash on hand | low | Core capital-adequacy input | Request current cash balance and monthly roll-forward | |
| Burn rate | low | Shows how quickly capital is consumed while scaling | Request monthly burn bridge and headcount plan | |
| Runway | low | Drives next-round dependency and financing risk | Request runway under base / downside cases | |
| Net revenue retention | low | Reveals expansion versus churn quality | Request cohort NRR by plan and segment |
Nulls mean the prefetched evidence does not disclose the metric; they are diligence asks, not zero values.
[CI008, CI009, CI010, CI011, CI012, CI013]05Product & Technology
5.1 Product surface and customer workflows
MotherDuck's public positioning is straightforward: it is a serverless analytics platform built on DuckDB that is meant to stand in for a cloud warehouse when customers want simpler SQL analytics, direct query access to files, or a backend for data apps. The strongest pattern in the public copy is not a single SKU but a workflow layer. Analysts get a notebook-like SQL surface, engineers get a cloud service that can connect to local and remote data, and teams get a story about taking the same engine from a laptop into a shared cloud context. That makes the product easier to frame than to benchmark: the use-case breadth is clear, but the public record does not publish hard sizing limits, pricing bands, or performance thresholds.[CE001, CE002, CE005, CE006]
| module or asset | primary user | status / maturity | differentiation | diligence gap |
|---|---|---|---|---|
| Notebook-like SQL workspace | analyst / engineer / agent | public, customer-facing surface | SQL-first analytics with local and remote data in one environment | No public benchmark, SLA, or pricing band |
| Hybrid execution engine | data team / platform builder | core architecture claim | Can split work between local and cloud data instead of forcing one tier | Need detail on planner controls and workload limits |
| Isolated duckling compute | dashboard, person, or agent session | key tenancy model | Per-session DuckDB instances reduce noisy-neighbor risk | Need published capacity and cost trade-offs |
| Modern Duck Stack / integrations | platform owner / workflow integrator | ecosystem expansion | Marketing positions MotherDuck across orchestration, ingestion, BI, and AI | Exact coverage and support depth are not fully disclosed |
Status labels are qualitative syntheses of public product pages and launch announcements; null or unknown in the underlying materials means the company did not publish a benchmark, SLA, or sizing threshold.
[CE001, CE002, CE003, CE004, CE005, CE006]| user job | current workflow | MotherDuck solution | measurable benefit | limitation |
|---|---|---|---|---|
| Cloud warehouse replacement | Teams need simpler analytics than a distributed warehouse | Use MotherDuck as a simplified DuckDB-based warehouse | Less operational overhead than a heavy distributed stack | Public materials do not quantify cost or latency |
| Data lake query engine | Users want to query files where they sit | Query Parquet, Iceberg, or CSV directly with a notebook-like UI | Avoids unnecessary preloading and supports in-place analytics | Iceberg support and scaling details are not independently benchmarked |
| Serverless backend for data apps | SaaS apps need fresh analytics without hammering OLTP databases | Use DuckDB as the analytics backend | Better fit for fast, fresh analytics than a transactional database | App-level SLAs and cost envelopes are not public |
| Community demos and test harnesses | Open-source teams need shareable data and repeatable CI targets | Use managed DuckDB for synthetic data, demos, and GitHub Actions tests | Offloads compute and centralizes shared datasets | No public case study gives production-scale operating data |
Benefit and limitation columns are qualitative because the public materials do not publish controlled benchmark data or pricing; null means the source did not disclose a numeric value.
[CE001, CE005, CE009, CE010]5.2 Architecture, isolation, and operating model
The operating model is the main differentiator. MotherDuck says every person, dashboard, and agent session gets its own isolated DuckDB instance and that those isolated instances are spun up quickly, which is the company’s answer to noisy-neighbor problems in shared analytics systems. The same public materials also describe hybrid execution, meaning the planner can split work between local and cloud data instead of forcing everything through one storage or compute tier. That architecture is opinionated but lightweight: it depends on DuckDB semantics, on direct access to common analytical file formats, and on a service layer that can coordinate sharing without exposing the user to the underlying orchestration details.[CE003, CE004, CE010, CE011]
| layer / component | role | dependency | risk |
|---|---|---|---|
| Client surface / notebook UI | Lets users and agents author and run SQL | Browser/app experience and query submission flow | Public docs do not show extensibility or embedded SDK detail |
| Hybrid query planner | Splits work across local and cloud data | DuckDB execution semantics and file connectors | Behavior is hard to evaluate without published benchmarks |
| Isolated duckling compute | Keeps sessions separate at the compute layer | Fast orchestration and provisioning | Capacity and cost trade-offs are not public |
| Trust and integration layer | Processes customer data and third-party platform data | Contract permissions and partner integrations | Security and privacy exposure depends on customer configuration |
This is a synthesized architecture view from public copy and contract language; it should be read as a diligence map rather than an audited deployment diagram.
[CE003, CE004, CE007, CE008, CE010]Public materials describe MotherDuck as a layered system: notebook and agent surfaces on top, hybrid execution in the middle, isolated DuckDB compute beneath, and data/governance controls around the edges.
- Client surfaces
- Notebook UI, SQL authoring, and agent entry points
- Modules
- Web UI
- Agent workflows
- Outputs
- Queries submitted
- Hybrid execution
- Planner splits local and cloud work
- Modules
- DuckDB engine
- Query planner
- Outputs
- Optimized SQL execution
- Collaboration and sharing
- Shared catalog and organization-wide access
- Modules
- Data catalog
- Shared assets
- Outputs
- Team access
- Isolated ducklings
- Per-user and per-dashboard compute
- Modules
- Per-session DuckDB instances
- Outputs
- Concurrent workloads
- Storage and file formats
- Parquet, Iceberg, and CSV as query targets
- Modules
- Parquet
- Iceberg
- CSV
- Outputs
- In-place analytics
- Data and governance
- Files, sharing, integrations, and contract controls
- Modules
- Parquet
- Iceberg
- CSV
- Third-party platforms
- Outputs
- Managed analytics
Layer ordering is synthesized from public marketing copy and contract language rather than an official vendor diagram.
[CE001, CE002, CE003, CE004, CE007, CE008, CE010, CE011]5.3 Trust, governance, and maturity signals
The legal and trust story is more explicit than the reliability story. MotherDuck's Terms of Use authorize broad processing of customer data and usage data, including queries, prompts, and outputs, and they also say customers may not security-test the service without prior written consent. That is a normal managed-service posture, but it also means the buyer has to read the contract carefully if the workflow involves sensitive data or custom integrations. External maturity signals are positive but still incomplete: the community discussion around OHDSI shows practitioners evaluating MotherDuck for shared demos and automated tests, and public funding trackers indicate a real company with meaningful capital behind it. What remains missing is the kind of published SLA, security certification, or benchmark set that would let a diligence team separate product promise from verified operating reliability.[CE007, CE008, CE009, CE012]
06Customers
6.1 Public customer segments and workflow fit
MotherDuck's public customer story clusters around three recurring segments: tech-forward product teams embedding analytics into SaaS experiences, data/analytics teams replacing slower warehouse or transactional patterns, and internal teams using the product as a self-serve analysis layer. The official home page and case-study page both point to production apps, customer-facing analytics, and internal insights, while the independent codecentric article explains why those workloads value sub-second response, tenant isolation, and lower operational overhead. That combination makes the use case legible, but it is still a public sample rather than a full customer census.[CU001, CU002, CU005, CU006, CU015]
| segment | buyer / user / payer | use case | scale signal | revenue or strategic value | gap |
|---|---|---|---|---|---|
| Data / analytics teams at tech-forward companies | analytics leaders, data engineers, product teams | customer-facing analytics, internal BI, and agentic workflows | named stories show production and near-production usage | helps teams ship analytics features without OLTP overload | no public customer census or segment revenue split |
| Embedded analytics / SaaS teams | product and platform teams | tenant-isolated dashboards and queries for end customers | homepage plus independent commentary align on this pattern | improves customer experience while reducing ops burden | public retention and expansion metrics are not disclosed |
| AI / agentic data teams | platform, ML, and applied-AI teams | remote MCP, hybrid local-cloud querying, and agent workflows | case studies and dogfooding show real usage | positions MotherDuck for emerging agent-led analytics | sample is vendor-heavy and likely incomplete |
| Internal self-serve BI / dogfooding | internal analysts and product ops | self-service exploration and scheduled workloads | about 6,000 queries daily across 40 jobs internally | de-risks product maturity and surfaces edge cases early | internal use is not the same as external retention |
Segment rows are a sampled read of public evidence, not a complete customer census. Missing fields reflect public opacity rather than absence of any commercial usage.
[CU001, CU002, CU004, CU005, CU006, CU015]Public customer journey from discovery to evaluation, deployment, expansion, and risk watch.
This is a qualitative synthesis of public adoption signals, not a measured funnel or audited lifecycle.
[CU001, CU005, CU012, CU014, CU015]6.2 Adoption signals and named proof
The strongest adoption signals are a mix of company-reported usage metrics and named customer outcomes. MotherDuck said it had 2,000 users querying the product and more than 100 users providing feedback at open-for-all launch, and the duckfooding talk adds an internal workload of roughly 6,000 queries a day across 40 scheduled jobs. The case-study page then supplies concrete customer stories: AheadComputing, Together AI, GoodShip, Hazel, and others show adoption moving from evaluation into production or near-production use, with outcomes such as faster onboarding, shorter dashboard turnaround, and sub-second queries.[CU003, CU004, CU007, CU008, CU009, CU010, CU011, CU014]
| metric | value | date | source | confidence | implication | missing denominator |
|---|---|---|---|---|---|---|
| Launch users querying the product | 2,000 | 2023-09 | MotherDuck Series B blog | medium | early demand beyond a private waitlist | total signups and active-vs-inactive split |
| Users who provided feedback | 100+ | 2023-09 | MotherDuck Series B blog | medium | visible feedback loop during product iteration | share of the user base and sample bias |
| Internal dogfooding workload | 6,000 queries / day across 40 scheduled jobs | 2026-09-22 access | Duckfooding talk | medium | product is used in a real internal production-like loop | whether this is one system or several |
| AheadComputing onboarding | 74% of engineers onboarded in the first weeks | public case-study page | MotherDuck case studies | medium | strong team adoption velocity | team size and prior baseline |
| AheadComputing dashboard turnaround | 3 months -> 1.5 hours | public case-study page | MotherDuck case studies | medium | material workflow acceleration | request volume and workload shape |
| Together AI active user count | 128 unique Hex users | public case-study page | MotherDuck case studies | medium | multi-team adoption | total company headcount and active usage denominator |
| Together AI concurrency support | 40 read-scaling replicas | public case-study page | MotherDuck case studies | medium | supported concurrent analytics and agent workloads | data volume and concurrency baseline |
| GoodShip deployment speed | analytics agent built in under a week | public case-study page | MotherDuck case studies | medium | fast path from idea to deployment | whether the deployment was a pilot or production rollout |
The table mixes launch, internal, and customer-case metrics. Values are directional and are not normalized to a common cohort or time window.
[CU003, CU004, CU007, CU008, CU009, CU010, CU011, CU014]| customer | segment | deployment / use case | production vs pilot | outcome | limitation |
|---|---|---|---|---|---|
| AheadComputing | data / analytics team | building a data platform for the agent era | public case study says "1 week to production" | 74% of engineers onboarded within the first weeks; dashboard requests fell from months to hours | public proof is vendor-authored and lacks third-party audit |
| Together AI | AI / platform team | scaling a data platform while scaling the company | appears production-facing from the case-study framing | 128 unique Hex users and 40 read-scaling replicas | no public customer-by-customer retention view |
| GoodShip | logistics analytics team | analytics agent built on MotherDuck's remote MCP | public page frames it as a shipped workflow, not a lab demo | built in under a week; sub-second queries where Postgres timed out | the page does not give a denominator or full rollout scope |
| Hazel | e-commerce / AI co-worker team | hundreds of dbt models on a central MotherDuck warehouse | production intent is implied but not quantified | strong architecture fit for customer-facing analytics | no explicit production date or adoption denominator |
Sampled from the public case-study page only. The row set is illustrative and intentionally omits logos without a concrete named outcome.
[CU007, CU008, CU009, CU010, CU011, CU014, CU015]6.3 Durability, expansion, and unresolved gaps
Durability is the weakest part of the public record. The visible materials support real deployment and some expansion, but they do not disclose NRR, GRR, churn, or a concentration schedule, so the chapter cannot separate broad adoption from a few enthusiastic logos. The public criticism is also mixed: a Reddit thread questions production readiness, while the company's own terms and customer stories imply that real customer workflows involve customer data and third-party integrations. Netting those together, the company looks genuinely used, but the stickiness story remains unresolved. That matters because visible demand can still sit on top of poor renewal visibility or a concentrated customer base. It is enough to trust the usage signal, but not enough to underwrite durable customer economics.[CU012, CU013]
07Risks
7.1 Risk summary
MotherDuck looks less exposed to classic regulatory blowups than to a more ordinary but still meaningful set of control, dependency, and proof risks. Its public terms let the company process customer and usage data broadly, change or discontinue service, and disclaim most downstream platform risk. The product story is attractive because it combines isolated compute with hybrid local-cloud execution, but that same design means reliability, query correctness, and customer trust depend heavily on MotherDuck-managed infrastructure and on a transaction-log abstraction most buyers will not inspect directly. The funding and user-count disclosures are encouraging, yet the public record still leaves unanswered questions about the depth of production adoption, concentration, incidents, and security posture.[CR003, CR004, CR005, CR006, CR007, CR008, CR012, CR013]
7.2 Legal, regulatory, and contractual exposure
The reviewed legal surface is straightforward but vendor-favorable. The terms of use give MotherDuck broad rights to process customer data and usage data, impose strong customer-side warranties around legal compliance, and cap liability at a nominal amount. They also let MotherDuck modify, suspend, or terminate the service and place most responsibility for third-party platforms, credentials, and customer permissions on the user. That structure is common for SaaS, but it matters more here because the product is itself a data-processing layer; if the service is interrupted, the customer may have limited contractual leverage and little recourse beyond support or switching costs. For underwriting, the key diligence question is not whether the terms exist, but whether enterprise customers have negotiated stronger paper or whether the standard contract is the practical norm.[CR004, CR005, CR006]
| Rule / issue | Jurisdiction / scope | Status | Likelihood | Severity | Mitigation | Residual exposure | Diligence path |
|---|---|---|---|---|---|---|---|
| Broad data-processing and usage-data rights | Contract / service terms | Disclosed | Medium | High | Standard MSA/DPA review; customer-side notices and consents | MotherDuck keeps broad processing rights and customers carry most consent burden | Review enterprise paper, DPA language, and any negotiated carve-outs |
| Service change, suspension, or termination at will | Contract / service continuity | Disclosed | Medium | High | Operational SLAs and internal migration planning | Customers may have limited leverage if service scope changes or access is suspended | Ask for SLA history, termination clauses, and support escalation paths |
| Third-party platform and integration liability shift | Third-party platforms | Disclosed | Medium | High | Integration testing and vendor review | MotherDuck disclaims control over outside platforms, including availability and security | Request integration map, platform dependencies, and contractual responsibility matrix |
Analytical register built from reviewed public terms and product pages; likelihood and residual exposure are judgment calls, and the scope is limited to publicly visible contract language rather than negotiated customer paper.
[CR004, CR005, CR006, CR007]7.3 Operational and platform reliability risk
MotherDuck's architecture reduces some classic warehouse pain, but it also makes operational quality harder to observe from the outside. The company emphasizes isolated DuckDB instances per user or agent, which should limit noisy-neighbor issues, and it uses a transaction log to manage file-level changes rather than mutating parquet in place. That is efficient, but it also means correctness depends on the log being applied consistently and on users not confusing raw file contents with the logical table view. The platform therefore has a failure mode that looks less like a single catastrophic outage and more like a set of subtle correctness, freshness, and state-management issues. Those are the kinds of problems that usually show up only after production load and complicated data operations arrive.[CR001, CR002, CR003, CR009, CR010]
| Failure mode | Likelihood | Severity | Mitigation maturity | Residual exposure | Unresolved gap |
|---|---|---|---|---|---|
| Logical-state drift versus raw parquet | Medium | High | Medium | High | Need evidence on versioning discipline, delete handling, and user safeguards |
| Isolated compute or agent instance failure | Medium | High | Medium | Medium to High | Need uptime history, rollback behavior, and isolation guarantees under load |
| Hybrid local/cloud query complexity | Medium | High | Medium | Medium to High | Need planner behavior, network-failure handling, and cross-environment consistency proof |
Analytical register based on public architecture and demo material; the residual exposure estimates assume normal SaaS controls but no private incident or certification disclosures.
[CR001, CR002, CR003, CR009, CR010]7.4 Dependency, market, and diligence gaps
The remaining risk is a mix of dependency and market-size uncertainty. MotherDuck sits on top of DuckDB and must keep compatibility, performance, and developer trust aligned with that open-source base. At the same time, the company's public positioning favors lightweight, cost-sensitive analytics rather than the broadest possible warehouse market, which is good for clarity but can narrow the funnel. The public evidence of adoption is positive, but it is still not the same as a clean view of customer concentration, renewal strength, incident history, or formal security posture. The right diligence response is to ask for proof, not assume it: current uptime and incident disclosures, enterprise contract terms, certification status, and a clearer view of how much usage is still exploratory versus embedded in production.[CR007, CR008, CR011, CR012, CR013]
| Dependency | Counterparty / role | Concentration | Failure scenario | Severity | Mitigation | Residual exposure | Diligence path |
|---|---|---|---|---|---|---|---|
| DuckDB open-source base | Core engine / ecosystem | High | Compatibility, roadmap, or performance divergence | High | Upstream stewardship and compatibility testing | Medium to High | Review release cadence, contribution pattern, and fallback options |
| MotherDuck-controlled cloud runtime | Primary platform | High | Instance outage or degraded query performance | High | Multi-region ops, monitoring, and customer comms | High | Request uptime, postmortems, and recovery objectives |
| Third-party clouds and integrations | Storage and external platforms | Medium | Interoperability or availability failures outside MotherDuck's control | Medium to High | Integration validation and contract mapping | Medium to High | Obtain dependency inventory and responsibility split |
| Narrow lightweight-workload focus | Go-to-market segment | Medium | Adoption stalls if the market stays niche or price-sensitive | Medium to High | Land-and-expand motion and usage-based pricing | Medium to High | Ask for pipeline mix, retention, and segment expansion data |
Analytical register that mixes structural dependency risk with market-concentration risk; concentration and residual exposure are inferred from public positioning rather than a disclosed customer ledger.
[CR001, CR003, CR007, CR008, CR011, CR012, CR013]Residual exposure is highest where contractual control, platform dependency, and opaque production proof overlap.
Cells are analytical ratings synthesized from the reviewed public record rather than company-issued risk scores.
[CR004, CR005, CR006, CR009, CR010, CR011, CR012, CR013]08Valuation
8.1 Valuation context
MotherDuck is not being valued as a generic data warehouse. The public story is a narrower, more differentiated one: serverless DuckDB-based analytics, isolated compute per person and agent, and a hybrid workflow that spans local and cloud execution. That positioning matters because it can justify a premium relative to undifferentiated BI tooling if adoption actually translates into durable usage. The most concrete public price anchors are the $400M post-money valuation in 2023 and Forge's 2025 mark at roughly $496M. Those marks are directionally consistent, but they are still secondary-market signals, not audited operating proof. The current evidence therefore supports a "priced as an interesting private growth asset" view, not a claim that the company has already earned public-market software multiples on disclosed fundamentals.[CV001, CV002, CV003, CV004, CV011, CV012]
| Dimension | Assessment | Evidence | Decision implication | Confidence |
|---|---|---|---|---|
| Recommendation | Track | Current evidence supports continued diligence but not a buy. | Hold for more operating disclosure before underwriting a new entry. | Medium |
| Valuation stance | Fair | Forge's 2025 mark and the 2023 $400M round cluster around the mid-$400M range. | The price is defensible, but only on private-market signals. | Medium |
| Risk rating | High | Public ARR, margin, and retention data are still missing. | Price discipline should stay conservative until operating metrics are disclosed. | High |
| Price support | Conditional | Product positioning and funding history support a premium software narrative. | The premium is credible, not yet fully proven. | Medium |
| Downside protection | Mixed | Contract terms and service-control rights are platform-standard but not benign. | Enterprise diligence should focus on the liability and data-processing surface. | High |
| Entry discipline | Tight | The evidence base is incomplete on current revenue quality. | Prefer a lower-risk entry only after current financials are disclosed. | Medium |
Judgments are synthesized from public product, funding, legal, and market data; "Confidence" is the confidence in the table row, not an external credit rating.
[CV003, CV004, CV007, CV011, CV012]Public product proof and funding marks support a plausible premium, but missing operating disclosure and contractual downside keep the recommendation at track rather than buy.
| Node / Connection | Node / from | To | Context |
|---|---|---|---|
| Node 1 | Product proof [n1] | ||
| Node 2 | Private-market marks [n2] | ||
| Node 3 | Contractual downside [n3] | ||
| Node 4 | Missing operating metrics [n4] | ||
| Node 5 | Valuation call [n5] | ||
| Node 6 | Disclosed metrics [n6] | ||
| Connection 1 | Product proof [n1] | Private-market marks [n2] | |
| Connection 2 | Private-market marks [n2] | Valuation call [n5] | |
| Connection 3 | Contractual downside [n3] | Valuation call [n5] | |
| Connection 4 | Missing operating metrics [n4] | Valuation call [n5] | |
| Connection 5 | Disclosed metrics [n6] | Valuation call [n5] |
8.2 Downside, moat, and contractual posture
The valuation case gets stronger when you look at the product moat and team depth, but the downside case is real. MotherDuck's own materials emphasize enterprise support, millions of weekly ducklings, and a product model built around dedicated compute for every user and agent. That is a meaningful operating claim because it suggests usage depth rather than just curiosity traffic. At the same time, the terms of use show broad data processing rights, a hard $100 liability cap, and unilateral service modification rights, which are standard for a software platform but still relevant for enterprise diligence. The startup program further implies a customer base that still spans small teams and startups, so there is room for expansion, but the public evidence does not yet show the kind of disclosed recurring-revenue engine that would remove valuation debate.[CV007, CV008, CV009, CV010]
| Argument | What would change the view |
|---|---|
| Differentiated product posture: serverless DuckDB, isolated compute, and hybrid local/cloud execution are meaningfully sharper than generic warehouse software. | A competing product with similar simplicity and better disclosed unit economics would weaken the premium. |
| Funding marks show investors continue to value the company in the mid-$400M range. | A materially lower mark, or no new capital support, would imply weaker conviction. |
| MotherDuck is already talking about enterprise support and real service depth, suggesting the platform is beyond hobbyist usage. | If enterprise support remains anecdotal and no revenue quality is disclosed, the moat looks thinner. |
| The legal and contractual surface is normal for a SaaS platform, but still exposes customer-data and liability risk. | Stronger enterprise contracting, higher liability coverage, and clearer data controls would reduce the downside case. |
| The startup program shows a low-friction adoption wedge among small teams. | A broader enterprise pipeline and more public reference customers would justify a higher multiple. |
This is a qualitative synthesis table. The rows are not meant to sum to a formal model; they separate the core bullish argument from the conditions that would falsify it.
[CV001, CV002, CV003, CV007, CV008, CV009, CV010, CV011]8.3 Decision and diligence
My recommendation is to track rather than buy. MotherDuck looks like a credible long-duration software asset with a differentiated architecture, solid private-funding history, and enough product momentum to justify continued diligence. The problem is that the valuation call is still built on proxies: funding marks, customer-facing positioning, legal terms, and a few usage anecdotes. The next step before a stronger underwriting stance is a current read on ARR, growth, margin, retention, and concentration, so the present mark can be tested against operating reality instead of just market sentiment. If those metrics confirm that the company is scaling efficiently, the current range can look fair; if not, the price starts to look stretched quickly.[CV003, CV004, CV007, CV011, CV012]
| Scenario | Assumptions | Valuation / return logic | Key risks | Probability signal |
|---|---|---|---|---|
| Bull | Enterprise support scales, agent-first usage grows, and the current private mark becomes a floor rather than a ceiling. | Multiple can expand if the company turns product pull into measurable recurring revenue. | Competitive imitation or slower enterprise conversion than expected. | Needs current ARR and retention to validate. |
| Base | The company keeps adding users and use cases, but keeps public metrics sparse. | The current mid-$400M mark remains roughly in line with private-market sentiment. | The valuation can stagnate if the disclosure gap persists. | Most consistent with today's public record. |
| Bear | Usage depth proves real, but revenue quality and margin are weaker than the product story implies. | Down-round or flat-round risk rises if growth does not translate into better economics. | A weak conversion from users to durable revenue. | Triggered by poor financial disclosure or weaker funding appetite. |
| Upside catalyst | Fresh disclosed metrics show efficient growth and broadening enterprise reference accounts. | Would support a higher price discipline and a more aggressive entry. | Still needs proof that the market is willing to pay for the platform. | Needs management disclosure or a financing update. |
| Downside trigger | The next diligence pass still cannot confirm ARR, margin, or retention. | Price support remains sentiment-driven rather than fundamentals-driven. | The market could re-rate the company quickly once harder metrics surface. | This is the present state of the public evidence. |
Scenario probabilities are judgmental and illustrative. They reflect valuation discipline rather than a calibrated financial model.
[CV003, CV004, CV007, CV009, CV012]8.4 Exhibits
This chapter's exhibits are intentionally sectioned because each one serves the argument in the section where it is introduced. The recommendation table summarizes the judgment, the thesis table separates what is attractive from what would change the view, and the scenario table shows how the call shifts under better or worse operating disclosure. The flow figure ties those pieces together by showing how product proof, price anchors, contractual risk, and missing metrics feed the final stance.[CV001, CV004, CV007, CV012]
Disclaimer
This report is a public-evidence diligence snapshot, not investment advice. Important financial, legal, technical, and contractual facts remain non-public and should be verified directly with management and primary documents before any investment decision.
Evidence index
| ID | Statement | Confidence | Sources |
|---|---|---|---|
| CO001 | MotherDuck presents itself as a cloud data warehouse built on DuckDB with dedicated compute for each user and agent session. | High | SO001, SO007 |
| CO002 | Reviewed third-party materials support a 2022 founding year and a Seattle headquarters for MotherDuck. | Medium | SO005, SO006 |
| CO003 | MotherDuck launched its serverless cloud analytics platform in June 2023 after having raised $47.5M. | High | SO003, SO005 |
| CO004 | MotherDuck said it had roughly 2,000 users querying the platform and feedback from over 100 users at the time of the Series B announcement. | High | SO007, SO003 |
| CO005 | MotherDuck's Series B announcement said the round brought total capital raised to $100M, and third-party funding data reported a $400M valuation. | Medium | SO007, SO005 |
| CO006 | MotherDuck said the product was free to use until billing would be enabled the following year. | Medium | SO007 |
| CO007 | MotherDuck's public website now frames the product as agent-first, with isolated DuckDB instances that avoid noisy neighbors. | High | SO001, SO007 |
| CO008 | TechCrunch and the company blog present Jordan Tigani as the public CEO/co-founder and a central category expert from Google BigQuery. | High | SO003, SO007 |
| CO009 | A third-party profile describes Antony Courtney as a founding engineer with prior experience at Snowflake and Facebook. | Medium | SO006 |
| CO010 | The same third-party profile describes Boaz Leskes as a founding engineer with prior experience at Elastic and Buzzcapture. | Medium | SO006 |
| CO011 | MotherDuck said Felicis led its Series B financing. | Medium | SO007 |
| CO012 | MotherDuck's Series B announcement names a16z and Madrona among the continuing investors. | Medium | SO007 |
| CO013 | MotherDuck's Series B announcement names Amplify Partners among the continuing investors. | Medium | SO007 |
| CO014 | MotherDuck's Series B announcement names Altimeter, Redpoint, and Zero Prime among the continuing investors. | Medium | SO007 |
| CO015 | Built In's 2026 profile describes MotherDuck as capitalized for growth but facing a narrower competitive position and pricing headwinds. | Medium | SO004 |
| CO016 | MotherDuck's terms page and 2026 legal update indicate an active commercial service with an updated contractual posture. | Medium | SO008 |
| CM001 | MotherDuck positions itself as a cloud data warehouse built on DuckDB and explicitly for agent-driven analytics workflows. | High | SM001, SM004 |
| CM002 | MotherDuck's homepage says customers build production apps, customer-facing analytics, and internal insights on the platform. | Medium | SM001 |
| CM003 | MotherDuck advertises dedicated compute for every user and agent, implemented as isolated DuckDB instances spun up in milliseconds. | Medium | SM001 |
| CM004 | The startup guide frames the market as three archetypes: skyscraper, workshop, and smart hub. | Medium | SM002 |
| CM005 | The guide says the smart-hub or lean serverless warehouse is best for startups that want very low operational overhead, minutes to first query, and a local-first development loop. | Medium | SM002 |
| CM006 | The same guide says the skyscraper and workshop archetypes still win when the job demands multi-petabyte scale, complex governance, or open-format data-lake flexibility. | Medium | SM002 |
| CM007 | MotherDuck's terms describe the service as a serverless data analytics platform that processes customer data and can integrate with third-party platforms, so buyers are purchasing an analytics runtime rather than storage alone. | High | SM004, SM001 |
| CM008 | SiliconANGLE reports that Flights lets users create and operate ingestion workflows through natural-language interactions with AI assistants and MCP-connected agents. | Medium | SM005 |
| CM009 | SiliconANGLE reports that MotherDuck had about 850 paying customers after 18 months of commercial operation and priced Flights at about 60 cents per hour. | Medium | SM005 |
| CM010 | Bytebase characterizes MotherDuck as commercializing DuckDB in a 'SQLite for Analytics' style startup playbook. | Medium | SM006 |
| CM011 | Amplify's investment note frames MotherDuck around smaller, faster data, edge computing, and interactive analytics instead of giant distributed warehouses. | Medium | SM007 |
| CM012 | VentureRadar groups MotherDuck with analytics platforms, open-source databases, multi-model databases, and serverless data tools, which shows the adjacent market boundary extends beyond classic warehouses. | Medium | SM008 |
| CM013 | The practical spend boundary includes warehouse runtime, lightweight orchestration, and agent tooling, because MotherDuck is trying to collapse those layers into one product path. | Medium | SM001, SM005 |
| CM014 | The most likely buyer is an analytics engineer, data engineer, or full-stack developer at a startup that needs a short path from local development to cloud analytics. | Medium | SM001, SM002, SM005 |
| CM015 | The main adoption constraints are large distributed workloads, heavy governance, and the maturity gap of newer open-storage and agentic workflows. | Medium | SM002, SM007, SM008 |
| CM016 | Agentic data ingestion and AI-assisted analytics are the clearest near-term growth drivers because they expand MotherDuck from query serving into pipeline creation, scheduling, and monitoring. | Medium | SM001, SM005 |
| CP001 | MotherDuck presents itself as a serverless cloud analytics platform built on DuckDB with hybrid local-cloud processing. | High | SP001, SP004 |
| CP002 | MotherDuck's public positioning includes pay-for-use pricing and collaborative features for sharing queries, tables, and results. | High | SP001, SP006 |
| CP003 | MotherDuck's terms of use give the company broad rights to process customer data and usage data and disclaim liability for third-party platforms. | Medium | SP003 |
| CP004 | MotherDuck publicly said the company had reached $100M in total capital raised after its Series B round, and Raising.fi lists more than $100M across two rounds. | High | SP002, SP005 |
| CP005 | MotherDuck said it had 2,000 users during the waitlist-to-open launch and had received feedback from more than a hundred users. | Medium | SP002 |
| CP006 | MotherDuck's launch narrative focused on three use cases: cloud data warehouse, data lake query engine, and serverless backend for data apps. | Medium | SP002, SP001 |
| CP007 | MotherDuck's clearest technical differentiator is hybrid query execution that can split work between local DuckDB and cloud compute. | Medium | SP002, SP004 |
| CP008 | DBCode describes MotherDuck as DuckDB-compatible, serverless, and pay-for-use, and it surfaces query, preview, import, and export workflows inside VS Code. | Medium | SP006 |
| CP009 | MotherDuck's own SQLite comparison frames SQLite as a transactional row-store alternative and names Turso and SQLite Cloud as cloud SQLite substitutes. | Medium | SP008 |
| CP010 | The SQLite comparison also says DuckDB is stronger on analytical aggregations, joins, and larger datasets, while SQLite is stronger for simple point queries and concurrent reads. | Medium | SP008 |
| CP011 | The independent review says MotherDuck's onboarding, UI, and documentation are polished, but its skeptical framing suggests the company is still proving its identity as more than a DuckDB wrapper. | Medium | SP007 |
| CP012 | Wikipedia places MotherDuck's founding in 2022, its private preview in June 2023, and its general availability in June 2024. | Medium | SP004 |
| CI001 | MotherDuck said its September 2023 Series B raised $52.5M and brought total capital raised to $100M. | High | SI001, SI005, SI007 |
| CI002 | MotherDuck said it was free to use until billing would begin the following year. | Medium | SI001 |
| CI003 | The startup program offers an $8,000 annual commitment for $16,000 of MotherDuck value, including $13,000 in consumption credits and a $3,000 annual platform fee waiver. | Medium | SI003 |
| CI004 | Startup-program eligibility is limited to customers with less than $5M in VC funding and fewer than 20 employees. | Medium | SI003 |
| CI005 | Sacra describes MotherDuck’s monetization as consumption-based pricing around compute and storage usage, with free, Lite, and Business tiers. | Medium | SI006 |
| CI006 | Sacra says MotherDuck also monetizes AI functions through AI Units. | Medium | SI006 |
| CI007 | MotherDuck’s official pages describe serverless analytics with hybrid local-and-cloud execution and dedicated compute instances per user or agent. | High | SI001, SI002 |
| CI008 | Sacra estimates a $33M Series B+ in May 2025 that brought total funding to about $133M and places the 2023 Series B at a $400M post-money valuation. | Medium | SI006 |
| CI009 | Tracxn reports 160 employees as of Aug. 26 and total funding of $100M over three rounds. | Medium | SI007 |
| CI010 | Raising.fi also reports MotherDuck with $100M total funding over two tracked rounds. | Medium | SI008 |
| CI011 | MotherDuck’s terms allow it to process customer data and usage data, including to operate the service and improve products. | Medium | SI004 |
| CI012 | MotherDuck’s terms reserve the right to modify or discontinue the service and cap aggregate liability at $100. | Medium | SI004 |
| CI013 | Business Insider reported the 2022 round at $47.5M, a $175M valuation, and warned that large workloads still favor Snowflake or BigQuery. | Medium | SI005 |
| CI014 | MotherDuck’s homepage says customers are shipping production apps, customer-facing analytics, and internal insights on the platform. | Medium | SI002 |
| CI015 | At launch, MotherDuck said it had 2,000 users querying the product and feedback from more than 100 users. | Medium | SI001 |
| CE001 | MotherDuck publicly frames its core product as a serverless analytics platform built on DuckDB for warehouse, lake-query, and data-app workflows. | High | SE001, SE002, SE003 |
| CE002 | The public homepage and announcement copy describe a notebook-like SQL environment that can query local and remote data through hybrid execution. | High | SE001, SE002 |
| CE003 | MotherDuck says each person, dashboard, and agent session gets its own isolated DuckDB instance, which it calls a duckling. | Medium | SE001 |
| CE004 | MotherDuck says its service supports organization-wide sharing and read scaling across multiple DuckDB nodes. | High | SE001, SE007 |
| CE005 | The launch and Series B materials describe an integration ecosystem that started with 16 integrations and then added 11 more partners. | High | SE002, SE003 |
| CE006 | MotherDuck positions itself for production apps, customer-facing analytics, and internal insights rather than only one narrow analytics use case. | High | SE001, SE003 |
| CE007 | The Terms of Use authorize MotherDuck to process customer data and usage data, including queries, prompts, and outputs, to provide and improve the service. | Medium | SE004 |
| CE008 | The Terms of Use also prohibit security testing without prior written consent, disclaim uninterrupted or secure service, and cap liability at $100. | Medium | SE004 |
| CE009 | An OHDSI community thread treats MotherDuck as a managed DuckDB service that could support synthetic-data distribution, Atlas demos, and GitHub Actions testing. | Medium | SE005 |
| CE010 | MotherDuck's public copy says it can query Parquet, Iceberg, or CSV where the data sits, so file-format compatibility is a core dependency of the workflow. | High | SE001, SE002, SE007 |
| CE011 | The GitHub-hosted MotherDuck model-data skill documents a code-first workflow for analytical schemas and transformation models using SQL files and a model manifest. | Medium | SE006 |
| CE012 | Raising.fi lists MotherDuck with $100M+ total funding across two rounds, but the page withholds detailed history behind a premium gate. | Medium | SE008 |
| CU001 | MotherDuck publicly positions the product for production apps, customer-facing analytics, and internal insights. | High | SU001, SU003 |
| CU002 | The public case-study page surfaces a multi-sector mix of named customer stories, including e-commerce, logistics, healthcare, finance, and AI. | Medium | SU003 |
| CU003 | MotherDuck said it had 2,000 users querying the product and more than 100 users providing feedback at open-for-all launch. | Medium | SU002 |
| CU004 | The duckfooding talk says an internal MotherDuck analytics system handles about 6,000 queries daily across 40 scheduled jobs. | Medium | SU004 |
| CU005 | Codecentric frames customer-facing analytics as needing sub-second responsiveness, tenant separation, and less OLTP overload, and places MotherDuck/DuckDB in that pattern. | High | SU005, SU001 |
| CU006 | MotherDuck's terms explicitly contemplate processing customer data and integrating with third-party platforms in customer workflows. | High | SU008, SU005 |
| CU007 | The AheadComputing case study reports that 74% of engineers onboarded onto MotherDuck within the first weeks. | Medium | SU003 |
| CU008 | The AheadComputing case study also says dashboard requests fell from three months to 1.5 hours and the rollout reached production in one week. | Medium | SU003 |
| CU009 | The Together AI case study says MotherDuck supported 128 unique Hex users across product teams, the C-suite, and the board. | Medium | SU003 |
| CU010 | The Together AI case study says 40 read-scaling replicas supported concurrent analytics and agent workloads without cost spikes or rate-limiting. | Medium | SU003 |
| CU011 | The GoodShip case study says it built an analytics agent on MotherDuck's remote MCP in under a week and saw sub-second queries where Postgres timed out. | Medium | SU003 |
| CU012 | A Reddit thread titled "Is MotherDuck ProDUCKtion-Ready?" shows a visible summary saying MotherDuck does not appear ready for use as a production data warehouse. | Low | SU006 |
| CU013 | Raising.fi lists MotherDuck with $100M total funding across two rounds, but its free profile does not surface customer-stickiness metrics. | Medium | SU007 |
| CU014 | On 2026-09-22, the public case-studies page remained accessible and still listed the named customer stories used in this chapter. | Medium | SU003 |
| CU015 | The visible customer set skews toward tech-forward companies using MotherDuck for analytics, agents, or internal BI rather than generic consumer commerce. | Medium | SU003, SU005 |
| CR001 | MotherDuck's homepage frames the product as fast, serverless analytics powered by DuckDB with dedicated compute for every user and agent. | Medium | SR001 |
| CR002 | MotherDuck says each person, dashboard, and agent session gets its own isolated DuckDB instance that spins up in milliseconds. | Medium | SR001 |
| CR003 | MotherDuck's public messaging emphasizes hybrid local-cloud query execution and use cases for production apps, customer analytics, and internal insights. | High | SR001, SR002 |
| CR004 | MotherDuck's terms authorize broad processing of customer and usage data, and they cap aggregate liability at $100. | Medium | SR003 |
| CR005 | MotherDuck reserves the right to modify, suspend, or discontinue the service at any time, including without notice. | Medium | SR003 |
| CR006 | The terms place third-party platform security, availability, and interoperability outside MotherDuck's control and liability. | Medium | SR003 |
| CR007 | MotherDuck publicly said it had 2,000 users querying on the platform and that total capital raised reached $100M, while GeekWire reported $47.5M of funding in November 2022. | High | SR002, SR005 |
| CR008 | MotherDuck's public positioning targets lightweight, cost-sensitive analytics for existing DuckDB users, analysts, and developers rather than the broadest possible petabyte-scale warehouse market. | High | SR005, SR002 |
| CR009 | The MotherDuck demo explains that its Delta log tracks appended and removed parquet files rather than mutating parquet data in place. | Medium | SR004 |
| CR010 | The same demo says that deleting data is logical in the Delta layer, so direct queries against raw parquet files can still surface rows that the table view excludes. | Medium | SR004 |
| CR011 | A third-party Skills Directory page lists a 'Motherduck Migrate To Motherduck' skill dated 2026-09-05, which indicates some external migration-tooling ecosystem activity. | Low | SR006 |
| CR012 | The Scribd fetch for a 'DuckDB in Action Final MotherDuck' document returned only an inaccessible load-failure page, so the underlying document contents remain unverified. | Low | SR007 |
| CR013 | A Reddit thread titled 'Am I making a mistake building on motherduck?' exists, but the fetch returned 403, so the underlying criticism could not be reviewed. | Low | SR008 |
| CV001 | MotherDuck's public site positions the company as a serverless data warehouse built on DuckDB with isolated compute per person and agent. | High | SV001, SV003 |
| CV002 | MotherDuck's own materials say the product supports hybrid query execution across local and cloud data and targets the large share of warehouse workloads that do not need petabyte-scale systems. | High | SV001, SV002 |
| CV003 | MotherDuck's September 2023 Series B added $52.5 million and brought disclosed total funding to $100 million. | High | SV002, SV006, SV007 |
| CV004 | Forge lists MotherDuck at a $496.48 million Series B+ valuation in May 2025 and shows a $400.9 million post-money valuation for the 2023 round. | Medium | SV004 |
| CV005 | GeekWire reported the 2023 round as $52.5 million at a $400 million valuation and said the company had 30 employees with plans to reach 45 by year-end. | Medium | SV007 |
| CV006 | CWI reported MotherDuck's earlier $47.5 million raise and framed the company as a cloud layer on DuckDB created through the DuckDB Labs partnership. | High | SV006, SV007 |
| CV007 | MotherDuck's terms of use allow broad processing of customer and usage data while capping aggregate liability at $100. | Medium | SV005, SV001 |
| CV008 | MotherDuck's startup program offers $16,000 of credits for an $8,000 annual commitment and limits eligibility to startups with fewer than 20 employees and less than $5 million in VC funding. | Medium | SV008, SV001 |
| CV009 | MotherDuck's August 2026 post says the company now offers enterprise support and that users run millions of DuckDB instances, or 'ducklings,' each week. | High | SV003, SV001 |
| CV010 | MotherDuck's current architecture messaging gives each person, dashboard, and agent an isolated DuckDB instance, which reinforces the agent-first positioning. | High | SV001, SV003 |
| CV011 | Forge's page frames the quote as a secondary-market indicator with limited activity and $133 million in total funding, so the displayed mark should be treated as a market signal rather than a definitive exit price. | Medium | SV004 |
| CV012 | The public sources here do not disclose current ARR, gross margin, or net revenue retention, so the valuation view has to lean on funding marks, product posture, and legal terms. | High | SV004, SV005, SV006, SV007, SV002 |
| ID | Publisher | Title | Quote |
|---|---|---|---|
| SO001 | MotherDuck | MotherDuck | The Cloud Data Warehouse Built on DuckDB | Fast, serverless analytics powered by DuckDB — with dedicated compute for every user and every agent. |
| SO002 | MotherDuck | Big Data is Dead | MotherDuck | The world in 2023 looks different from when the Big Data alarm bells started going off. |
| SO003 | TechCrunch | MotherDuck launches its DuckDB-based cloud analytics platform | Open source database company MotherDuck, which has raised a total of $47.5 million, today announced the launch of its serverless cloud analytics platform. |
| SO004 | Built In | MotherDuck Company Growth, Stability & Outlook 2026 | Strengths in capital access, geographic/commercial expansion, and ecosystem partnerships are accompanied by a narrower competitive position versus incumbents and a focused customer segment with potential pricing headwinds. |
| SO005 | Raising.fi | MotherDuck - Company Profile & Funding Data | Raising.fi | Total Funding $100M+; First Raise Nov 15, 2022; Latest Raise Sep 20, 2023. |
| SO006 | Dealroom | MotherDuck company information, funding & investors | MotherDuck is a serverless data warehouse built on the open-source DuckDB in-process analytics database. Founded in 2022 and headquartered in Seattle. |
| SO007 | MotherDuck | Duck and Roll: MotherDuck is Open for All With $100M in the Nest! | This round brings the total capital raised to $100M. |
| SO008 | MotherDuck | MotherDuck: Terms of Use | BY ACCESSING OR USING THE SERVICES, YOU AGREE THAT YOU HAVE READ AND UNDERSTOOD. |
| SM001 | MotherDuck | MotherDuck | The Cloud Data Warehouse Built on DuckDB | Production apps, customer-facing analytics, and internal insights — shipped on MotherDuck. |
| SM002 | MotherDuck | The Best Data Warehouse for Startups in 2026 | The Smart Hub (e.g. DuckDB-based) |
| SM003 | MotherDuck | Duck and Roll: MotherDuck is Open for All With $100M in the Nest! | This round brings the total capital raised to $100M. |
| SM004 | MotherDuck | MotherDuck: Terms of Use | The Services provides information about MotherDuck’s serverless data analytics platform. |
| SM005 | SiliconANGLE | Exclusive: MotherDuck adds agentic data ingestion to its cloud analytics service | MotherDuck's cloud service currently has about 850 paying customers after 18 months of commercial operation. |
| SM006 | Bytebase | MotherDuck, from SQLite to the Docker for Data | MotherDuck commercializes the open-source DuckDB. |
| SM007 | Amplify Partners | Our Investment in MotherDuck | smaller, faster data |
| SM008 | VentureRadar | Similar companies to MotherDuck | Companies like MotherDuck. |
| SP001 | MotherDuck | MotherDuck | The Cloud Data Warehouse Built on DuckDB | Hybrid local-cloud processing: Query local data or scale to the cloud seamlessly. |
| SP002 | MotherDuck | Duck and Roll: MotherDuck is Open for All With $100M in the Nest! | This round brings the total capital raised to $100M. |
| SP003 | MotherDuck | MotherDuck: Terms of Use | You grant MotherDuck a non-exclusive, worldwide, sublicensable right to Process Customer Data ... and Usage Data for internal business purposes. |
| SP004 | Wikipedia | MotherDuck | MotherDuck is a serverless cloud analytics platform ... built on the open-source DuckDB database system. |
| SP005 | Raising.fi | MotherDuck - Company Profile & Funding Data | Raising.fi | Total Funding $100M+. |
| SP006 | DBCode | MotherDuck Database Management in VS Code | DBCode enhances your MotherDuck experience with: SQL query editor, data preview, file import integration, query performance visualization, and results export. |
| SP007 | Data Engineering Central | Honest review of MotherDuck - by Daniel Beach | What MotherDuck has done with DuckDB in the cloud is insane, the entire experience end to end is bullet and idiot proof. |
| SP008 | MotherDuck | DuckDB vs SQLite: Which Embedded Database Should You Use? | MotherDuck | DuckDB outperforms SQLite significantly for analytical queries involving aggregations, joins, and large datasets. |
| SI001 | MotherDuck | Duck and Roll: MotherDuck is Open for All With $100M in the Nest! | Today ... this round brings the total capital raised to $100M. |
| SI002 | MotherDuck | MotherDuck | The Cloud Data Warehouse Built on DuckDB | Customers building on MotherDuck Production apps, customer-facing analytics, and internal insights |
| SI003 | MotherDuck | MotherDuck: Startup Program | For an $8,000 annual commitment, qualifying startups get $16,000 worth of MotherDuck. |
| SI004 | MotherDuck | MotherDuck: Terms of Use | TO THE FULLEST EXTENT PERMITTED BY LAW, THE AGGREGATE LIABILITY ... IS LIMITED TO $100. |
| SI005 | Business Insider | Andreessen Horowitz bets millions on emerging startup MotherDuck to build data analytics tech for companies that don't need all the oomph pushed by cloud giants | The round comes at a $175 million valuation. |
| SI006 | Sacra | MotherDuck funding, news & analysis | MotherDuck is a B2B SaaS company with a consumption-based pricing model built around compute and storage usage. |
| SI007 | Tracxn | MotherDuck | MotherDuck has 160 employees as of Aug 26. |
| SI008 | Raising.fi | MotherDuck - Company Profile & Funding Data | Raising.fi | MotherDuck (Technology, Software & SaaS) - View funding rounds, investors, capital raised ($100 Million). |
| SE001 | MotherDuck | MotherDuck | The Cloud Data Warehouse Built on DuckDB | Every person, dashboard, and agent session gets its own isolated DuckDB instance — a Duckling — spun up in milliseconds. |
| SE002 | PR Newswire | MotherDuck Raises $52.5 Million Series B Funding as DuckDB Adoption Soars | MotherDuck, builder of a serverless, easy to use data analytics platform based on open source database DuckDB, today announced a $52.5 million round of funding. |
| SE003 | MotherDuck | Duck and Roll: MotherDuck is Open for All With $100M in the Nest! | This round brings the total capital raised to $100M. |
| SE004 | MotherDuck | MotherDuck: Terms of Use | You also represent and warrant that your submission of Prompts to us will not violate these Terms or any laws applicable to those Prompts. |
| SE005 | OHDSI Forum | Evaluating the Potential of MotherDuck for Enhancing OHDSI's Open-Source Ecosystem | We could benefit from switching other resources to MotherDuck, but I would not be the right person to comment. |
| SE006 | GitHub | agent-skills/skills/motherduck-model-data/SKILL.md at main | Design or implement MotherDuck analytical schemas and transformation models, including grain, types, and materialization. |
| SE007 | MotherDuck | DuckDB vs SQLite: Which Embedded Database Should You Use? | The MotherDuck cloud data warehouse is powered by DuckDB and allows DuckDB to scale to the cloud with concurrent queries, a data catalog and organization-wide sharing. |
| SE008 | Raising.fi | MotherDuck - Company Profile & Funding Data | Total Funding $100M+ Total Rounds 2 |
| SU001 | MotherDuck | MotherDuck | The Cloud Data Warehouse Built on DuckDB | Customers building on MotherDuck Production apps, customer-facing analytics, and internal insights — shipped on MotherDuck. |
| SU002 | MotherDuck | Duck and Roll: MotherDuck is Open for All With $100M in the Nest! | Since the launch, we’ve had 2,000 users querying on MotherDuck and are grateful to have received feedback from over a hundred users. |
| SU003 | MotherDuck | Case Studies | MotherDuck | Building a Data Platform for the Agent Era at AheadComputing - 1 week to production |
| SU004 | MotherDuck | Duckfooding at MotherDuck | MotherDuck | The system now handles about 6,000 queries daily across 40 scheduled jobs. |
| SU005 | codecentric AG | Customer-facing analytics with DuckDB and MotherDuck | Especially in SaaS scenarios you need to ensure tenant separation. |
| SU006 | Is MotherDuck ProDUCKtion-Ready? : r/dataengineering - Reddit | MotherDuck the data warehouse does not appear to be ready for use as a production data warehouse. | |
| SU007 | Raising.fi | MotherDuck - Company Profile & Funding Data | Raising.fi | MotherDuck (Technology, Software & SaaS) - View funding rounds, investors, capital raised ($100 Million), and investment data. |
| SU008 | MotherDuck | MotherDuck: Terms of Use | Certain features of the Services may enable integration with third-party platforms, add-ons, services, or products not provided by MotherDuck. |
| SR001 | MotherDuck | MotherDuck | The Cloud Data Warehouse Built on DuckDB | Every person, dashboard, and agent session gets its own isolated DuckDB instance. |
| SR002 | MotherDuck | Duck and Roll: MotherDuck is Open for All With $100M in the Nest! | This round brings the total capital raised to $100M. |
| SR003 | MotherDuck | MotherDuck: Terms of Use | MotherDuck may modify or discontinue the Services at any time. |
| SR004 | MotherDuck | Leveraging DuckDB and Delta Lake Together | MotherDuck | Delta log basically says pretend to delete this data just like just don't read from it anymore. |
| SR005 | GeekWire | Seattle data analytics startup MotherDuck emerges from stealth, reveals $47.5M in funding | MotherDuck, valued at $175 million, was founded by Jordan Tigani. |
| SR006 | Skills Directory | Motherduck Migrate To Motherduck (Grade A) - Claude Skill | Security-tested ai-agents skill for Claude AI. |
| SR007 | Scribd | Client Challenge | A required part of this site couldn’t load. |
| SR008 | Am I making a mistake building on motherduck? | Target URL returned error 403: Forbidden. | |
| SV001 | MotherDuck | MotherDuck | The Cloud Data Warehouse Built on DuckDB | Customers building on MotherDuck Production apps, customer-facing analytics, and internal insights — shipped on MotherDuck. |
| SV002 | MotherDuck | Duck and Roll: MotherDuck is Open for All With $100M in the Nest! | This round brings the total capital raised to $100M. |
| SV003 | MotherDuck | DuckDB outgrows its nest | MotherDuck now offers enterprise support. |
| SV004 | Forge Data LLC | MotherDuck IPO Timeline and Financing Details - Forge | Series B+ Valuation, May 2025 |
| SV005 | MotherDuck | MotherDuck: Terms of Use | TO THE FULLEST EXTENT PERMITTED BY LAW ... the aggregate liability ... is limited to $100. |
| SV006 | CWI | CWI spin-off DuckDB Labs partners with MotherDuck, who raises $47.5 million | MotherDuck managed to raise $47.5 million. |
| SV007 | GeekWire | Seattle startup MotherDuck raises $52.5M at a $400M valuation to fuel DuckDB analytics platform | The Series B round pushes its post-money valuation to $400 million. |
| SV008 | MotherDuck | MotherDuck: Startup Program | For an $8,000 annual commitment, qualifying startups get $16,000 worth of MotherDuck. |