Feature Requests

We are evaluating MotherDuck for analyzing heavy streams of concurrent device telemetry generated by our network of industrial weighing systems and retail calibration hardware at Scales4U ( https://scales4u.co.za/ ). Currently, our edge sensors generate millions of transactional logging rows per hour across regional distribution nodes in South Africa. We are pushing this data into local DuckDB instances and syncing up to MotherDuck. It would be an absolute game-changer if MotherDuck introduced native background optimizations for handling continuous micro-batches or automated chronological Parquet partitioning for high-concurrency IoT telemetry. Are there any features on the roadmap to improve write performance for continuous sensor logging or specific time-series macros?

Personally can't justify $250/mo for my personal use case, but could definitely justify $50-100/mo to get access to non-Pulse instance types. Some sort of hobby/prosumer plan could be nice.

It would be a game changer if motherduck sql notebooks can be executed by schedule or triggers using an orchestrator (airflow, prefect ,dagster , etc.).

It would be great if I could somehow share a secret with other team members in my org, so that they can use the connection to cloud storage and don't have to create another connection on their own.

Support a single user being a member of more than one organization at the same time. This will help enable contract/consultancy workflows as well as enabling separate development/production workspaces

Today, only a single user can modify a database (while many users can read that database through the use of shares). It would be closer to a traditional data warehouse experience if multiple users could edit/insert/update/delete the same database. (Added on behalf of Dante Oz)

Currently this feature is broken, but works in DuckDB. Reference: https://duckdb.org/dev/profiling.html

Just like with the list_tables and list_columns tools, a list_functions tool would let the agent discover any functions defined as part of the current schema. It should include comments on those functions, just as the aforementioned tools do. It could be called list_macros instead, since these terms are used interchangeably in DuckDB.