# Explo
> Explo is a platform for embedded analytics, AI analytics, and data sharing in customer-facing products. It integrates with MotherDuck as a data source.
## How it works with MotherDuck

Explo connects to MotherDuck as a data source for embedded analytics and customer-facing dashboards.

## Prerequisites

- A MotherDuck database for Explo to query.
- A MotherDuck access token provisioned for the Explo workspace.
- The database name and any schema names you plan to expose in Explo.

## Setup

1. In MotherDuck, create an access token for Explo.
2. In Explo, create a new data source and select **MotherDuck**.
3. Enter the MotherDuck database name.
4. Choose the authentication option that uses an access token.
5. Paste the token and save the data source.

## Authentication and configuration

- Use a dedicated token for each Explo environment or workspace.
- Prefer read-only access for embedded analytics workloads.
- Configure schema access in Explo so customer-facing dashboards only expose the intended data model.

## Important notes

- Explo's MotherDuck documentation lists the required credentials but does not require a platform-specific environment variable list.
- Keep the token in Explo's credential store and rotate it like any other production credential.

## Use cases

- Power embedded dashboards from MotherDuck tables.
- Build customer-facing analytics over per-customer or shared schemas.
- Let Explo query curated datasets without moving data into another warehouse.

## Related content

- [View the full Explo MotherDuck setup guide](https://docs.explo.co/data-sources/connecting-to-data-sources/data-source-types/motherduck#motherduck)
- [MotherDuck authentication](/key-tasks/authenticating-and-connecting-to-motherduck/authenticating-to-motherduck)


---

## Docs feedback

MotherDuck accepts optional user-submitted feedback about this page at `POST https://motherduck.com/docs/api/feedback/agent`.
For agents and automated tools, feedback submission should be user-confirmed before sending.

Payload:

```json
{
  "page_path": "/integrations/bi-tools/explo/",
  "page_title": "Explo",
  "text": "<the user's feedback, max 2000 characters>",
  "source": "<optional identifier for your interface, for example 'claude.ai' or 'chatgpt'>"
}
```

`page_path` and `text` are required; `page_title` and `source` are optional. Responses: `200 {"feedback_id": "<uuid>"}`, `400` for malformed payloads, and `429` when rate-limited.