# Concepts
> How MotherDuck works: hypertenancy, Dual Execution, database concepts, 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.
- [Database Concepts](https://motherduck.com/docs/concepts/database-concepts): MotherDuck Database Concepts
- [Hypertenancy](https://motherduck.com/docs/concepts/hypertenancy): Learn how MotherDuck's hypertenancy model provides dedicated compute for every user through per-user Ducklings, enabling predictable performance without noisy neighbors.
- [Resource management](https://motherduck.com/docs/concepts/resource-management): Understand MotherDuck's resource hierarchy, from organizations, accounts, tokens, and secrets down to databases and tables, and how each level provides compute isolation, data isolation, and access control.
- [Security and compliance](https://motherduck.com/docs/concepts/security): Overview of MotherDuck's security features including encryption, authentication, access control, network security, and compliance certifications.
- [Database Snapshots](https://motherduck.com/docs/concepts/database-snapshots): Understand how snapshots work in MotherDuck, including retention, restore, snapshot management, and plan availability
- [pg_duckdb Extension](https://motherduck.com/docs/concepts/pgduckdb): Use pg_duckdb to run DuckDB analytics within PostgreSQL and connect to MotherDuck.
- [Role-based access control (RBAC)](https://motherduck.com/docs/concepts/roles-and-access-control): Understand MotherDuck roles, including preset and custom roles, how platform privileges and data grants combine, and how permissions resolve.
- [Storage Lifecycle and Management](https://motherduck.com/docs/concepts/storage-lifecycle): Understand how MotherDuck manages data storage across different lifecycle stages and how this affects your billing and data management strategies.
- [Data Recovery](https://motherduck.com/docs/concepts/data-recovery): Understand MotherDuck's data recovery mechanisms
- [Flights](https://motherduck.com/docs/concepts/flights): How Flights run scheduled Python next to your MotherDuck data, and when to reach for one instead of SQL, a Dive, or an external orchestrator.
- [Workload scaling patterns](https://motherduck.com/docs/concepts/scaling-patterns): Choose the right compute size, scaling approach, and connection model for your MotherDuck workload using a decision flowchart and workload-to-pattern matrix.
- [Object name resolution](https://motherduck.com/docs/concepts/object-name-resolution): Fully qualified naming conventions and database resolution rules in MotherDuck.
- [Where code runs](https://motherduck.com/docs/concepts/execution-environments): Choose a local DuckDB client, MotherDuck cloud SQL, or a Flight based on the extensions, credentials, and schedule your workload needs.
- [DuckDB Extensions in MotherDuck](https://motherduck.com/docs/concepts/duckdb-extensions): Supported DuckDB extensions for the MotherDuck cloud service, Web UI, and CLI.
- [DuckLake](https://motherduck.com/docs/concepts/ducklake): Understanding DuckLake - A high-performance open table format for petabyte-scale analytics
- [Results](https://motherduck.com/docs/concepts/results): Results


---

## 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.