Declarative Data Modeling

THE DATA PLATFORM
AGENTS CAN READ

declared, not hand-coded

One declared model that humans and coding agents can understand, build on, and operate together.

[JOIN THE BETA]
Need help building your data platform? Free assessment →
Declare with YAML
Operate with CLI
Build with agents
Join symbol
[JOIN CLOSED BETA]
// Declare and let Daana handle the rest
Install Daana and go

Daana CLI is a declarative data modeling engine.

Define your business entities, relationships, and transformations in YAML. The engine handles consolidation, historization, deduplication, testing, lineage, and change tracking automatically.

No complex setup. No heavy frameworks. Just consistent, maintainable data models that run in your platform - Snowflake, BigQuery, Postgres, or any analytical database.

Steps
Editor
# Start modeling
model:
   id: "MY_DATA_MODEL"
   name: "MY_DATA_MODEL"
   definition: "A comprehensive business data model"
   description: "Defines entities and relationships"

   entities:
   # ... entity definitions

   relationships:
   # ... relationship definitions

`daana-cli init` creates project structure

// MECHANISMS

3-Layered
Architecture

Describe your sources, define your business concepts, and declare your metrics. Daana connects the layers and generates the pipelines.

// TECHNICAL + SEMANTIC LINEAGE

Connected data.
Connected context.

Knowing where a field came from is only part of the picture. Daana connects the data path with definitions at every layer, so humans and agents can understand both how data moves and what it means.

TECHNICAL LINEAGE

The fields, transformations, and dependencies.

SEMANTIC LINEAGE

The connected definitions that give them meaning.

FROM SOURCE TO METRIC

Illustrative example · subscription lifecycle
  1. 01 / SOURCE CONTRACT

    What does this field represent?

    The account's status after a change. Its contract describes the possible states, including CHURNED.

    account_status_changed

    new_status

    Contract field · STRING · REQUIRED

  2. 02 / BUSINESS MODEL

    Which concept does it describe?

    The subscription's lifecycle state, recorded at the time it changed. The mapping connects the source status to this business definition.

    SUBSCRIPTION

    subscription_status

    Mapped from new_status · effective at the source event time

  3. 03 / METRIC DEFINITION

    How is the number built?

    Monthly churn events: count subscription events that enter the CHURNED state, grouped by the month in which the change happened.

    fact_subscription_event

    Monthly churn events

    Event count · grouped by event month

The source contract, business model, and metric definition together create semantic lineage. Combined with the technical connections, they explain what this number means and how it was built.

// FOR YOUR TEAM AND YOUR AGENTS

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.

Less time reconstructing the platform.
More time building and operating it.

[ JOIN THE BETA ]
// WE BUILD IT WITH YOU

Need help getting there? We build alongside your engineers, from your first business model to a working data platform your team can own.

Get a free assessment →
JOIN DAANA'S WAITLIST
// 01 ABOUT YOU

Role

Data Engineer

Analytics Engineer

Platform Lead

Other

Favorite Platform

BigQuery

Snowflake

Postgres

Other

// 02 ENTER DETAILS
SET_NAME *
SET_EMAIL *