Adam E.

Hi Mauricio, Thanks for reaching out. There's a PR already in place on the DuckLabs side. Once the fix has been merged, we'll backport the fixes on our side and ship it with the next duckling release.

Sounds great. Like our engineer said, you shouldn't need to go through additional procurement. Better safe than sorry in a corporate environment.

You can read the license within the DuckDB UI. Reading through it, it looks like standard MIT license.

The closed-source portion is still considered MIT-licensed. You should not need to go through any additional procurement. This comes straight from the engineer who built the UI.

The UI extension is under the standard MIT license.

Got it. Basically, the DuckDB UI extension loads a local HTTP server, pulls the latest UI assets from the DuckDB UI server (ui.duckdb.org), and starts the UI in browser. You're not buying anything or signing additional terms. The ultimate intention is to open source the extension entirely.

Can you tell me a bit about your concern? Are you more concerned about ownership of data, modifying the DuckDB UI, or something else? I'd like to connect with the right folks about this.

Valid question.

Hi! Yes, the local UI is free to use by running duckdb -ui. It is closely related to our MotherDuck UI, and in fact is our contribution back to the DuckDB project 😄