# Concepts
> How MotherDuck works: hypertenancy, Dual Execution, storage lifecycle, scaling patterns, and access control.
Understand how MotherDuck works, the serverless cloud data warehouse built on DuckDB. These pages explain the mental model behind the platform: hypertenancy, Dual Execution, storage lifecycle, and access control, so you know not just what to do but why it works the way it does.

## Included pages

- [Architecture and capabilities](https://motherduck.com/docs/concepts/architecture-and-capabilities): MotherDuck's serverless architecture combines cloud scale with DuckDB's efficiency through a hypertenancy model.
- [Compute and execution](https://motherduck.com/docs/category/compute-and-execution): How MotherDuck runs your queries and code: per-user Ducklings, where code runs, scaling patterns, Flights, and Results.
- [Database and storage](https://motherduck.com/docs/category/database-and-storage): How MotherDuck stores, names, versions, and recovers your data, including the storage lifecycle, snapshots, DuckLake, and object name resolution.
- [Security and access](https://motherduck.com/docs/category/security-and-access): How MotherDuck secures your data and controls access: the resource hierarchy, role-based access control, encryption, and compliance.
- [Extensions](https://motherduck.com/docs/category/extensions): DuckDB extensions supported in MotherDuck, and the pg_duckdb extension for running DuckDB inside PostgreSQL.


---

## Docs feedback

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

URL-encode query parameter values and send a GET request:

```text
GET https://motherduck.com/docs/api/feedback/agent?page_path=%2Fconcepts%2F&page_title=Concepts&text=<url-encoded user feedback, max 2000 characters>
```

Optionally append `&source=<url-encoded interface identifier>` such as `claude.ai` or `chatgpt`.

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