MotherDuck
Consumption-based B2B SaaS on a freemium base; free tier for individuals, paid plans plus usage-based compute credits ('Ducklings'). Built on and gives back to open-source DuckDB (open-core-adjacent).
Nov-2022 and Sep-2023 valuations are confirmed post-money figures. The May-2025 Series B+ valuation was not disclosed; the point is held flat at the last confirmed $400M as a floor, not a reported mark — the modest $33M size implies a flat-to-modestly-up round, not a breakout markup.
Earnings, margins, COGS & capex
Private, venture-funded, pre-profitability. Raised ~$133M total: a $47.5M seed+Series A in Nov 2022 ($12M seed led by Redpoint + $35M Series A led by a16z, at $175M post-money), a $52.5M Series B (Sep 2023, led by Felicis at $400M post-money), and a $33M Series B+ (May 2025, valuation undisclosed). No revenue, margin, or burn figures are officially disclosed. The economic story is a bet that a large share of real-world analytics workloads are under ~10-20TB and are over-served (and over-charged) by Snowflake/Databricks/BigQuery, and that a DuckDB-based, single-node-plus-cloud engine can serve them far more cheaply.
Revenue trend
Margins
n/a
n/a
n/a
COGS structure
Primarily cloud compute/storage (AWS) for serverless query execution plus data-egress and support. Hybrid execution pushes work to the client, which can lower server-side COGS per query vs. an all-cloud warehouse. Actual figures not disclosed.
Capex
Minimal owned capex — infrastructure is rented cloud capacity. R&D headcount (engineering + DevRel) and cloud spend are the dominant cash uses, not capitalized hardware.
Latest earnings
n/a
n/a
- Total funding raised
- ~$133M
- Last confirmed valuation
- ~$400M post (Series B, Sep 2023)
- Prior valuation
- ~$175M post (seed+A, Nov 2022)
- Founded
- 2022, Seattle
- Ducklings cold-start (company claim)
- ~30ms serverless compute start
Growth drivers
- Explosive open-source DuckDB adoption feeding a top-of-funnel of already-proficient users
- AI-native SQL features (text-to-SQL, FixIt debugging, Instant SQL) lowering the skill barrier
- DuckLake managed lakehouse format — treating object storage as a warehouse extension while keeping DuckDB syntax
- Larger instance tiers (Mega/Giga) to move upmarket into bigger workloads
- EU cloud region (Frankfurt, AWS eu-central-1) announced Sep 2025 for data-residency demand
- Cost-conscious buyers seeking cheaper alternatives to Snowflake/BigQuery for sub-20TB analytics
Bull & bear
MotherDuck is the commercial front door to the DuckDB wave — a category-defining open-source engine — led by a founder who literally helped build the incumbent he's now undercutting, aimed at the (large, underserved) majority of analytics workloads that don't need a Snowflake-sized bill.
- DuckDB adoption is compounding; MotherDuck converts that free community into paying cloud usage with near-zero paid CAC
- The 'most data is small' thesis is directionally right — a huge share of real workloads sit under 20TB and are massively over-provisioned today
- Hybrid local+cloud plus a ~30ms serverless compute cold-start (company claim) delivers a real latency/cost advantage that incumbents' architectures can't easily copy
- AI-native SQL (text-to-SQL, FixIt, Instant SQL) expands the addressable user base beyond expert analysts
- Top-tier syndicate and a still-modest ~$400M last valuation leave room for large multiple expansion if ARR inflects
- DuckLake gives it a credible open-lakehouse wedge into larger, sticky data estates
MotherDuck sells a paid cloud on top of a free engine, into a category owned by three deep-pocketed incumbents and several funded challengers — with no disclosed revenue to prove customers will pay at scale, and a real risk the value it adds gets commoditized.
- The core engine is free and open-source — many teams will self-host DuckDB (or use pg_duckdb / embedded DuckDB) and never pay MotherDuck
- Snowflake, Databricks, and Google BigQuery can price-cut, bundle, or ship DuckDB-compatible offerings and squeeze the mid-market wedge
- Deliberately targeting smaller workloads caps ARPU and raises the risk that fast-growing customers graduate to a bigger warehouse
- No disclosed revenue/growth/margins — the commercial engine is unproven; the small $33M Series B+ in 2025 at an undisclosed valuation hints at a measured, not breakout, trajectory
- Dependence on DuckDB Labs for core roadmap creates strategic/technical risk it doesn't fully control
- Crowded field (ClickHouse, Firebolt, SingleStore, plus incumbents) competing for overlapping fast-analytics demand in a tight funding environment
What it is worth
Private-market / last-round + VC scenario framing (no public price or reliable revenue multiple available).
Sub-$300M or a soft acqui-hire outcome if monetization stalls, incumbents bundle/undercut, or self-hosted DuckDB captures the value — pre-revenue-scale infra is vulnerable in a tight funding climate.
Roughly $400M-$700M range — a credible, growing challenger in the mid-market analytics niche, valued on promise and community rather than proven scale; likely needs another round to reach breakout.
$1B+
if DuckDB-driven ARR inflects and MotherDuck becomes the default cloud for the DuckDB ecosystem, moving upmarket via DuckLake/larger tiers — a plausible unicorn on continued category momentum.
Last confirmed valuation ~$400M post-money (Series B, Sep 2023), up from ~$175M post (seed+A, Nov 2022). A $33M Series B+ (May 2025) was raised at an undisclosed valuation — the modest size suggests a flat-to-modestly-up round rather than a breakout markup. Revenue is not disclosed, so any multiple is speculative. Value hinges on converting DuckDB's open-source adoption into durable paid ARR.
SWOT
Strengths
- Rides one of the fastest-growing open-source data projects (DuckDB) — a built-in, self-selecting developer funnel and brand halo
- Founder-market fit — CEO Jordan Tigani was a founding engineer on Google BigQuery and authored the influential 'Big Data Is Dead' thesis that underpins the product bet
- Genuinely differentiated hybrid local+cloud execution — fast, cheap, and low-latency for the common sub-20TB case
- Strong, top-tier investor syndicate (Felicis, a16z / Andreessen Horowitz, Redpoint, Madrona, Amplify, Altimeter)
- Asset-light, favorable unit economics potential vs. heavier warehouse architectures
Weaknesses
- No disclosed revenue and small absolute scale — commercially unproven vs. entrenched incumbents
- Monetizing open-source DuckDB, which is itself free — must continually justify paying MotherDuck over self-hosting DuckDB
- Deliberately scoped to smaller data sizes — must prove it can move upmarket without losing its cost/simplicity edge
- Dependent on a separate organization (DuckDB Labs) for the core engine's roadmap
- Crowded, capital-heavy category where incumbents can bundle and undercut
Opportunities
- Capture the 'big-enough data' mid-market that finds Snowflake/Databricks overkill and overpriced
- Become the default cloud endpoint for the millions of DuckDB users as they scale from laptop to team
- Lakehouse land-grab via DuckLake as an open, DuckDB-native table format
- AI/agent workloads that need fast, cheap, iterative SQL — text-to-SQL and embedded analytics
- Embed into application/data-app builders and vertical SaaS as the analytics engine
Threats
- Incumbents (Snowflake, Databricks, Google BigQuery) can add DuckDB compatibility, cut prices, or bundle equivalents
- DuckDB's own ubiquity commoditizes the layer MotherDuck sells; pg_duckdb and others embed the engine elsewhere
- Well-funded low-latency rivals (ClickHouse, Firebolt) chasing overlapping workloads
- Macro/AI-spend reallocation and a tough venture climate for pre-revenue-scale infra startups
- Long path to the scale/valuation that justifies later rounds or an IPO/M&A exit
Moats, dependencies & bottlenecks
Moats
Powerful top-of-funnel and brand, but the community can also route around paying MotherDuck.
Tigani's BigQuery pedigree and thought-leadership drive trust and hiring, but talent moats erode.
Real engineering edge today; architecturally copyable by well-resourced incumbents over time.
Warehouses get sticky once data and pipelines land; MotherDuck is early on accumulating this.
Standards-based lock-in play, but open formats cut both ways and face Iceberg/Delta competition.
Dependencies
The entire product is built on the DuckDB engine, stewarded by a separate organization.
Cloud infrastructure Serverless compute/storage runs on public cloud; exposes MotherDuck to a competitor-adjacent supplier.
Pre-profit; depends on continued fundraising until revenue self-funds.
Integration/distribution Adoption depends on fitting cleanly into existing pipelines and tools.
Advantages
- Near-zero paid customer-acquisition cost via the DuckDB open-source funnel
- Superior latency/cost for the common small-to-mid analytics workload
- AI-native SQL UX broadening the user base
- Elite investor and advisor network
- Asset-light economics with favorable long-run margin potential
Weaknesses
- No disclosed revenue or growth metrics — commercially unproven at scale
- Sells a paid layer on top of a free engine (weak inherent pricing power)
- Scoped to smaller data sizes, capping ARPU and inviting graduation risk
- Strategic dependence on an external core-engine team
- Exposed to incumbent bundling and price competition
Bottlenecks
- Converting free DuckDB users into paying cloud customers (monetization of an open engine)
- Proving it can scale upmarket beyond sub-20TB without losing cost/simplicity advantage
- Small absolute revenue base vs. capital-heavy incumbents
- Reliance on DuckDB Labs' roadmap for the core engine
- Enterprise trust/compliance/security maturity needed to win larger accounts
Top signals & trends
Top signals
Investors continued to fund it nearly two years after Series B — but the modest size and undisclosed valuation suggest steady, not breakout, momentum.
Geographic expansion implies enough demand/data-residency pull to justify EU infrastructure.
Product moves to court larger workloads and lakehouse use cases.
Opacity at this stage typically means scale is still modest relative to the category.
The upstream funnel MotherDuck monetizes keeps widening.
Trends
Core thesis that favors single-node-plus-cloud engines over massive distributed warehouses.
Fast, cheap, iterative query engines fit agent and copilot workloads well.
Opportunity via DuckLake, but also a competitive standards battle.
Buyers actively seek cheaper alternatives to Snowflake/BigQuery bills.
Snowflake/Databricks/Google can absorb or undercut the mid-market wedge.
Ecosystem & competitor graph
Suppliers feed the company; customers pull from it. Line thickness shows the strength of each tie (supply-chain dependency, customer earnings contribution). Hover to isolate a tie.
Steward of the open-source DuckDB engine at MotherDuck's core.
Underlying cloud compute/storage for the serverless platform.
Startups, SMBs, and mid-market data teams with sub-20TB workloads seeking cheaper/faster warehousing.
Products embedding analytics/SQL who want a fast, low-cost backend.
Dominant independent cloud data warehouse; the primary 'too big/too expensive for small data' incumbent MotherDuck positions against.
Private (~$100B+ last valuations); lakehouse leader expanding into warehousing/SQL and AI — broad platform competitor.
Serverless warehouse incumbent; MotherDuck's CEO came from its founding team, and it can add DuckDB-style features.
Private; fast open-source OLAP engine with a commercial cloud — overlapping low-latency analytics workloads.
Private; low-latency cloud data warehouse targeting performance-sensitive analytics.
Private; real-time/HTAP database competing for fast analytics use cases.
Bundled analytics platform with enterprise distribution advantage.
The free engine itself — the 'do nothing / self-host' alternative is a structural competitor to MotherDuck's paid cloud.