The data platformAgents can read
Declare your sources, your business and your metrics. Daana generates the warehouse tables and transformations, with definitions your team and AI agents can trace from every declared metric back to the source columns it comes from.
Need help building your data platform? Free assessment →The Daana CLI overview film
Describe the business. Generate the warehouse. Your team builds the source contracts and staging. Daana generates DAB and DAR from the model, mappings and reporting declarations.
- Model your business: entities, their attributes and the relationships between them, declared in YAML. The RC1 bookstore model has 43 entities and 71 relationships.
- Generate: daana deploy and daana execute generate the warehouse, and marts are generated from reporting declarations. Semantic models and graphs can be built from the same model. The bookstore example generates 43 current views and 71 relationship views. Daily revenue uses order_line_purchase_ts, separately from the landing-time history clock: 31 order lines, 762.88 USD across 16 order days, reconciled day by day.
- Ask: an agent answers a question about history, reading the definitions from the model. Two customers have lived in Boston; the recorded query returns six activities during those periods, including three event registrations.
Model. Generate. Ask.
Loading film…
The parts you'd hand‑write,
already handled.
Every warehouse needs these, and every team builds them again. In Daana they come from the model, the same way every time.
// NEXTORY · 01 MODEL ONCE
“The business logic is still fully visible, the transformations are still there, you just don't need to write the boilerplate code.”
- // 01
Model once, generate everything
Declare entities, attributes and relationships in YAML and map your sources to them. Daana generates the tables, a current and a history view per entity, and a view for every relationship. No schema copied across dbt models or stored procedures. Follow the warehouse example →
Explore warehouse automation →daana deploy - // 02
History is first-class, not bolted on
For every entity you declare, Daana generates the history: a history view and point-in-time functions. You don't write history SQL.
view_customer_hist - // 03
Multiple IDs are reality, not edge cases
A customer has an email, a customer number and a partner reference. Daana keeps up to five identifiers per entity and resolves them to one stable key, instead of making you pick the one true key and hack around it later.
allow_multiple_identifiers: true - // 04
Load strategies you can explain at 3am
Four ways in: FULL for current state, FULL_LOG for history, INCREMENTAL for rows that change, TRANSACTIONAL for events that never do. Pick one per source and move on. Compare loading strategies →
FULLFULL_LOGINCREMENTALTRANSACTIONAL - // 05
Merge, don't nuke
Your model evolves. Merge brings the mappings up to date: new attributes arrive with placeholders, removed ones go, and your transformation expressions, table settings and where clauses stay. A backup is written first.
daana merge - // 06
Definitions live with the data
Deploy writes business definitions into your warehouse metadata. Measure definitions live in the project’s dar/*.yaml files, where an agent working in the project can read them. Warehouse-only access sees the views and columns.
daana_metadata
CI/CD without surprises
Check validates the model, mappings, workflow and connections before anything deploys. Generation is deterministic: the same model produces the same SQL, so every pull request shows exactly what will change.
daana check3-Layered
Architecture
Daana generates, deploys and loads SQL from a YAML model. Your team builds DAS, the source contracts and staging. Daana generates DAB and DAR from your business model, mappings and reporting declarations.
Marts, semantic models and graphs, all from the same model. Daana generates the marts; semantic models and graphs can be built from the same model. You can keep your semantic layer.
Semantic lineage Technical lineage
Connected data. Connected context. Daana connects the data path with definitions at every layer, declared where an agent can read them. This is the map an agent walks.
// NEXTORY · DAB BUSINESS MODEL
“What crystallized it was simple: when we actually wrote down what our core business concepts meant, we realized we didn't all agree.”
From source to metric, through DAS, DAB and DAR
Illustrative example · subscription lifecycleDAS · Data contract
What does the source mean?
The state the accounts service gave the account. DISABLED, since 2020: blocked by support or billing, no login. CLOSED_BY_USER, since last year: the user closed it in the app.
DAS: built by your team · open blueprintaccount_state_changed
new_state
ACTIVE · DISABLED · CLOSED_BY_USER
Contract field · STRING · REQUIRED
DAB · Business model
What does the business mean?
Where the customer's subscription stands. ENDED: no access and no billing, however the account was closed.
SUBSCRIPTION
subscription_status
DISABLED → ENDED
CLOSED_BY_USER → ENDED
Mapped from new_state · effective at the source event time
DAR · Metric definition
What is churn?
Subscriptions that ended in the month. Each counts once, in the month its status became ENDED.
fct__subscription_event
Monthly churn
Event count · grouped by event month
To investigate a number, give your agent the project declarations and the relevant data. It can inspect the metric definition, business mapping and source contract, then compare them with the evidence. How an agent found the root cause in a real standup →
Talk to your
data platform
One prepared table. A few charts. We've seen that “talk to your data” demo. Here the question goes further: what does the metric count, how is its business attribute mapped, and what arrived from the source? The declarations give an agent a way to investigate. The data and run records provide the evidence.
[ HUMAN ]
Why is revenue so low on the 4th?
[ AGENT ]
It isn't slow sales. Orders are missing.
Walked back
- Checked: DAR Daily revenueDefinition unchanged.
- Checked: DAB order_line.
order_line_amountThe mapping drops no line. - Checked: DAS sales_ordersorder_date against ingested_at: lost, not late.
- Failed: Landing Shop databaseNo orders landed for 6h40m. The connector stalled overnight.
Follow the declarations. Check the evidence.
Follow the declarations.Check the evidence.
That was one walk. The same declarations answer the other questions too:
Understand a metric
Trace a number through its business definition, mapping, and source contract.
Assess a change
Follow the connections to see which business concepts and metrics depend on a source field.
Diagnose a mismatch
Compare the definitions, mappings, and run history to locate what needs correcting.
Don't take our word for it. Ask your agent.
Give the agent you already use this question about your own platform:
Our revenue looks low for last Tuesday. Walk from the dashboard metric back to the source system. At each step, tell me what the data means and where it comes from, and show me where you found it.
Count how often it had to read code, or guess. With Daana, your agent can inspect the model, mappings and reporting declarations behind a number.
Agents can read what Daana is at daana.dev/llms.txt.
Inspect the bookstore’s public declarations and revenue example
Request
access
Less time reconstructing the platform. More time building and operating it.
Need help building your data platform?
We'll spend time with your data team, understand where you are and where you want to go, and come back with a roadmap. What to build, in what order, and why.