Hacker News new | ask | show | jobs
by chrisjc 1506 days ago
What are some potential long-term liabilities we might see in choosing to adopt duckdb today?

Obviously there will be a desire to monetize this project, if not for the very simple reason of subsidizing the cost of its development and maintenance. I love everything I hear and see about this project, but it makes me nervous to recommend this internally due to it not only being in such an early stage, but also bc of any unforeseen costs and liabilities that it might introduce in the future.
1 comments
1egg0myegg0 1506 days ago
Let me see if I can assuage some of your concerns!

First off - DuckDB is MIT licensed, so you are welcome to use and enhance it essentially however you please!

DuckDB Labs is a commercial entity that offers commercial support and custom integrations. (https://duckdblabs.com/). If the MIT DuckDB works for what you need, then you are all set no matter what!

However, much of the IP for DuckDB is owned by a foundation, so it is independent of that commercial entity. (https://duckdb.org/foundation/)

Does that help? Happy to answer any other questions!

link
chrisjc 1502 days ago
Absolutely. I think DuckDB's future is bright and excited to hopefully work with it in the near future.
link