Dashboards as Code/Dashboards as codeAnalytics Engineer

How do I build a metrics layer so metrics stay consistent?

In Bruin, a metric is defined once in YAML with its aggregation, source table, and time dimension, next to the pipeline that builds the table. Every chart and query references that single definition, so the same number is returned wherever the metric is used.

Command

bruin run

Defined in

YAML + SQL

Works with

Bruin + your warehouse

What you get

single metric definitionshared aggregationsreusable dimensions

How it works in code

metrics:
  - name: active_users
    label: Active Users
    source: analytics.events
    aggregation: count_distinct
    expression: user_id
    time_dimension: event_date

Run bruin run and every chart reads the metric from one definition.

About Bruin

What is Bruin?

Bruin is an open-source, AI-powered data platform. One project covers the whole path from source to answer: data ingestion (with ingestr), SQL and Python transformations, quality checks, column-level lineage, a data catalog and scheduling. On top of that data, an AI data analyst answers questions in Slack, Microsoft Teams, Google Chat, WhatsApp, Discord, Telegram, email or the browser, and builds dashboards from a prompt.

Pipelines are plain SQL, Python and YAML files in your own Git repository, and the work runs inside your own warehouse: Snowflake, BigQuery, Databricks, Redshift, Postgres, ClickHouse, DuckDB and others. The Bruin CLI is open source under Apache 2.0 and runs on a laptop, in CI or on-prem. Bruin Cloud is optional and adds scheduling, the AI data analyst, governance, SSO and audit logs.

For dashboards as code that means dac: dashboards defined as YAML in Git, served from your warehouse, next to the pipelines that build the data.

Replaces
Separate tools for ingestion, transformation, orchestration, data quality, cataloguing and BI
Open source
Bruin CLI under Apache 2.0; ingestr source-available under the Functional Source License
Your data
Stays in your warehouse; pipelines stay in your Git repository
Security
ISO/IEC 27001:2022 certified and SOC 2 Type 2 attested
Used by
Data teams at Lessmore, StarBerry, NativeMinds, SCG, M8 Games and Fabrikatör

Why Bruin for dashboards as code

  • Dashboards in Git

    Each dashboard is a file, reviewed in a pull request and rolled back like code.

  • Straight from the warehouse

    dac queries your warehouse directly. There is no extract to refresh.

  • Next to the pipeline

    The tables a dashboard reads are built and checked in the same Bruin project.

  • Testable in CI

    Run dac validate on every change to catch a broken dashboard before it reaches users.

How it works

  1. 01

    Install dac

    Install dac and point it at your warehouse connection.

  2. 02

    Write the dashboard

    Describe charts, queries and filters in a YAML file.

  3. 03

    Serve it

    Run dac serve to get a live dashboard, then commit it.

Dashboards that live in git

Bruin CLI and ingestr are on GitHub.

A demo walks through your own data.

Sign up to our newsletter

Practical updates on open-source data pipelines, AI analysts, governance, and what we are shipping at Bruin.

The signup form is hosted by Brevo. Allow marketing cookies to load it.