The title is misleading. AWS acquired DuckLabs, NOT DuckDB. The DuckDB source code is still owned by the nonprofit DuckDB Foundation.
Quote from the article:
"As the CWI representative on the DuckDB Foundation... When DuckLabs spun out of CWI, we created this foundation, which holds all IP of open-source DuckDB, and will continue to do so." - Peter Boncz
You are right.
AWS did not acquire the DuckDB technology itself, which is MIT-licensed open source and governed by the DuckDB Foundation which holds most of the related IP [1].
What they did acquire is DuckLabs, the Amsterdam-based services and development company behind the technology which is owned by and employs the creators and major contributors.
And MotherDuck is a US-based venture-funded commercial company, whose cloud-based data platform is centered around DuckDB but has been significantly expanded recently, including Python pipelines, an agentic context layer, and a visualisation layer.
[1]: https://duckdb.foundation/
[2] https://ducklabs.com/
[3] https://motherduck.com/
Interesting to see how they will update their About page.
Currently it says “Today, DuckLabs remains independent and fully owned by the original creators. We've deliberately chosen not to take venture capital, so we can focus on sustainable engineering, correctness, and keeping DuckDB open and MIT-licensed for everyone. “
Future will tell if that ends up being true.
>...sustainable engineering, correctness, and keeping DuckDB open and MIT-licensed for everyone
Hah. Never have I ever heard a sentence that described Amazon less.
what do you mean? amazon maintains a ton of open source projects, including a pure FOSS version of Elasticsearch called Opensearch
Top-level troll: that's not a "version" of Elastic Search, it's a fork of ES specifically created due to ES's licence change that made it more difficult for AWS to extract money from it at Elastic's expense.
Not that I like either actor in this particular play, but this isn't exactly an example of community oriented goodwill on Amazon's part.
No one's asking for "community oriented goodwill", just "sustainable engineering, correctness, and keeping DuckDB open and MIT-licensed for everyone". OpenSearch is a perfectly good example of Amazon maintaining an openly licensed open-source project.
I can’t tell if you are trolling or just oblivious.
Open search wasn’t precisely born out of the kindness of their heart and their defence of FOSS values… it’s more like a predatory practice to capture market.
I would agree that they very much had business decisions around the fork - but calling them malicious is bizarre.
They used the software in a way that complied with the license. When the license changed to no longer suit them for future releases, they forked from the original license.
Remove the names here, and in context, every single person familiar with open source projects and licensing would think this is a nonissue. They used the software as the license was intended, and exercised the rights given to them by that license. That freedom to fork if they don't like where the project is going, or things change and the project is no longer viable for them with the new license, is one of the key freedoms enshrined in the whole FOSS movement.
:-D
Yes I think motherduck is going to get ... well motherducked bad by AWS
Amazon is actually pretty good about open sourcing core technologies like that. Firecracker is a big one. They also support Valkey and pay some of its maintainers.
The past tells us not to hold our breath
They now updated it. That bit is indeed gone.
Still says
>Independence: We are fully founder-owned and not externally funded. Our priorities align with the long-term health of the project and its users.
smells like redhat
This is an important distinction, I hope the title can be changed.
I was really surprised when I first came across DuckDB at how good at it is for its target use cases. It is a game changer for me for the "local analytics" space, and its ability to scale up to a large degree helps a lot.
It is simply awesome to be able to point DuckDB at a mess of CSV and other files and have an instant database on top of it that I can run regular SQL over, and it is fast and just works.
It’s faster than trino and spark for 99% of your use cases. Only once the datasets reach the 100GiB to TiB range is trino/spark faster. Compute is scaling vertically faster than Data Eng/Analytics dataset growth, over time DuckDB will be the better choice.
No way spark is faster at 100 GB!
Not sure why the submitter changed the title from the page: "DuckLabs to Join AWS, Projects to Remain Open Source"
For clicks
Fixed above. Thanks!
you raised a good point but (et al) didn't touch on the meaningful questions: where does the "core team" of developers of DuckDB now reside? are they now "captured/cashing-in/getting paid" at AWS, or will meaningful MIT-licensed development of DuckDB continue in a robust way outside of commercial enterprises with proprietary needs that are not aligned with where the project was going?
What about motherduck?
It is not misleading at all. For all these softwares, the team that behind is the most important part rather than the software itself.