Skip to main content

MotherDuck

MotherDuck is a cloud-native DuckDB service that provides scalable analytics and data processing capabilities. Built on the same core engine as DuckDB, MotherDuck offers the familiar SQL interface and performance characteristics while adding cloud-native features like serverless compute, automatic scaling, and collaborative data sharing.


Rill supports connecting to MotherDuck and using it as an OLAP engine to power dashboards. This is particularly useful when you want the performance and SQL compatibility of DuckDB with the scalability and collaboration features of a cloud service.

Supported Versions

Rill supports connecting to MotherDuck using the latest DuckDB-compatible drivers and protocols.

Configuring Rill Developer with MotherDuck​

When using MotherDuck for local development, you can connect using your MotherDuck access token. The connection is established through MotherDuck's secure API endpoints.

  1. Connect to your OLAP engine via Add Data. This will automatically create the motherduck.yaml file in your connectors folder and populate the .env file with .connector.motherduck.token.

For more information on supported parameters, see our MotherDuck connector YAML reference docs.

Getting Your MotherDuck Access Token​


To connect to MotherDuck, you'll need a access token from your MotherDuck account:

  1. Log in to your MotherDuck account
  2. Navigate to the Settings section
  3. Go to Access Tokens
  4. Create a new access token or copy an existing one
  5. Use this token as the value for motherduck_token in your .env file
Keep Your Token Secure

Your MotherDuck access token provides access to your data. Keep it secure and never commit it directly to version control. Always use environment variables or secure credential management.

Connection Configuration​

MotherDuck connections are established through secure API endpoints. The connection is automatically configured when you provide your access token:

motherduck.token="your_motherduck_service_token_here"

Configuring Rill Cloud​

When deploying a MotherDuck-backed project to Rill Cloud, you have the following options to pass the appropriate access token:

  1. If you have followed the UI to create your MotherDuck connector, the token should already exist in the .env file. During the deployment process, this .env file is automatically pushed with the deployment.

  2. If motherduck_token has already been set in your project .env, you can push and update these variables directly in your cloud deployment by using the rill env push command.

  3. If you manually passed the connector when running rill start, you will need to use the rill env configure command to set motherduck_token onto Rill Cloud as well.

info

Note that you must cd into the Git repository that your project was deployed from before running rill env configure.

Setting the Default OLAP Connection​

Creating a connection to MotherDuck will automatically add the olap_connector property in your project's rill.yaml and change the default OLAP engine to MotherDuck.

olap_connector: motherduck
Interested in using multiple OLAP engines in the same project?

Please see our Using Multiple OLAP Engines page.

Additional Notes​

  • MotherDuck uses the same SQL syntax as DuckDB, so all standard DuckDB functions and features are available
  • For dashboards powered by MotherDuck, measure definitions should follow standard DuckDB SQL syntax
Need help connecting to MotherDuck?

If you would like to connect Rill to MotherDuck or need assistance with setup, please don't hesitate to contact us. We'd love to help!