--- title: DuckLabs (the company behind DuckDB) is joining AWS description: DuckLabs, the company behind DuckDB, is becoming a new subsidiary of Amazon Web Services, effective early September. DuckDB, DuckLake, Quack, and other... canonical: https://daily.dev/posts/ducklabs-the-company-behind-duckdb-is-joining-aws-tq2z4se6n twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: DuckLabs (the company behind DuckDB) is joining AWS | daily.dev og:description: DuckLabs, the company behind DuckDB, is becoming a new subsidiary of Amazon Web Services, effective early September. DuckDB, DuckLake, Quack, and other... og:url: https://daily.dev/posts/ducklabs-the-company-behind-duckdb-is-joining-aws-tq2z4se6n og:image: https://api.daily.dev/og/posts/tq2Z4SE6N.png og:image:alt: DuckLabs (the company behind DuckDB) is joining AWS og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # DuckLabs (the company behind DuckDB) is joining AWS **[Collections](https://daily.dev/sources/collections)** · 3 min read · 2 upvotes · 0 comments ## Summary DuckLabs, the company behind DuckDB, is becoming a new subsidiary of Amazon Web Services, effective early September. DuckDB, DuckLake, Quack, and other extensions remain free and open source under the MIT license, stewarded by the non-profit DuckDB Foundation, with roadmap, licensing, and governance unchanged. A stakeholder advisory board will be created, and prior limits on community support are being removed. Corey Quinn added a lighthearted anecdote about initially misreading the announcement as involving his own company, Duckbill Group. ## Content Amazon Web Services has signed a definitive agreement to acquire DuckLabs, the roughly 30-person Amsterdam company responsible for building and maintaining DuckDB, the popular open-source in-process analytical database. The deal is expected to close in early September, with DuckLabs operating as a wholly-owned AWS subsidiary. The open-source project itself isn't changing hands. DuckDB, DuckLake, Quack, and related extensions remain under the independent DuckDB Foundation, MIT-licensed, with the same governance model. AWS says it's establishing a stakeholder advisory board and lifting previous limitations on community support. ## What DuckLabs actually is It's worth being clear about the structure here, because it's easy to conflate the pieces. DuckDB is the open-source project. The DuckDB Foundation holds the IP and license. DuckLabs was the founding team and core maintainers — the people who actually write the code — operating as a separate commercial entity. MotherDuck is a distinct company that built a cloud service on top of DuckDB. AWS bought DuckLabs, not the project or the foundation. The DuckLabs team chose acquisition over venture funding, a decision that mirrors Databricks buying Tabular (the team behind Apache Iceberg's original development). The analogy is instructive: Databricks now has real influence over Spark, Delta Lake, and Iceberg without formally owning them. Expect something similar here. ## Why this makes sense for AWS Andy Warfield of AWS published a piece tracing the physics behind DuckDB's rise. The short version: modern single machines have enough RAM, fast-enough CPUs, and cheap-enough NVMe storage that many analytical workloads no longer need to be distributed across a cluster. MapReduce and Spark made sense when you couldn't fit data or compute on one box. That's less true now. DuckDB runs as an embedded library rather than a remote service, which means it goes where the data is rather than requiring data to move to it. AWS has been integrating DuckDB with S3 Tables and Iceberg support already. The acquisition accelerates that. Analysts expect AWS to embed DuckDB deeper into existing services — S3 Tables, SageMaker Lakehouse, Athena, Redshift, EMR, Glue — potentially building a serverless query layer against S3 and Iceberg tables without requiring users to spin up a separate cluster. DuckLake 1.0, DuckLabs' alternative to Apache Iceberg for table format management, also gives AWS a card to play in the ongoing open table format competition. ## What it means for the ecosystem The license keeps DuckDB portable, but AWS effectively becomes its de facto owner in the sense that matters most: the roadmap will reflect AWS priorities. That's not necessarily bad for users — AWS has strong incentives to keep DuckDB fast and widely adopted — but it's worth being clear-eyed about. MotherDuck's CEO, reflecting on four years of partnership with the DuckLabs team, welcomed the news and announced that MotherDuck is now offering enterprise support (something it previously avoided to not compete with DuckLabs directly). He drew a parallel to the Snowflake/BigQuery/Redshift era, suggesting that an eventual Amazon-built DuckDB cloud service would validate the market rather than kill it. The DuckDB project itself remains free. The people who built it now work for AWS. Whether those two facts stay compatible long-term is the question worth watching. ## Questions this post answers ### Is DuckDB still open source now that DuckLabs is joining AWS? Yes, DuckDB remains free and open source under the MIT license. DuckLabs, the company behind DuckDB, is becoming an AWS subsidiary effective early September, but DuckDB, DuckLake, Quack, and other extensions continue to be stewarded by the non-profit DuckDB Foundation, with the roadmap, licensing, and governance model unchanged. _Anyone relying on DuckDB for analytics can track licensing and governance updates like this on daily.dev._ ### What changes for DuckDB users after DuckLabs joins AWS? Little changes for users directly: licensing, roadmap, and governance remain the same, and DuckDB stays MIT-licensed. What is new is a stakeholder advisory board being established and previous limitations on community support being lifted, giving the community broader access to support going forward. _Teams evaluating DuckDB's future direction can follow governance changes like this on daily.dev._ --- Tags: [#open-source](https://daily.dev/tags/open-source), [#aws](https://daily.dev/tags/aws), [#backend](https://daily.dev/tags/backend), [#duckdb](https://daily.dev/tags/duckdb) [View this post on daily.dev](https://daily.dev/posts/ducklabs-the-company-behind-duckdb-is-joining-aws-tq2z4se6n) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"DuckLabs (the company behind DuckDB) is joining AWS","url":"https://daily.dev/posts/ducklabs-the-company-behind-duckdb-is-joining-aws-tq2z4se6n","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/ducklabs-the-company-behind-duckdb-is-joining-aws-tq2z4se6n"},"datePublished":"2026-08-26T13:16:32.257Z","dateModified":"2026-08-31T16:01:04.342Z","description":"DuckLabs, the company behind DuckDB, is becoming a new subsidiary of Amazon Web Services, effective early September. DuckDB, DuckLake, Quack, and other...","isAccessibleForFree":true,"articleSection":"Collections","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Collections","logo":"https://media.daily.dev/image/upload/s--fk_6ycEi--/f_auto,q_auto/v1780996001/logos/collections?_a=BAMAMiWQ0","url":"https://daily.dev/sources/collections"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/ducklabs-the-company-behind-duckdb-is-joining-aws-tq2z4se6n","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":2},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"open-source,aws,backend,duckdb","timeRequired":"PT3M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Collections","item":"https://daily.dev/sources/collections"},{"@type":"ListItem","position":3,"name":"DuckLabs (the company behind DuckDB) is joining AWS"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/ducklabs-the-company-behind-duckdb-is-joining-aws-tq2z4se6n#faq","mainEntity":[{"@type":"Question","name":"Is DuckDB still open source now that DuckLabs is joining AWS?","acceptedAnswer":{"@type":"Answer","text":"Yes, DuckDB remains free and open source under the MIT license. DuckLabs, the company behind DuckDB, is becoming an AWS subsidiary effective early September, but DuckDB, DuckLake, Quack, and other extensions continue to be stewarded by the non-profit DuckDB Foundation, with the roadmap, licensing, and governance model unchanged. Anyone relying on DuckDB for analytics can track licensing and governance updates like this on daily.dev."}},{"@type":"Question","name":"What changes for DuckDB users after DuckLabs joins AWS?","acceptedAnswer":{"@type":"Answer","text":"Little changes for users directly: licensing, roadmap, and governance remain the same, and DuckDB stays MIT-licensed. What is new is a stakeholder advisory board being established and previous limitations on community support being lifted, giving the community broader access to support going forward. Teams evaluating DuckDB's future direction can follow governance changes like this on daily.dev."}}]} ```