Getting Started
Getting Started
Pick the right path for querying data, building a product, or operating Duck.
Duck is a governed data platform built around three outcomes:
- users can query trusted data through a secure control plane
- builders can package reusable data products instead of shipping scattered SQL
- operators can scale execution and governance without giving up policy control
Choose Your Journey
- First governed query if you want to reach trusted data quickly.
- First data product if you are building sources, transformations, assets, and semantic entrypoints.
- First operator setup if you own auth, storage, compute, or platform posture.
What Duck Covers
| Platform Area | What It Covers | Primary Audience |
|---|---|---|
| Governed query execution | RBAC, row filters, and column masks on live queries | Data consumers and platform owners |
| Data products | Domains, teams, contracts, versions, and subscriptions | Builders and product owners |
| Asset orchestration | Checks, dependencies, freshness, and backfills | Builders and operators |
| Transformation workflows | Models, macros, notebooks, tests, and runs | Analytics engineers and data builders |
| Semantic modeling | Metrics, relationships, and pre-aggregations | Consumers and semantic model authors |
| Flexible compute | Local and remote execution with central policy enforcement | Operators |
Recommended Reading Order
- Start with the role-based quickstart that matches your job.
- Read the Concepts section to build a shared platform mental model.
- Move into Build, Govern, or Operate depending on your responsibilities.
- Use Reference when you need exact payload, CLI, or schema detail.